Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The method comprises: acquiring identifiers of M non-3rd generation partnership project (3GPP) network access nodes, wherein the M non-3GPP network access nodes comprise a first node, the first node supports simplified access traffic steering, switching and splitting (ATSSS)-lite, and M is an integer greater than or equal to 1; on the basis of the identifier of the first node, determining a first user plane function network element, wherein the first user plane function network element supports the ATSSS-lite, and a connection can be established between the first user plane function network element and the first node; and sending address information of the first user plane function network element. By means of the method, in an ATSSS-lite scenario, a user plane function network element, which supports an ATSSS-lite function and has a connection relationship with a selected non-3GPP network access node, is selected, such that a terminal device can complete the authentication and user plane establishment of non-3GPP access.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 3, 2024, with application number 202410404960.8 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more particularly, to a communication method and a communication device. Background Art

[0003] Access traffic steering, switching, splitting (ATSSS) is an optional feature of 5G networks that can be supported by user equipment (UE) and 5G core (5GC) networks.

[0004] The ATSSS feature allows both 3rd Generation Partnership Project (3GPP) and non-3GPP access. In the ATSSS scenario, the non-3GPP access path uses the non-3GPP interworking function (N3IWF) or the trusted non-3GPP gateway function (TNGF) to establish a connection with the core network.

[0005] The simplified access traffic steering, conversion, and splitting (ATSSS-lite) scenario hopes that on the basis of the ATSSS scenario, the non-3GPP access path will no longer use the non-3GPP interworking function (N3IWF) or the trusted non-3GPP gateway function (TNGF) to establish a connection with the core network. Instead, the non-3GPP user plane will be directly established through non-3GPP network access nodes such as Wi-Fi networks and user plane function (UPF) network elements.

[0006] There are many non-3GPP network access nodes, and it is basically impossible to establish connections between all nodes and all user plane functional network elements. How to establish non-3GPP network access in the ASSSS-lite scenario is an urgent problem to be solved. Summary of the Invention

[0007] The present application provides a communication method and a communication device for selecting a non-3GPP network access node that can be directly connected to a user plane function network element and a user plane function network element that supports the ATSSS-lite function and has a connection relationship with the selected non-3GPP network access node in an ATSSS-lite scenario.

[0008] In a first aspect, a communication method is provided. The method may be executed by a session management function network element, or may be executed by a chip or circuit configured in the session management function network element, and this application does not limit this.

[0009] The method includes: obtaining identifiers of M non-3GPP network access nodes, the M non-3GPP network access nodes including a first node, the first node supporting simplified access traffic steering, switching and splitting ATSSS-lite, and M being an integer greater than or equal to 1; determining a first user plane function network element according to the identifier of the first node, the first user plane function network element supporting ATSSS-lite, and a connection being able to be established between the first user plane function network element and the first node; and sending address information of the first user plane function network element.

[0010] Through the above solution, in the ATSSS-lite scenario, a user plane function network element that supports the ATSSS-lite function and has a connection relationship with the selected non-3GPP network access node is selected, so that the terminal device can complete the authentication and user plane establishment of the non-3GPP access.

[0011] In combination with the first aspect, in some implementations of the first aspect, the M non-3GPP network access nodes include N nodes that support ASSSS-lite, where N is an integer greater than or equal to 1, 1≤N≤M; the method also includes: determining a first node from the N nodes that support ASSSS-lite.

[0012] Through the above solution, the session management function network element can select a node that supports ATSSS-lite, thereby completing the subsequent non-3GPP access authentication and user plane establishment.

[0013] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending an identifier of the first node.

[0014] Through the above solution, the session management function network element selects a node that supports ASSSS-lite and can inform the terminal device, so that the terminal device can complete the authentication and user plane establishment of non-3GPP access through the node.

[0015] In combination with the first aspect, in some implementations of the first aspect, determining the first node from N nodes supporting ASSSS-lite includes: determining the first node based on the location of the terminal device and / or the priority of the N nodes supporting ASSSS-lite.

[0016] In combination with the first aspect, in some implementations of the first aspect, before sending the address information of the first user plane function network element, the method further includes: acquiring the address information of the first user plane function network element.

[0017] In combination with the first aspect, in some implementations of the first aspect, obtaining identifiers of M 3GPP network access nodes includes: receiving identifiers of M non-3GPP network access nodes from a terminal device.

[0018] Through the above solution, the session management function network element can receive the identifier of the non-3GPP network access node from the terminal device, and thus can select the user plane function network element according to the identifier provided by the terminal device.

[0019] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving first indication information from an access and mobility management function network element, the first indication information indicating that a first user plane function network element is determined based on identifiers of M non-3GPP network access nodes.

[0020] In combination with the first aspect, in some implementations of the first aspect, the method further includes: obtaining information of non-3GPP network access nodes supporting ASSSS-lite within the service area of ​​the access and mobility management function network element.

[0021] Through the above solution, the session management function network element can pre-configure or obtain from other network elements the information of non-3GPP network access nodes supporting ATSSS-lite within the service area of ​​the access and mobility management function network element, so that the M obtained non-3GPP network access nodes can be selected.

[0022] In a second aspect, a communication method is provided. The method can be executed by a terminal device, or can be executed by a chip or circuit configured in the terminal device, and this application does not limit this.

[0023] The method includes: obtaining identifiers of L non-3GPP network access nodes, the L non-3GPP network access nodes including a first node that supports simplified access traffic steering, switching and splitting ATSSS-lite, and L is an integer greater than or equal to 1; sending identifiers of P non-3GPP network access nodes, the P non-3GPP network access nodes belong to the L non-3GPP network access nodes, the P non-3GPP network access nodes include the first node, 1≤P≤L; receiving address information of a first user plane function network element, the first user plane function network element supports ASSSS-lite, and a connection can be established between the first user plane function network element and the first node.

[0024] Through the above scheme, in the ATSSS-lite scenario, the non-3GPP network access node that can be directly connected to the user plane function network element and the user plane function network element that supports the ATSSS-lite function and has a connection relationship with the selected non-3GPP network access node are determined, so that the terminal device can complete the authentication and user plane establishment of the non-3GPP access.

[0025] In combination with the second aspect, in some implementations of the second aspect, the L non-3GPP network access nodes all support ASSSS-lite, and the method further includes: determining P non-3GPP network access nodes from the L non-3GPP network access nodes.

[0026] Through the above solution, the terminal device can select a node that supports ATSSS-lite, thereby completing the subsequent non-3GPP access authentication and user plane establishment.

[0027] In combination with the second aspect, in some implementations of the second aspect, P is equal to 1, and the P non-3GPP network access nodes are first nodes.

[0028] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving an identifier of the first node; and establishing a connection with the first user plane function network element through the first node.

[0029] Through the above solution, the core network can select a node that supports ATSSS-lite for the terminal device, thereby completing the subsequent non-3GPP access authentication and user plane establishment.

[0030] In combination with the second aspect, in some implementations of the second aspect, obtaining the identifiers of L non-3GPP network access nodes includes: receiving a broadcast message from the L non-3GPP network access nodes, where the broadcast message includes the identifiers of the L non-3GPP network access nodes.

[0031] Through the above solution, the terminal device can collect information about non-3GPP network access nodes through broadcast messages, thereby completing the subsequent selection of non-3GPP network access nodes that support ASSSS-lite.

[0032] In combination with the second aspect, in some implementations of the second aspect, obtaining identifiers of L non-3GPP network access nodes includes: receiving identifiers of the L non-3GPP network access nodes from an access and mobility management function network element.

[0033] Through the above solution, the terminal device can request the network to obtain information about non-3GPP network access nodes that support ASSSS-lite.

[0034] In combination with the second aspect, in some implementations of the second aspect, before receiving the identifiers of L non-3GPP network access nodes from the access and mobility management function network element, the method also includes: sending a first request message to the access and mobility management function network element, the first request message being used to request information about non-3GPP network access nodes that support ATSSS-lite within the service area of ​​the access and mobility management function network element.

[0035] In combination with the second aspect, in some implementations of the second aspect, obtaining identifiers of L non-3GPP network access nodes includes: receiving identifiers of the L non-3GPP network access nodes from a unified data management network element.

[0036] Through the above solution, the network can actively push information about non-3GPP network access nodes that support ASSSS-lite to the terminal device.

[0037] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending second indication information, where the second indication information indicates that the terminal device supports ASSSS-lite.

[0038] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending third indication information, the third indication information instructing the access and mobility management function network element to select a session management function network element that supports ATSSS-lite.

[0039] On the third aspect, a communication method is provided, which can be executed by an access and mobility management function network element, or by a chip or circuit configured in the access and mobility management function network element, and this application does not limit this.

[0040] The method includes: obtaining identifiers of P non-3GPP network access nodes, where the P non-3GPP network access nodes include a first node, the first node supports ATSSS-lite, and P is an integer greater than or equal to 1; determining M non-3GPP network access nodes that support ATSSS-lite among the P non-3GPP network access nodes, where the M non-3GPP network access nodes include the first node, and 1≤M≤P; and sending the identifiers of the M non-3GPP network access nodes.

[0041] Through the above solution, the access and mobility management function network element can select a non-3GPP network access node that supports ASSSS-lite, thereby completing the subsequent non-3GPP access authentication and user plane establishment.

[0042] In conjunction with the third aspect, in some implementations of the third aspect, sending the identifiers of the M non-3GPP network access nodes includes: sending the identifiers of the M non-3GPP network access nodes to a session management function network element;

[0043] In combination with the third aspect, in some implementations of the third aspect, the method further includes: determining a session management function network element that supports ASSSS-lite.

[0044] In combination with the third aspect, in some implementations of the third aspect, the method further includes: sending a third indication message to instruct the AMF to select a session management function network element that supports ASSSS-lite.

[0045] In combination with the third aspect, in some implementations of the third aspect, the method further includes: sending information of non-3GPP network access nodes supporting ATSSS-lite within the service area of ​​the access and mobility management function network element to the session management function network element.

[0046] In the fourth aspect, a communication method is provided, which can be executed by an access and mobility management function network element or a session management network element, or can also be executed by a chip or circuit configured in the access and mobility management function network element or the session management network element. This application does not limit this.

[0047] The method includes: receiving identifications of one or more non-3GPP network access nodes, wherein none of the one or more non-3GPP network access nodes supports ATSSS-lite; and sending failure indication information, wherein the failure indication information indicates that the terminal device has failed to access the non-3GPP network.

[0048] In combination with the fourth aspect, in some implementations of the fourth aspect, the method further includes: sending information of non-3GPP network access nodes supporting ASSSS-lite within the location range of the terminal device to the terminal device.

[0049] In a fifth aspect, a communication method is provided. The method can be executed by a terminal device, or can be executed by a chip or circuit configured in the terminal device. This application does not limit this.

[0050] The method includes: obtaining the identifiers of one or more non-3GPP network access nodes, wherein none of the one or more non-3GPP network access nodes supports ATSSS-lite; sending the identifiers of the one or more non-3GPP network access nodes; and receiving failure indication information, wherein the failure indication information indicates that the terminal device has failed to access the non-3GPP network.

[0051] In combination with the fifth aspect, in some implementations of the fifth aspect, the method further includes: receiving information of non-3GPP network access nodes supporting ASSSS-lite within the location range of the terminal device.

[0052] In a sixth aspect, a communication method is provided. The method can be executed by a terminal device, or can be executed by a chip or circuit configured in the terminal device. This application does not limit this.

[0053] The method includes: sending ATSSS-lite-related session request information or inquiry information inquiring whether an ASSSS-lite-related session can be initiated; receiving an identifier of a first node, where the first node is a non-3GPP network access node that supports ATSSS-lite; receiving address information of a first UPF, where the first UPF supports ATSSS-lite, and a connection can be established between the first UPF and the first node.

[0054] In the seventh aspect, a communication method is provided, which can be executed by an access and mobility management function network element, or by a chip or circuit configured in the access and mobility management function network element. This application does not limit this.

[0055] The method includes: receiving ASSSS-lite-related session request information or inquiry information inquiring whether an ASSSS-lite-related session can be initiated; determining at least one non-3GPP network access node supporting ASSSS-lite based on the location of a terminal device, the at least one non-3GPP network access node supporting ASSSS-lite including a first node; and sending an identifier of the first node.

[0056] In the eighth aspect, a communication device is provided, which may include modules or units corresponding to the methods / operations / steps / actions described in the first aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0057] In the ninth aspect, a communication device is provided, which may include modules or units corresponding to the methods / operations / steps / actions described in the second aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0058] In the tenth aspect, a communication device is provided, which may include modules or units corresponding to the methods / operations / steps / actions described in the third aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0059] In the eleventh aspect, a communication device is provided, which may include modules or units corresponding to the methods / operations / steps / actions described in the fourth aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0060] In the twelfth aspect, a communication device is provided, which may include modules or units corresponding to the methods / operations / steps / actions described in the fifth aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0061] In the thirteenth aspect, a communication device is provided, which may include modules or units corresponding to the methods / operations / steps / actions described in the sixth aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0062] In the fourteenth aspect, a communication device is provided, which may include modules or units corresponding to the methods / operations / steps / actions described in the seventh aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0063] In a fifteenth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and configured to execute instructions in the memory to implement the method of the first and fourth aspects, and any possible implementation of the first and fourth aspects. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

[0064] In one implementation, the communication device is a session management function network element. When the communication device is a session management function network element, the communication interface may be a transceiver, or an input / output interface.

[0065] In another implementation, the communication device is a chip configured in a session management function network element. When the communication device is a chip configured in a session management function network element, the communication interface may be an input / output interface.

[0066] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0067] In a sixteenth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and configured to execute instructions in the memory to implement the method of the second, fourth, and fifth aspects, and any possible implementation of the second, fourth, and fifth aspects. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

[0068] In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver, or an input / output interface.

[0069] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface may be an input / output interface.

[0070] In a seventeenth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and configured to execute instructions in the memory to implement the method of the third, fourth, and seventh aspects, and any possible implementation of the third, fourth, and seventh aspects. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

[0071] In one implementation, the communication device is an access and mobility management function network element. When the communication device is an access and mobility management function network element, the communication interface may be a transceiver, or an input / output interface.

[0072] In another implementation, the communication device is a chip configured in an access and mobility management function network element. When the communication device is a chip configured in an access and mobility management function network element, the communication interface may be an input / output interface.

[0073] In an eighteenth aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method of any possible implementation of aspects one to seven.

[0074] In a specific implementation, the processor may be one or more chips, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be received and input by a receiver, and the signal output by the output circuit may be output to and transmitted by a transmitter. The input circuit and the output circuit may be the same circuit, which functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0075] In a nineteenth aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a receiver and transmit signals via a transmitter to execute the method of any possible implementation of aspects one to seven.

[0076] Optionally, there are one or more processors and one or more memories.

[0077] Optionally, the memory may be integrated with the processor, or be provided separately from the processor.

[0078] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM). The memory can be integrated with the processor on the same chip, or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0079] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, data output by the processor can be output to the transmitter, and input data received by the processor can be received from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0080] The processing device in the aforementioned aspect 19 may be one or more chips. The processor in the processing device may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated into the processor or located independently of the processor.

[0081] In the twentieth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute a method in any possible implementation of the first to seventh aspects above.

[0082] In the twenty-first aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the method in any possible implementation of the above-mentioned first to seventh aspects to be executed.

[0083] In the twenty-second aspect, a communication system is provided, comprising the aforementioned terminal device, and at least one of an access and mobility function management network element and a session management function network element. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] FIG1 is a schematic diagram of an example of a communication system to which the present application is applied.

[0085] FIG2 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0086] FIG3 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0087] FIG4 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0088] FIG5 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0089] FIG6 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0090] FIG7 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0091] FIG8 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0092] FIG9 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0093] FIG10 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0094] FIG11 is a schematic block diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0095] The technical solution in this application will be described below with reference to the accompanying drawings.

[0096] The technical solutions provided in this application can be applied to various communication systems, such as new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0097] In a communication system, the part operated by an operator may be referred to as a public land mobile network (PLMN), or an operator network, etc. A PLMN is a network established and operated by an operator for the purpose of providing land mobile communication services to the public. It is mainly a public network in which a mobile network operator (MNO) provides mobile broadband access services to users. The PLMN described in the embodiments of the present application may specifically be a network that complies with the standards of the 3rd Generation Partnership Project (3GPP), referred to as a 3GPP network. 3GPP networks generally include but are not limited to fifth-generation mobile communication (5th-generation, 5G) networks, fourth-generation mobile communication (4th-generation, 4G) networks, and other future communication systems.

[0098] For ease of description, the embodiments of the present application will be described using PLMN or 5G network as an example.

[0099] Figure 1 is a schematic diagram of a network architecture 100, using the 5G network architecture based on a service-based architecture (SBA) in a non-roaming scenario as defined in the 3GPP standardization process as an example. As shown in Figure 1 , the network architecture may include a terminal device component, a data network (DN) component, and a carrier network (PLMN) component. The carrier network PLMN component may include, but is not limited to, a (radio) access network (R)AN) 120 and a core network (CN) component.

[0100] The following is a brief description of the functions of the network elements in each part.

[0101] The terminal device portion may include a terminal device 110, which is a device that provides voice and / or data connectivity to the user. The terminal device 110 may also be referred to as a user equipment UE. The terminal device 110 in this application is a device with wireless transceiver functions, which can communicate with one or more core network (CN) devices via an access network device (or also referred to as an access device) in a (radio) access network (R)AN 120. The terminal device 110 may also be referred to as an access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent or user device, etc. The terminal device 110 may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it may also be deployed on water (such as a ship, etc.); it may also be deployed in the air (such as an airplane, balloon and satellite, etc.). The terminal device 110 may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a smartphone, a mobile phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or the like. Alternatively, the terminal device 110 may be a handheld device with wireless communication capabilities, a computing device, or other device connected to a wireless modem, an in-vehicle device, a wearable device, an unmanned aerial vehicle (UAV) device, or a terminal in the Internet of Things (IoT), the Internet of Vehicles (IoV), any terminal in a 5G network or future networks, a relay user device, or a terminal in a future-evolved network. The relay user device may be, for example, a 5G residential gateway (RG). For example, the terminal device 110 may be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home. The terminal device here refers to a 3GPP terminal. The embodiments of the present application do not limit the type or category of terminal devices. For ease of explanation, the present application will use UE to represent terminal devices as an example for explanation.

[0102] (R)AN 120 may include one or more access network elements or access network devices, and the interface between the access network device and the terminal device may be a Uu interface (or air interface, i.e., the messages exchanged between the access network device and the terminal device may be called air interface messages). Of course, in future communications, the interface name may remain unchanged or may be replaced by other names, and this application does not limit this. (R)AN 120 is a device that provides wireless communication functions for the terminal device 110, which can connect the terminal device to a node or device of a wireless network, and may also be called a network device. (R)AN 120 can be regarded as a subnet of the operator network, and is an implementation system between a service node in the operator network and the terminal device 110. For example, the terminal device 110 can connect to a service node of the operator network through (R)AN 120, thereby obtaining the services provided by the service node. For the convenience of description, in all embodiments of this application, the above-mentioned device that provides wireless communication functions for the terminal device 110 is collectively referred to as an access network device or simply referred to as RAN. It should be understood that this document does not limit the specific type of access network device.

[0103] The CN part may include but is not limited to the following network functions (NF): user plane function (UPF) 130, network exposure function (NEF) 131, network function repository function (NRF) 132, policy control function (PCF) 133, unified data management function (UDM) 134, unified data repository function (UDR) 135, application function (AF) 136, authentication server function (AUSF) 137, access and mobility management function (AMF) 138, and session management function (SMF) 139.

[0104] The data network DN 140, also called a packet data network (PDN), is typically a network outside the operator's network, such as a third-party network.

[0105] The following is a brief description of the NF functions included in CN.

[0106] 1. UPF 130 is a gateway provided by the operator, serving as the gateway for communication between the operator network and DN 140. UPF 130 network functions include packet routing and transmission, packet detection, service usage reporting, Quality of Service (QoS) processing, uplink packet detection, downlink packet storage, and other user-plane-related functions.

[0107] 2. NEF 131 is a control plane function provided by the operator. It mainly enables third parties to use the services provided by the network, supports the network to open its capabilities, event and data analysis, provide PLMN security configuration information from external applications, and convert interactive information within and outside the PLMN.

[0108] 3. NRF 132 is a control plane function provided by the operator, which can be used to maintain real-time information of network functions and services in the network.

[0109] 4. PCF 133 is the control plane function provided by the operator. It mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network function, and is responsible for obtaining user subscription information related to policy decisions.

[0110] 5. UDM 134 is a control plane function provided by the operator and is responsible for storing information such as the subscriber permanent identifier (SUPI), the generic public subscription identifier (GPSI), and credentials of subscribers in the operator's network.

[0111] 6. UDR 135 is a control plane function provided by the operator. It provides the UDM with the function of saving and retrieving subscription data, the PCF with the function of saving and retrieving policy data, and the user's NF group ID information.

[0112] 7. AF 136 is a control plane function provided by the operator. It mainly provides corresponding services by interacting with other NFs in the PLMN, such as providing roaming UE with visitor network selection information, guiding the routing of data flows, and accessing NEF 131.

[0113] 8. AUSF 137 is a control plane function provided by the operator, and is usually used for level 1 authentication, i.e., authentication between the terminal device 110 (subscriber) and the operator's network.

[0114] 9. AMF 138 is a control plane network function provided by the operator network, responsible for access control and mobility management of the terminal device 110 accessing the operator network, such as mobility status management, allocation of user temporary identity, authentication and authorization of users, etc.

[0115] 10. SMF 139 is a control plane network function provided by the operator network. It is responsible for managing the protocol data unit (PDU) sessions of the terminal device 110 (including session establishment, modification, and release). This function is used for the selection and reselection of user plane function network elements, the allocation of Internet Protocol (IP) addresses for the terminal device, and quality of service (QoS) control. A PDU session is a channel for transmitting PDUs. The terminal device exchanges PDUs with the DN 140 through a PDU session. The SMF network function 139 is responsible for establishing, maintaining, and deleting PDU sessions. The SMF network function 139 includes session management (such as session establishment, modification, and release, including tunnel maintenance between the user plane function (UPF) 130 and the (R)AN 120), selection and control of the UPF network function 130, service and session continuity (SSC) mode selection, roaming, and other session-related functions.

[0116] It is understood that the above network elements or functions can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualized functions instantiated on a shared platform (e.g., a cloud platform). Simply put, an NF can be implemented by hardware or software.

[0117] In Figure 1, Nnef, Nnrf, Npcf, Nudm, Nudr, Naf, Nausf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. For example, the meaning of the above interface serial numbers can be found in the meaning defined in the 3GPP standard protocol, and this application does not limit the meaning of the above interface serial numbers. It should be noted that the interface name between the various network functions in Figure 1 is only an example. In a specific implementation, the interface name of the system architecture may also be other names, which is not limited by this application. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.

[0118] It should be noted that in the architecture shown in Figure 1, the interface between the (R)AN and CN can also be called the NG interface (not shown in the figure), and the (R)AN and CN are connected via the NG interface. The NG interface can include the NG-C interface and the NG-U interface. The NG-C interface is a control plane interface, connecting the (R)AN and AMF, and is used to transmit control plane data; the NG-U interface is a user plane interface, connecting the (R)AN and UPF, and is used to transmit user plane data.

[0119] It should be understood that the above network architecture 100 is only described from the perspective of a service-based architecture. In this service-based architecture, the PLMN can combine some or all network functions in an orderly manner according to specific scenario requirements, realizing customized network capabilities and services, thereby deploying dedicated networks for different services, that is, realizing 5G network slicing. Network slicing technology enables operators to respond to customer needs more flexibly and quickly, and supports flexible allocation of network resources.

[0120] For ease of explanation, in the embodiments of the present application, network functions (such as NEF 131...SMF 139) are collectively referred to as NFs. That is, the NFs described later in the embodiments of the present application can be replaced by any network function. In addition, in the embodiments of the present application, the session management function SMF 139 is referred to as SMF, and the terminal device 110 is referred to as UE. That is, the SMFs described later in the embodiments of the present application can be replaced by session management functions, and the UE can be replaced by a terminal device. Figure 1 only schematically illustrates some network functions, and the NFs described later are not limited to the network functions shown in Figure 1.

[0121] It should be understood that the AMF, SMF, UPF, NEF, AUSF, NRF, PCF, and UDM shown in Figure 1 can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0122] It should also be understood that the above naming is defined only to facilitate the distinction between different functions and should not constitute any limitation on this application. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks. For example, in future communication networks, some or all of the above network elements may continue to use 5G terminology, or may adopt other names.

[0123] In order to facilitate the introduction of this application, some concepts or terms involved in this application are first introduced.

[0124] 1. PDU Session

[0125] A PDU session is a logical connection between a UE and a specified DN, providing the UE with a user plane connection to the DN.

[0126] 2. Access traffic steering, switching, splitting (ATSSS)

[0127] It can also be called access traffic steering, conversion, and splitting. It is an optional feature of 5G networks and can be supported by UE and 5GC networks.

[0128] The ATSSS feature implements a multi-access PDU connection service that can use one 3GPP access network and one non-3GPP access network simultaneously, as well as two independent N3 / N9 tunnels between the PDU session anchor (PSA) and the RAN / AN to exchange protocol data units (PDUs) between the UE and the data network. The multi-access PDU connection service is achieved by establishing a multi-access PDU (MA PDU) session, that is, a PDU session with user plane resources on two access networks. This assumes that a single network slice selection assistance information (S-NSSAI) for the PDU session allows both 3GPP access and non-3GPP access.

[0129] The UE may request an MA PDU session when the UE is registered through both 3GPP and non-3GPP accesses, or when the UE is registered through only one access.

[0130] After the MA PDU session is established, when user plane resources are available on both access networks, the UE applies the network-provided policies (i.e., ATSSS rules) and takes into account local conditions (such as network interface availability, signal loss conditions, user preferences, etc.) to decide how to distribute uplink traffic across the two access networks. Similarly, the UPF anchor of the MA PDU session applies the network-provided policies (i.e., N4 rules) and feedback information received from the UE via the user plane (such as access network unavailability or availability) to decide how to distribute downlink traffic across the two N3 / N9 tunnels and the two access networks. When only one access network has user plane resources, the UE applies ATSSS rules and takes into account local conditions that trigger the establishment or activation of user plane resources on the other access.

[0131] The type of MA PDU session can be one of the following types: IPv4, IPv6, IPv4v6 and Ethernet. Unstructured type is not supported.

[0132] 3. Trusted non-3GPP access

[0133] A Trusted Non-3GPP Access Point (TNAP) is a trusted non-3GPP access point (eg, a Wi-Fi node), and a TNGF is a trusted non-3GPP gateway function that has a connection relationship with a 3GPP network.

[0134] The UE establishes a connection with the TNGF through TNAP, and connects to the AMF through TNGF, thus establishing a channel with the core network for identity authentication and registration processes. Subsequently, based on this established control plane channel, 5GC can establish a channel between the UE and TNGF and UPF to complete the transmission of user plane data.

[0135] 4. Untrusted non-3GPP access

[0136] The non-3GPP interworking function (N3IWF) is responsible for connecting untrusted non-3GPP access networks to the 5G core network. The UE must establish an IPSec tunnel with the N3IWF to connect to the core network through untrusted non-3GPP access.

[0137] 5. Simplified ATSSS (ATSSS-lite)

[0138] The ATSSS-lite scenario aims to build on the ATSSS scenario by eliminating the need for N3IWF or TNGF to establish a connection with the core network for non-3GPP access. Instead, the non-3GPP user plane is established directly with the user plane functional network element via Wi-Fi or IP access. According to the ATSSS-lite architecture, non-3GPP network access nodes must establish a connection with the user plane functional network element.

[0139] The following introduces the technical problems and technical solutions to be solved by this application.

[0140] In the ATSSS-lite scenario, the non-3GPP user plane is established directly through non-3GPP network access nodes such as Wi-Fi or IP access, instead of using N3IWF or TNGF to establish a connection with the core network.

[0141] There are many non-3GPP network access nodes, and it is basically impossible to establish connections between all nodes and all user plane functional network elements. Therefore, it is necessary to consider the support of ATSSS-lite by non-3GPP access nodes and the connection status with user plane functional network elements during the process of establishing connections and selecting user plane functional network elements.

[0142] The present application provides a communication method for selecting a non-3GPP network access node that supports ATSSS-lite, and selecting a user plane function network element that supports ASSSS-lite function and can establish a connection relationship with the selected non-3GPP network access node.

[0143] The following describes the communication method, communication device, and system according to the embodiments of the present application in conjunction with the accompanying drawings.

[0144] For ease of understanding and explanation, the following describes the perception method of the embodiment of the present application using the interaction between the access and mobility management function network element, the terminal device, and the session management function network element as an example, but this does not constitute any limitation on the execution subject of the perception method of the embodiment of the present application. For example, the method performed by the access and mobility management function network element may also be performed by a module (such as a circuit, chip, or chip system) of the access and mobility management function network element, or may be implemented by a logical node, logical module, or software that can implement all or part of the functions of the access and mobility management function network element. The method performed by the terminal device may also be performed by a module (such as a circuit, chip, or chip system) of an intermediate node, or may be implemented by a logical node, logical module, or software that can implement all or part of the functions of the terminal device. The method performed by the session management function network element may also be performed by a module (such as a circuit, chip, or chip system) of the session management function network element, or may be implemented by a logical node, logical module, or software that can implement all or part of the functions of the session management function network element.

[0145] It should be understood that the description of the specific scenarios in the embodiments of the present application is only an example. In addition to being applicable to the application scenarios described above, the methods provided in the embodiments of the present application are also applicable to application scenarios with similar problems.

[0146] It should be understood that the names of all nodes and messages in this application are merely names set for the convenience of description in this application. The names in the actual network may be different. This application should not be understood as limiting the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as a method or equivalent replacement of this application, and is within the scope of protection of this application. No further details will be given below.

[0147] The following describes in detail various communication methods provided in the embodiments of the present application with reference to the accompanying drawings.

[0148] It should be understood that the step numbers in the embodiments of the present application are for illustration only and do not limit the order in which the steps occur.

[0149] FIG2 shows a communication method 200 provided in the present application. The method in FIG2 includes at least part of the following steps.

[0150] S201: The terminal device obtains identifiers of L non-3GPP network access nodes, where L is an integer greater than or equal to 1.

[0151] Among them, the terminal device obtains the identifiers of L non-3GPP network access nodes, which can be divided into the following situations.

[0152] Case 1

[0153] In one implementation, obtaining the identifiers of the L non-3GPP network access nodes includes: obtaining the identifiers of the L non-3GPP network access nodes actively pushed by the network side, wherein the L non-3GPP network access nodes all support ATSSS-lite.

[0154] For example, the data management network element (such as UDM) sends the identifiers of the L non-3GPP network access nodes to the terminal device, and correspondingly, the terminal device receives the identifiers of the L non-3GPP network access nodes.

[0155] Optionally, the data management network element may determine whether the terminal device supports ASSSS-lite after the terminal device successfully registers for 3GPP access. If the terminal device supports ASSSS-lite, the data management network element may actively send the identifiers of the L non-3GPP network access nodes to the terminal device.

[0156] Optionally, the terminal device may send second indication information to the network side during the 3GPP access registration process, where the second indication information indicates that the terminal device supports ATSSS-lite. For example, the terminal device carries the second indication information in a 3GPP registration request message; or, during the 3GPP registration process, the terminal device carries the second indication information in an interactive message with a data management network element, so that the data management network element can determine whether the terminal device supports ATSSS-lite based on the second indication information and the terminal device's identifier.

[0157] It should be understood that the identifiers of the L non-3GPP network access nodes sent by the data management network element to the terminal device may be the identifiers of all non-3GPP network access nodes stored in the data management network element, or the identifiers of non-3GPP network access nodes that support ATSSS-lite within the service area of ​​the access and mobility management function network element, or the identifiers of non-3GPP network access nodes that support ATSSS-lite within the location range of the terminal device. Among them, the location information of the terminal device may be at the granularity of the tracking area identity (TAI) or the granularity of the cell ID. In this case, the data management network element may need to continuously update the identifiers of the non-3GPP network access nodes pushed to the terminal device during the movement of the terminal device.

[0158] Case 2

[0159] In another implementation, obtaining the identifiers of the L non-3GPP network access nodes includes: the terminal device requests the network side to obtain the identifiers of the L non-3GPP network access nodes, wherein the L non-3GPP network access nodes all support ATSSS-lite.

[0160] For example, after 3GPP registration, the terminal device sends a first request message to the access and mobility management function network element, where the first request message is used to request information about non-3GPP network access nodes that support ATSSS-lite within the service area of ​​the access and mobility management function network element. After receiving the first request message, the access and mobility management function network element sends the identifiers of L non-3GPP network access nodes that support ATSSS-lite within the service area to the terminal device. Optionally, the access and mobility management function network element determines and sends the L non-3GPP network access nodes based on the location of the terminal device.

[0161] It should be understood that the access and mobility management function network element is pre-configured with information of non-3GPP network access nodes supporting ASSSS-lite within its service range.

[0162] Case 3

[0163] In yet another implementation, obtaining the identifiers of the L non-3GPP network access nodes includes: the terminal device collecting identifiers of the non-3GPP network access nodes that support ASSSS-lite.

[0164] For example, if a non-3GPP network access node broadcasts whether it supports ASSSS-lite, the terminal device can receive the broadcast message sent by the non-3GPP network access node, thereby obtaining the identifiers of the L non-3GPP network access nodes. That is, the terminal device receives a broadcast message from the L non-3GPP network access nodes, and the broadcast message includes the identifiers of the L non-3GPP network access nodes that support ASSSS-lite, and the terminal device can determine that the L non-3GPP network access nodes support ASSSS-lite based on the broadcast message.

[0165] Case 4

[0166] In yet another implementation, obtaining the identifiers of the L non-3GPP network access nodes includes: the terminal device collecting the identifiers of the non-3GPP network access nodes.

[0167] For example, a terminal device may receive a broadcast message sent by a non-3GPP network access node, thereby obtaining the identifiers of the L non-3GPP network access nodes. That is, the terminal device receives a broadcast message from the L non-3GPP network access nodes, and the broadcast message includes the identifiers of the L non-3GPP network access nodes. However, the terminal device cannot learn or determine whether the L non-3GPP network access nodes support ATSSS-lite. In other words, the L non-3GPP network access nodes may all support ASSSS-lite, may partially support ASSSS-lite, or may not support ASSSS-lite at all.

[0168] S202 (optional step, performed with either step S204 or S206), the terminal device determines P non-3GPP network access nodes from L non-3GPP network access nodes, where the P non-3GPP network access nodes belong to the above L non-3GPP network access nodes, and 1≤P≤L.

[0169] In one implementation, corresponding to Case 1, Case 2, and Case 3 in S201, the terminal device determines (or selects) P ​​non-3GPP network access nodes from the L non-3GPP network access nodes supporting ASSS-lite.

[0170] Optionally, the terminal device may obtain a list of identifiers of accessible non-3GPP network access nodes within its location range, and compare the list with the identifiers of the aforementioned L non-3GPP network access nodes. If an accessible node exists in both of the L non-3GPP network access nodes, the node is selected as one of the P non-3GPP network access nodes. For example, if the L non-3GPP network access nodes include a first node, and the first node is also an accessible non-3GPP network access node within the location range of the terminal device, the first node may be determined as one of the P non-3GPP network access nodes.

[0171] For example, the terminal device determines the first node from the L non-3GPP network access nodes supporting ATSSS-lite, and sends the identifier of the first node to the access and mobility management function network element. At this time, P is equal to 1.

[0172] For another example, the terminal device determines multiple non-3GPP network access nodes from the L non-3GPP network access nodes that support ATSSS-lite, and sends the identifiers of P non-3GPP network access nodes to the access and mobility management function network element, where 1<P<L.

[0173] S203, the terminal device sends the identifiers of P non-3GPP network access nodes to the access and mobility management function network element, where the P non-3GPP network access nodes belong to the above-mentioned L non-3GPP network access nodes, 1≤P≤L; correspondingly, the access and mobility management function network element receives the identifiers of the P non-3GPP network access nodes.

[0174] In one implementation, corresponding to Case 1, Case 2, and Case 3 in S201, the terminal device sends all the identifiers of the L non-3GPP network access nodes that support ASSSS-lite to the access and mobility management function network element, and at this time P is equal to L.

[0175] In another implementation, if step S202 is executed, the terminal device sends the identifiers of P non-3GPP network access nodes determined from L non-3GPP network access nodes to the access and mobility management function network element, where 1≤P<L.

[0176] In another implementation, corresponding to case 4 in S201, the terminal device sends all the collected L identifiers of non-3GPP network access nodes whose support for ASSSS-lite is uncertain to the access and mobility management function network element, and P is equal to L at this time.

[0177] Optionally, the terminal device also sends a third indication message to the access and mobility management function network element, where the third indication message instructs the access and mobility management function network element to select a session management function network element that supports ATSSS-lite.

[0178] It should be understood that the terminal device sends the identifiers of P non-3GPP network access nodes to the access and mobility management function network element. It can be understood that the terminal device sends the identifiers of P non-3GPP network access nodes to the access and mobility management function network element through the access network. For the sake of simplicity and ease of understanding, the access network device is not shown in Figure 2.

[0179] S204 (optional step): The access and mobility management function network element determines whether the P non-3GPP network access nodes support ATSSS-lite.

[0180] In one implementation, the P non-3GPP network access nodes include nodes that support ATSSS-lite, and the access and mobility management function network element selects M non-3GPP network access nodes that support ATSSS-lite from the P non-3GPP network access nodes, where 1≤M≤P.

[0181] For example, when M is equal to 1, the access and mobility management function network element selects a first node that supports ASSSS-lite from the P non-3GPP network access nodes. Optionally, the first node can be determined based on the location information of the terminal device, a configuration policy, a preference of the terminal device (e.g., the priority of the P non-3GPP network access nodes), etc.

[0182] For another example, when M is greater than 1, the access and mobility management function network element selects M nodes that support ATSSS-lite from the P non-3GPP network access nodes.

[0183] In another implementation, the P non-3GPP network access nodes do not include a node supporting ASSSS-lite, and the access and mobility management function network element sends a failure indication message to the terminal device, where the failure indication message indicates that the terminal device's non-3GPP access has failed.

[0184] It should be noted that when all the P non-3GPP network access nodes support ASSSS-lite, that is, step S201 is executed according to situation 1, 2 or 3, or step S202 is executed, step S204 and the subsequent step S206 may not be executed.

[0185] S205 , the access and mobility management function network element sends the identifiers of M non-3GPP network access nodes to the session management function network element; correspondingly, the session management function network element receives the identifiers of the M non-3GPP network access nodes, 1≤M≤P.

[0186] It should be understood that if step S204 is executed, the access and mobility management function network element determines the M non-3GPP network access nodes from the above-mentioned P non-3GPP network access nodes and sends them to the session management function network element; if step S204 is not executed, the access and mobility management function network element will directly forward the identifiers of the above-mentioned P non-3GPP network access nodes received from the terminal device to the session management function network element, and at this time P is equal to M.

[0187] Optionally, before step S205, after the access and mobility management function network element receives the identifiers of the P non-3GPP network access nodes sent by the terminal device, it selects a session management function network element that supports ATSSS-lite. Optionally, selecting the session management function network element that supports ATSSS-lite includes: receiving third indication information, and selecting the session management function network element that supports ATSSS-lite based on the third indication information.

[0188] S206 (optional step): The session management function network element determines whether the M non-3GPP network access nodes support ASSSS-lite.

[0189] In one implementation, the M non-3GPP network access nodes include nodes that support ATSSS-lite, and the session management function network element selects N non-3GPP network access nodes that support ATSSS-lite from the M non-3GPP network access nodes, where 1≤N≤M.

[0190] For example, when N is equal to 1, the session management function network element selects a first node that supports ASSSS-lite from the M non-3GPP network access nodes. Optionally, the first node can be determined based on the location information of the terminal device, a configuration policy, a preference of the terminal device, etc.

[0191] For another example, when N is greater than 1, the session management function network element selects N nodes that support ASSSS-lite from the M non-3GPP network access nodes.

[0192] In another implementation, the M non-3GPP network access nodes include nodes that do not support ASSSS-lite, and the session management function network element sends failure indication information to the terminal device, where the failure indication information indicates that the terminal device's non-3GPP access has failed.

[0193] It should be understood that before step S206, the session management function network element can pre-configure or obtain from other network nodes (such as PCF, OAM, UDM) the identification information of the non-3GPP network access nodes that support ATSSS-lite in the corresponding area of ​​the access and mobility management function network element, so as to determine whether the M non-3GPP network access nodes support ATSSS-lite; correspondingly, the access and mobility management function network element sends the identification information of the non-3GPP network access nodes that support ATSSS-lite in the corresponding area of ​​the access and mobility management function network element to the session management function network element.

[0194] It should be understood that when all the M non-3GPP network access nodes support ASSSS-lite, that is, when step S202 or S204 is executed, step S206 may not be executed.

[0195] S207: The session management function network element determines a first user plane function network element according to the identifier of the first node. The first user plane function network element supports ATSSS-lite, and a connection can be established between the first user plane function network element and the first node.

[0196] The fact that a connection can be established between the first user plane function network element and the first node can be understood as: there is a connection relationship between the first user plane function network element and the first node, or the first node is authorized to access the first user plane function network element.

[0197] Optionally, when M is equal to 1, the M non-3GPP network access nodes are first nodes, and the session management function network element determines the first user plane function network element according to the identifier of the first node.

[0198] Optionally, when M is greater than 1, the M non-3GPP network access nodes include N non-3GPP network access nodes that support ASSSS-lite, where 1≤N≤M. The session management function network element determining the first user plane function network element based on the identifier of the first node includes: determining the first node from the N non-3GPP network access nodes that support ASSSS-lite, and determining the first user plane function network element based on the identifier of the first node. It should be understood that if step S206 is not performed, M equals N.

[0199] The step of determining the first node from N non-3GPP network access nodes supporting ATSSS-lite includes determining the first node according to location information and configuration policy of the terminal device.

[0200] It should be understood that before step S207, the session management network element needs to pre-configure or obtain the following information from the NRF: whether the user plane function network element supports the ATSSS-lite function, and the connection information between the user plane function network element and the non-3GPP wireless network access node.

[0201] S208, the session management function network element sends the address information of the first username function network element to the terminal device; correspondingly, the terminal device receives the address information of the first username function network element.

[0202] It should be understood that before sending the address information, the session management function first obtains the address information of the first user plane function network element.

[0203] Specifically, obtaining the address information of the first user plane function network element includes: establishing an N4 connection with the first user plane function network element, establishing user plane resources for both 3GPP and non-3GPP access, and sending corresponding information to the session management function network element; establishing a packet forwarding control protocol (PFCP) between the first user plane function network element and the session management function network element, and obtaining the external IP address used for the corresponding non-3GPP access from the first user plane function network element.

[0204] It should be understood that the session management function network element sends the address information of the first user name function network element to the terminal device, including: sending the address information of the first user name function network element to the terminal device through other network elements (such as access and mobility management function network elements, access network equipment, etc.) as relays.

[0205] Optionally, if the first node is not determined by the terminal device in S202, the session management function network element further sends an identifier of the first node to the terminal device.

[0206] S209, the terminal device establishes a connection with the first user plane functional network element through the first node.

[0207] For example, the terminal device establishes an IPSec connection with the first user plane functional network element through the address information of the first user plane functional network element and the non-3GPP network corresponding to the first node, thereby completing the authentication of non-3GPP access and user plane establishment, and user plane data can be transmitted on the established user plane.

[0208] Figure 3 shows a communication method 300 provided by the present application. The method in Figure 3 includes at least part of the following steps. Figure 3 takes the access and mobility management function network element as AMF, the terminal device as UE, the session management network element as SMF, the user plane function network element as UPF, and the data management network element as UDM as an example to introduce the method of the present application. It should be understood that method 300 is a specific implementation of method 200. The concepts and terms in method 200 can be used in this method 300 and will not be repeated in this method 300.

[0209] S301: UDM sends identifiers of L non-3GPP network access nodes to a UE, where the L non-3GPP network access nodes all support ATSSS-lite.

[0210] The identifier of the non-3GPP network access node can be represented as a network service set identifier (SSID), where the SSID is the identifier of the non-3GPP network access node. The identifiers of the L non-3GPP network access nodes can be understood as an SSID list.

[0211] Optionally, after the UE successfully registers for 3GPP access, the UDM may determine whether the UE supports ASSSS-lite, and if the UE supports ASSSS-lite, proactively send the identifiers of the L non-3GPP network access nodes to the UE.

[0212] Optionally, during the UE's access registration process through 3GPP, a second indication information is sent to the AMF, where the second indication information indicates that the terminal device supports ATSSS-lite. For example, the UE carries the second indication information in a 3GPP registration request message; or, during the 3GPP registration process, the UE carries the second indication information in an interaction message with the UDM, so that the UDM can determine whether the UE supports ASSSS-lite based on the second indication information and the UE's identifier.

[0213] Optionally, the identifiers of the L non-3GPP network access nodes sent by the UDM to the UE may be the identifiers of all non-3GPP network access nodes stored in the UDM, or the identifiers of non-3GPP network access nodes that support ATSSS-lite within the AMF service area, or the identifiers of non-3GPP network access nodes that support ATSSS-lite within the UE location range. The UE location information may be of TAI granularity or cell granularity. In this case, the data management network element may need to continuously update the identifiers of the non-3GPP network access nodes pushed to the UE during the movement of the UE.

[0214] S302: The UE determines a first node from the L non-3GPP network access nodes.

[0215] Specifically, the UE can first obtain the identifier of the non-3GPP network access node that is accessible within the location range, for example, by receiving the broadcast message of the non-3GPP network access node that is accessible within the location range, obtain the identifier of the corresponding non-3GPP network access node, and construct a priority list of accessible non-3GPP network access nodes based on the UE's locally configured WLAN selection policy (WLANSP) rules and user preferences and other rule information.

[0216] Specifically, the UE may compare the identifier of the accessible non-3GPP network access node with the identifiers of the above-mentioned L non-3GPP network access nodes. If the accessible node exists in the L non-3GPP network access nodes at the same time, it is selected as one of the P non-3GPP network access nodes.

[0217] For example, the UE checks whether the accessible non-3GPP network access node is in the list of L non-3GPP network access nodes according to the constructed priority list of accessible non-3GPP network access nodes, starting from the highest priority. If so, the UE selects it as the first node.

[0218] For another example, after receiving the broadcast information, the UE excludes node information that is not in the L non-3GPP network access nodes, and then selects the node with the highest priority as the first node according to the WLANSP rules and user preferences configured locally in the UE.

[0219] S303, the UE sends the identifier of the first node to the AMF; correspondingly, the AMF receives the identifier of the first node.

[0220] Optionally, the UE may carry the identifier of the first node in the PDU session request message.

[0221] Optionally, the UE also sends a third indication information to the AMF, where the third indication information instructs the AMF to select an SMF that supports ASSS-lite.

[0222] S304, AMF selects SMF that supports ATSSS-lite.

[0223] S305, AMF sends the identifier of the first node to SMF; correspondingly, SMF receives the identifier of the first node.

[0224] S306, SMF selects the first UPF according to the identifier of the first node, a connection can be established between the first UPF and the first node, and the first UPF supports ATSSS-lite.

[0225] Specifically, the SMF may select a UPF based on information of a UPF that is configured in advance or obtained from other network elements (such as an NRF). The UPF information includes information of a UPF that supports ATSSS-lite, and at least one of the following information: location information of the UPF, and connection information between the UPF and a non-3GPP network access node.

[0226] S307, SMF obtains the address of the first UPF.

[0227] Specifically, the SMF first establishes an N4 session with the selected first UPF and sends an ATSSS-lite indication message to the first UPF; the first UPF opens the IP address information of the first UPF allocated to the UE to the SMF according to the ATSSS-lite indication message (it can be a session address or the same UPF IP address).

[0228] S308, SMF sends the address of the first UPF to the UE.

[0229] S309: The UE establishes a connection with the first UPF through the first node. Specifically, the UE establishes a connection with the first node and sends a data packet to the IP address of the first UPF through the first node. Correspondingly, the first UPF receives the data packet sent by the UE and forwarded by the first node.

[0230] Figure 4 shows a communication method 400 provided by the present application. The method in Figure 4 includes at least part of the following steps. Figure 4 takes the access and mobility management function network element as AMF, the terminal device as UE, the session management network element as SMF, the user plane function network element as UPF, and the data management network element as UDM as an example to introduce the method of the present application. It should be understood that method 400 is a specific implementation of method 200. The concepts and terms in method 200 can be used in this method 400 and will not be repeated in this method 400.

[0231] S401, the UE sends a first request message to the AMF, where the first request message is used to request information about non-3GPP network access nodes supporting ASSS-lite within the AMF service area.

[0232] S402: AMF sends the identifiers of L non-3GPP network access nodes to the UE, where all of the L non-3GPP network access nodes support ATSSS-lite.

[0233] Specifically, AMF pre-configures or obtains from other network elements the information of non-3GPP network access nodes that support ASSSS-lite within its service range, such as information of non-3GPP network access nodes that can be accessed by UEs at different locations. The location information of the UE can be at the TAI granularity or the cellID granularity.

[0234] Optionally, the AMF sends the identifiers of the above-mentioned L non-3GPP network access nodes to the UE based on the UE's location information.

[0235] S403: The UE determines a first node from the L non-3GPP network access nodes.

[0236] Specifically, before step S403, the UE may first obtain the identifiers of the non-3GPP network access nodes that are accessible within the location range, for example, by receiving broadcast messages of the non-3GPP network access nodes that are accessible within the location range, obtaining the identifiers of the corresponding non-3GPP network access nodes, and constructing a priority list of accessible non-3GPP network access nodes based on the WLAN selection policy WLANSP rules and user preferences and other rule information configured locally by the UE.

[0237] Specifically, the UE may compare the identifier of the accessible non-3GPP network access node with the identifiers of the above-mentioned L non-3GPP network access nodes. If the accessible node exists in the L non-3GPP network access nodes at the same time, it is selected as one of the P non-3GPP network access nodes.

[0238] For example, the UE checks whether the accessible non-3GPP network access node is in the list of L non-3GPP network access nodes according to the constructed priority list of accessible non-3GPP network access nodes, starting from the highest priority. If so, the UE selects it as the first node.

[0239] For another example, after receiving the broadcast information, the UE excludes node information that is not in the L non-3GPP network access nodes, and then selects the node with the highest priority as the first node according to the WLANSP rules and user preferences configured locally in the UE.

[0240] S404, the UE sends the identifier of the first node to the AMF; correspondingly, the AMF receives the identifier of the first node.

[0241] Optionally, the UE may carry the identifier of the first node in the PDU session request message.

[0242] Optionally, the UE also sends a third indication information to the AMF, where the third indication information instructs the AMF to select an SMF that supports ASSS-lite.

[0243] S405, AMF selects SMF that supports ATSSS-lite.

[0244] S406, AMF sends the identifier of the first node to SMF; correspondingly, SMF receives the identifier of the first node.

[0245] S407, SMF selects the first UPF according to the identifier of the first node, a connection can be established between the first UPF and the first node, and the first UPF supports ATSSS-lite.

[0246] Specifically, the SMF may select a UPF based on information of a UPF that is configured in advance or obtained from other network elements (such as an NRF). The UPF information includes information of a UPF that supports ATSSS-lite, and at least one of the following information: location information of the UPF, and connection information between the UPF and a non-3GPP network access node.

[0247] S408, SMF obtains the address of the first UPF.

[0248] Specifically, the SMF first establishes an N4 session with the selected first UPF and sends an ATSSS-lite indication message to the first UPF; the first UPF opens the IP address information of the first UPF allocated to the UE to the SMF according to the ATSSS-lite indication message (it can be a session address or the same UPF IP address).

[0249] S409, SMF sends the address of the first UPF to the UE.

[0250] S410: The UE establishes a connection with the first UPF through the first node. Specifically, the UE establishes a connection with the first node and sends a data packet to the IP address of the first UPF through the first node. Correspondingly, the first UPF receives the data packet sent by the UE and forwarded by the first node.

[0251] Figure 5 shows a communication method 500 provided by the present application. The method in Figure 5 includes at least some of the following steps. Figure 5 takes the access and mobility management function network element as AMF, the terminal device as UE, the session management network element as SMF, the user plane function network element as UPF, and the data management network element as UDM as an example to introduce the method of the present application. It should be understood that method 500 is a specific implementation of method 200. The concepts and terms in method 200 can be used in this method 500 and will not be repeated in this method 500.

[0252] S501: A UE receives a broadcast message from L non-3GPP network access nodes, where the broadcast message includes identifiers of the L non-3GPP network access nodes supporting ATSSS-lite.

[0253] It should be understood that in this embodiment, it is assumed that the non-3GPP network access node broadcasts whether it supports ASSSS-lite.

[0254] S502: The UE determines a first node from the L non-3GPP network access nodes.

[0255] Specifically, before step S502, the UE may first obtain the identifiers of the non-3GPP network access nodes that are accessible within the location range, for example, by receiving broadcast messages of the non-3GPP network access nodes that are accessible within the location range, obtaining the identifiers of the corresponding non-3GPP network access nodes, and constructing a priority list of accessible non-3GPP network access nodes based on the WLANSP rules and user preferences and other rule information configured locally by the UE.

[0256] Specifically, the UE may compare the identifier of the accessible non-3GPP network access node with the identifiers of the above-mentioned L non-3GPP network access nodes. If the accessible node exists in the L non-3GPP network access nodes at the same time, it is selected as one of the P non-3GPP network access nodes.

[0257] For example, the UE checks whether the accessible non-3GPP network access node is in the list of L non-3GPP network access nodes according to the constructed priority list of accessible non-3GPP network access nodes, starting from the highest priority. If so, the UE selects it as the first node.

[0258] For another example, after receiving the broadcast information, the UE excludes node information that is not in the L non-3GPP network access nodes, and then selects the node with the highest priority as the first node according to the WLANSP rules and user preferences configured locally in the UE.

[0259] S503, the UE sends the identifier of the first node to the AMF; correspondingly, the AMF receives the identifier of the first node.

[0260] Optionally, the UE may carry the identifier of the first node in the PDU session request message.

[0261] Optionally, the UE also sends a third indication information to the AMF, where the third indication information instructs the AMF to select an SMF that supports ASSS-lite.

[0262] S504, AMF selects SMF that supports ATSSS-lite.

[0263] S505, AMF sends the identifier of the first node to SMF; correspondingly, SMF receives the identifier of the first node.

[0264] S506, SMF selects the first UPF according to the identifier of the first node, a connection can be established between the first UPF and the first node, and the first UPF supports ATSSS-lite.

[0265] Specifically, the SMF may select the UPF based on the information of the UPF that is configured in advance or obtained from other network elements (such as NRF). The information of the UPF includes the information of the UPF that supports ATSSS-lite, and at least one of the following information: the location information of the UPF, and the connection information between the UPF and the non-3GPP network access node. Optionally, the location information of the UE may be of TAI granularity or cellID granularity. Optionally, the connection information between the UPF and the non-3GPP network access node may be the correspondence between the identifier of the UPF and the identifier of the non-3GPP network access node.

[0266] S507, SMF obtains the address of the first UPF.

[0267] Specifically, the SMF first establishes an N4 session with the selected first UPF and sends an ATSSS-lite indication message to the first UPF; the first UPF opens the IP address information of the first UPF allocated to the UE to the SMF according to the ATSSS-lite indication message (it can be a session address or the same UPF IP address).

[0268] S508, SMF sends the address of the first UPF to the UE.

[0269] S509, the UE establishes a connection with the first UPF through the first node.

[0270] Figure 6 shows a communication method 600 provided by the present application. The method in Figure 6 includes at least some of the following steps. Figure 6 takes the access and mobility management function network element as AMF, the terminal device as UE, the session management network element as SMF, the user plane function network element as UPF, and the data management network element as UDM as an example to introduce the method of the present application. It should be understood that method 600 is a specific implementation of method 200. The concepts and terms in method 200 can be used in this method 600 and will not be repeated in this method 600.

[0271] S601: A UE receives a broadcast message from L non-3GPP network access nodes, where the broadcast message includes identifiers of the L non-3GPP network access nodes supporting ATSSS-lite.

[0272] It should be understood that in this embodiment, it is assumed that the non-3GPP network access node broadcasts whether it supports ASSSS-lite.

[0273] S602, the UE sends the identifiers of the L non-3GPP network access nodes to the AMF; correspondingly, the AMF receives the identifiers of the L non-3GPP network access nodes.

[0274] Optionally, the UE may carry the identifiers of the L non-3GPP network access nodes in the PDU session request message.

[0275] Optionally, the UE also sends a third indication information to the AMF, where the third indication information instructs the AMF to select an SMF that supports ASSS-lite.

[0276] S603, AMF selects SMF that supports ATSSS-lite.

[0277] There are two ways to perform steps S604 and S605:

[0278] Option 1:

[0279] S604: The AMF determines a first node from the L non-3GPP network access nodes.

[0280] Specifically, before step S604, the AMF pre-configures or obtains from other network elements the information of non-3GPP network access nodes that support ASSSS-lite within the AMF service range, for example, the information of non-3GPP network access nodes that can be accessed by UEs at different locations. The location information of the UE can be at the TAI granularity or the cellID granularity. Thus, the AMF can obtain the identifiers of the non-3GPP network access nodes that support ASSSS-lite and are accessible within the UE location range.

[0281] Optionally, the AMF can also obtain the priority list of accessible non-3GPP network access nodes sent by the UE. The priority list is a priority list of accessible non-3GPP network access nodes constructed by the UE based on locally configured WLANSP rules and user preferences and other rule information.

[0282] Specifically, the AMF may compare the identifier of the non-3GPP network access node that supports ATSSS-lite and that the UE can access with the identifiers of the above-mentioned L non-3GPP network access nodes. If the non-3GPP network access node that supports ATSSS-lite and that the UE can access exists in the above-mentioned L non-3GPP network access nodes at the same time, it can be used as the first node.

[0283] Optionally, the AMF checks whether the accessible non-3GPP network access node is in the list of L non-3GPP network access nodes according to the received priority list, starting from the highest priority. If so, it is selected as the first node.

[0284] S605, AMF sends the identifier of the first node to SMF; correspondingly, SMF receives the identifier of the first node.

[0285] Option2:

[0286] S604, AMF sends the identifiers of L non-3GPP network access nodes to SMF; correspondingly, SMF receives the identifiers of the L non-3GPP network access nodes.

[0287] S605: The SMF determines a first node from the L non-3GPP network access nodes.

[0288] Specifically, before step S605, the SMF pre-configures or obtains from other network elements the information of non-3GPP network access nodes supporting ASSSS-lite within the service range of the AMF, for example, the information of non-3GPP network access nodes that can be accessed by UEs at different locations. The location information of the UE can be at the TAI granularity or the cellID granularity. Thus, the SMF can obtain the identifiers of the non-3GPP network access nodes supporting ASSSS-lite that can be accessed within the UE location range.

[0289] Optionally, the SMF can also obtain the priority list of accessible non-3GPP network access nodes sent by the UE. The priority list is a priority list of accessible non-3GPP network access nodes constructed by the UE based on locally configured WLANSP rules and user preferences and other rule information.

[0290] Specifically, the SMF can compare the identifier of the non-3GPP network access node that supports ATSSS-lite and can be accessed by the UE with the identifiers of the above-mentioned L non-3GPP network access nodes. If the non-3GPP network access node that supports ATSSS-lite and can be accessed by the UE exists in the above-mentioned L non-3GPP network access nodes at the same time, it can be used as the first node.

[0291] Optionally, the SMF checks whether the accessible non-3GPP network access node is in the list of L non-3GPP network access nodes according to the received priority list starting from the highest priority, and if so, selects it as the first node.

[0292] S606, SMF selects the first UPF according to the identifier of the first node, a connection can be established between the first UPF and the first node, and the first UPF supports ATSSS-lite.

[0293] Specifically, the SMF may select the UPF based on the information of the UPF that is configured in advance or obtained from other network elements (such as NRF). The information of the UPF includes the information of the UPF that supports ATSSS-lite, and at least one of the following information: the location information of the UPF, and the connection information between the UPF and the non-3GPP network access node. Optionally, the location information of the UE may be of TAI granularity or cellID granularity. Optionally, the connection information between the UPF and the non-3GPP network access node may be the correspondence between the identifier of the UPF and the identifier of the non-3GPP network access node.

[0294] S607, SMF obtains the address of the first UPF.

[0295] Specifically, the SMF first establishes an N4 session with the selected first UPF and sends an ATSSS-lite indication message to the first UPF; the first UPF opens the IP address information of the first UPF allocated to the UE to the SMF according to the ATSSS-lite indication message (it can be a session address or the same UPF IP address).

[0296] S608, SMF sends the address of the first UPF to the UE.

[0297] S609: The UE establishes a connection with the first UPF through the first node. Specifically, the UE establishes a connection with the first node and sends a data packet to the IP address of the first UPF through the first node. Correspondingly, the first UPF receives the data packet sent by the UE and forwarded by the first node.

[0298] Figure 7 shows a communication method 700 provided by the present application. The method in Figure 7 includes at least part of the following steps. Figure 7 takes the access and mobility management function network element as AMF, the terminal device as UE, the session management network element as SMF, the user plane function network element as UPF, and the data management network element as UDM as an example to introduce the method of the present application. It should be understood that method 700 is a specific implementation of method 200. The concepts and terms in method 200 can be used in this method 700 and will not be repeated in this method 700.

[0299] S701: A UE receives a broadcast message from L non-3GPP network access nodes, where the broadcast message includes identifiers of the L non-3GPP network access nodes.

[0300] It should be understood that in this embodiment, it is assumed that the non-3GPP network access node does not broadcast whether it supports ASSS-lite.

[0301] S702: The UE sends the identifiers of the L non-3GPP network access nodes to the AMF.

[0302] Optionally, the UE may carry the identifiers of the L non-3GPP network access nodes in the PDU session request message.

[0303] Optionally, the UE also sends a third indication information to the AMF, where the third indication information instructs the AMF to select an SMF that supports ASSS-lite.

[0304] S703, AMF selects SMF that supports ATSSS-lite.

[0305] There are two ways to execute steps S704 and S705:

[0306] Option 1:

[0307] S704: AMF determines whether the L non-3GPP network access nodes support ASSSS-lite.

[0308] If the L non-3GPP network access nodes include a first node that supports ASSSS-lite, the AMF determines the first node from the L non-3GPP network access nodes (refer to option 1 of step S604) and proceeds to step S705.

[0309] If none of the L non-3GPP network access nodes support ASSSS-lite, a failure indication message is sent to the UE.

[0310] S705, AMF sends the identifier of the first node to SMF; correspondingly, SMF receives the identifier of the first node.

[0311] Option2:

[0312] S704, AMF sends the identifiers of L non-3GPP network access nodes to SMF; correspondingly, SMF receives the identifiers of the L non-3GPP network access nodes.

[0313] S705, SMF determines whether the L non-3GPP network access nodes support ASSSS-lite.

[0314] If the L non-3GPP network access nodes include a first node that supports ASSS-lite, the SMF determines the first node from the L non-3GPP network access nodes (refer to option 2 of step S605) and proceeds to step S706.

[0315] If none of the L non-3GPP network access nodes support ASSSS-lite, a failure indication message is sent to the UE.

[0316] S706, SMF selects the first UPF according to the identifier of the first node, a connection can be established between the first UPF and the first node, and the first UPF supports ATSSS-lite.

[0317] Specifically, the SMF may select a UPF based on information of a UPF that is configured in advance or obtained from other network elements (such as an NRF). The UPF information includes information of a UPF that supports ATSSS-lite, and at least one of the following information: location information of the UPF, and connection information between the UPF and a non-3GPP network access node.

[0318] S707, SMF obtains the address of the first UPF.

[0319] Specifically, the SMF first establishes an N4 session with the selected first UPF and sends an ATSSS-lite indication message to the first UPF; the first UPF opens the IP address information of the first UPF allocated to the UE to the SMF according to the ATSSS-lite indication message (it can be a session address or the same UPF IP address).

[0320] S708, SMF sends the address of the first UPF to the UE.

[0321] S709: The UE establishes a connection with the first UPF through the first node. Specifically, the UE establishes a connection with the first node and sends a data packet to the IP address of the first UPF through the first node. Correspondingly, the first UPF receives the data packet sent by the UE and forwarded by the first node.

[0322] FIG8 shows a communication method 800 provided in the present application. The method in FIG8 includes at least part of the following steps.

[0323] S801, the terminal device sends an inquiry or request message to the access and mobility management network element, where the inquiry or request message is used to inquire or request whether the terminal device can initiate an ATSSS-lite related session; alternatively, the terminal device directly initiates an ATSSS-lite session request.

[0324] The inquiry or request information can be carried in the message exchanged between the terminal device and the access and mobility management network element, such as carried in the PDU session establishment request message, or it can be an inquiry or request message sent by the terminal device to the access and mobility management network element.

[0325] S802: The access and mobility management network element determines whether there is a non-3GPP network access node that supports ASSSS-lite based on the location of the terminal device.

[0326] S803 (option 1), if there is a non-3GPP network access node that supports ATSSS-lite, the access and mobility management network element sends the identifier of the first node to the session management function network element, and the first node is a non-3GPP network access node that supports ATSSS-lite, and then executes step S803.

[0327] S803 (option 2), if there is no non-3GPP network access node that supports ATSSS-lite, the access and mobility management network element sends a failure indication message to the terminal device, where the failure indication message indicates that the terminal device has failed to access the non-3GPP network.

[0328] It should be understood that the access and mobility management network element pre-configures the information of non-3GPP network access nodes supporting the ASSS-lite function within its service range.

[0329] Steps S804 to S806 may refer to steps S207 to S209 .

[0330] Figure 9 is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of the present application. As shown in Figure 9, the device 1000 may include a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 can communicate with the outside world, and the processing unit 1020 is used to process data. The transceiver unit 1010 may also be referred to as a communication interface or a transceiver unit.

[0331] In one possible design, the device 1000 can implement steps or processes corresponding to those executed by the terminal device in the above method embodiment, wherein the processing unit 1020 is used to perform operations related to processing of the terminal device element in the above method embodiment, and the transceiver unit 1010 is used to perform operations related to transceiving of the terminal device in the above method embodiment.

[0332] In another possible design, the device 1000 can implement steps or processes corresponding to those performed by the session management function network element in the above method embodiment, wherein the transceiver unit 1010 is used to perform operations related to the transmission and reception of the session management function network element in the above method embodiment, and the processing unit 1020 is used to perform operations related to the processing of the session management function network element in the above method embodiment.

[0333] In another possible design, the device 1000 can implement steps or processes corresponding to those performed by the access and mobility management function network element in the above method embodiment, wherein the transceiver unit 1010 is used to perform operations related to the reception and transmission of the access and mobility management function network element in the above method embodiment, and the processing unit 1020 is used to perform operations related to the processing of the access and mobility management function network element in the above method embodiment.

[0334] It should be understood that the device 1000 here is embodied in the form of a functional unit. The term "unit" here can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merging logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the device 1000 can be specifically the transmitting end in the above embodiment, and can be used to execute the various processes and / or steps corresponding to the transmitting end in the above method embodiment, or the device 2000 can be specifically the receiving end in the above embodiment, and can be used to execute the various processes and / or steps corresponding to the receiving end in the above method embodiment. To avoid repetition, it will not be repeated here.

[0335] The apparatus 1000 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the transmitting end in the above-mentioned method, or the apparatus 1000 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the receiving end in the above-mentioned method. The functions can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.

[0336] In addition, the above-mentioned transceiver unit can also be a transceiver circuit (for example, it can include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit. In an embodiment of the present application, the device in Figure 9 can be the receiving end or the transmitting end in the aforementioned embodiment, or it can be a chip or a chip system, such as a system on chip (SoC). Among them, the transceiver unit can be an input and output circuit or a communication interface. The processing unit is a processor or microprocessor or integrated circuit integrated on the chip. This is not limited here.

[0337] Figure 10 is a schematic diagram of the structure of a communication device 2000 provided in an embodiment of the present application. As shown in Figure 10, the device 2000 includes a processor 2010 and a transceiver 2020. The processor 2010 and the transceiver 2020 communicate with each other via an internal connection path. The processor 2010 is used to execute instructions to control the transceiver 2020 to send and / or receive signals.

[0338] Optionally, the apparatus 2000 may further include a memory 2030, which communicates with the processor 2010 and the transceiver 2020 via an internal connection path. The memory 2030 is used to store instructions, and the processor 2010 may execute the instructions stored in the memory 2030.

[0339] In a possible implementation, the apparatus 2000 is used to implement various processes and steps corresponding to the access and mobility management function network element in the above method embodiment.

[0340] In another possible implementation, the apparatus 2000 is used to implement the various processes and steps corresponding to the terminal device in the above method embodiment.

[0341] In another possible implementation, the apparatus 2000 is used to implement various processes and steps corresponding to the session management function network element in the above method embodiment.

[0342] It should be understood that the device 2000 can be specifically the transmitting end or receiving end in the above-mentioned embodiments, or can also be a chip or chip system. Correspondingly, the transceiver 2020 can be the transceiver circuit of the chip, which is not limited here. Specifically, the device 2000 can be used to perform the various steps and / or processes corresponding to the transmitting end or receiving end in the above-mentioned method embodiments.

[0343] Optionally, the memory 2030 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 2010 may be configured to execute instructions stored in the memory. When the processor 2010 executes the instructions stored in the memory, the processor 2010 is configured to perform the various steps and / or processes of the above-described method embodiments corresponding to the transmitting end or the receiving end.

[0344] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0345] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method embodiment can be completed by hardware integrated logic circuits in the processor or by software instructions. The above-mentioned processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor in the embodiments of the present application can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above-mentioned method.

[0346] It will be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronous linked dynamic random access memory, and direct memory bus random access memory. It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0347] FIG11 is a schematic diagram of the structure of a chip system 3000 provided in an embodiment of the present application. As shown in FIG11 , the chip system 3000 (or also referred to as a processing system) includes a logic circuit 3010 and an input / output interface 3020 .

[0348] The logic circuit 3010 may be a processing circuit in the chip system 3000. The logic circuit 3010 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 3000 can implement the methods and functions of the various embodiments of the present application. The input / output interface 3020 may be an input / output circuit in the chip system 3000, outputting information processed by the chip system 3000 or inputting data or signaling information to be processed into the chip system 3000 for processing.

[0349] As a solution, the chip system 3000 is used to implement the operations performed by the session management function network element in the above various method embodiments.

[0350] As a solution, the chip system 3000 is used to implement the operations performed by the access and mobility management function network element in the above various method embodiments.

[0351] As a solution, the chip system 3000 is used to implement the operations performed by the terminal device in the above various method embodiments.

[0352] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods executed by the terminal device and / or the access and mobility management function network element and / or the session management function network element in the above-mentioned method embodiments.

[0353] An embodiment of the present application also provides a computer program product, comprising computer program code or instructions. When the computer program code or instructions are executed on a computer, the computer implements the method executed by at least one of the terminal device, the access and mobility management function network element, and the session management function network element in the above-mentioned method embodiments.

[0354] An embodiment of the present application also provides a communication system, including the aforementioned terminal device, an access and mobility management function network element, and a session management function network element.

[0355] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0356] To facilitate understanding of the above embodiments provided in this application, the following points are explained:

[0357] 1) In this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0358] 2) The arrows or boxes indicated by dotted lines in the schematic diagrams in the accompanying drawings of this specification represent optional steps or optional modules.

[0359] 3) In the embodiments of this application, ordinal numbers such as "first" and "second" are used to distinguish multiple objects and are not used to define the size, content, sequence, timing, priority, or importance of the multiple objects. For example, the first message and the second message can be the same message or different messages, and such names do not indicate differences in content, size, application scenario, sender / receiver, priority, or importance between the two messages.

[0360] 4) In this application, descriptions such as "when...", "in the case of...", and "if" all mean that the device will perform corresponding processing under certain objective circumstances. They do not limit the time, nor do they require the device to perform judgment actions when implementing them, nor do they mean that there are other limitations.

[0361] 5) In this application, "indicate" or "used to indicate" can include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, and does not necessarily mean that the indication information carries A.

[0362] The indication methods involved in the embodiments of this application should be understood to encompass various methods that enable the party to be indicated to obtain information about the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or timing of these sub-information can be the same or different. This application does not limit the transmission method, for example.

[0363] In the embodiments of the present application, the "indication information" may be an explicit indication, i.e., a direct indication via signaling, or may be obtained based on parameters indicated by the signaling, in combination with other rules, other parameters, or by deduction. It may also be an implicit indication, i.e., based on a rule or relationship, or based on other parameters, or by deduction. This application does not impose specific limitations on this.

[0364] 6) The “protocol” referred to in this application may refer to a standard protocol in the field of communications, such as the fourth generation (4G) th generation, 4G) network, fifth generation (5 th This application does not limit the use of 5G network protocols, NR protocols, 5.5G network protocols, and related protocols used in future communication systems.

[0365] 7) In this application, "communication" may also be described as "data transmission", "information transmission", "data processing", etc. "Transmission" includes "sending" and "receiving".

[0366] 8) In this application, "sending information to XX (device)" can be understood as the destination of the information being the device. This can include sending information directly or indirectly to the device. "Receiving information from XX (device)" can be understood as the source of the information being the device, which can include receiving information directly or indirectly from the device. The information may undergo necessary processing between the source and destination, such as format changes, but the destination can still understand the valid information from the source.

[0367] 9) The terms "comprise," "include," and "have," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0368] 10) In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Where a, b and c can be single or multiple, respectively.

[0369] 11) In this application, under the premise that there is no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.

[0370] It should be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for illustrative description, and the specific form of the devices is not limited in the embodiments of the present application. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.

[0371] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0372] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be described again here.

[0373] 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 schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0374] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0375] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0376] If the functions are implemented in the form of 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 the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or an RDMA link target node, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0377] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: Obtaining identifiers of M non-3rd Generation Partnership Project 3GPP network access nodes, the M non-3GPP network access nodes including a first node, the first node supporting simplified access traffic steering, switching, and splitting ATSSS-lite, where M is an integer greater than or equal to 1; Determining a first user plane function network element according to the identifier of the first node, where the first user plane function network element supports ASSSS-lite, and a connection can be established between the first user plane function network element and the first node; Sending address information of the first user plane function network element.

2. The method according to claim 1, characterized in that The M non-3GPP network access nodes include N nodes supporting ASSSS-lite, where N is an integer greater than or equal to 1, and 1≤N≤M; The method further comprises: The first node is determined from the N nodes supporting ATSSS-lite.

3. The method according to claim 2, characterized in that The method further comprises: Sending the identifier of the first node.

4. The method according to claim 2 or 3, characterized in that The determining the first node from the N nodes supporting ATSSS-lite includes: The first node is determined according to the location of the terminal device and / or the priority of the N nodes supporting ATSSS-lite.

5. The method according to any one of claims 1 to 4, characterized in that Before sending the address information of the first user plane function network element, the method further includes: Obtain address information of the first user plane function network element.

6. The method according to any one of claims 1 to 5, characterized in that The obtaining of the identifiers of the M 3GPP network access nodes includes: Receive identifiers of the M non-3GPP network access nodes from the terminal device.

7. The method according to claim 6, characterized in that The method further comprises: First indication information is received from an access and mobility management function network element, where the first indication information indicates that the first user plane function network element is determined according to identifiers of the M non-3GPP network access nodes.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: Obtain information about non-3GPP network access nodes that support ASSSS-lite within the service area of ​​the access and mobility management function network element.

9. A communication method, characterized in that: include: Obtaining identifiers of L non-3rd Generation Partnership Project 3GPP network access nodes, the L non-3GPP network access nodes including a first node that supports simplified access traffic steering, handover, and split ATSSS-lite, where L is an integer greater than or equal to 1; Sending identifiers of P non-3GPP network access nodes, where the P non-3GPP network access nodes belong to the L non-3GPP network access nodes, the P non-3GPP network access nodes include the first node, and 1≤P≤L; Address information of a first user plane function network element is received, where the first user plane function network element supports ASSSS-lite, and a connection can be established between the first user plane function network element and the first node.

10. The method according to claim 9, characterized in that The L non-3GPP network access nodes all support ASSSS-lite, The method further comprises: The P non-3GPP network access nodes are determined from the L non-3GPP network access nodes.

11. The method according to claim 10, characterized in that P is equal to 1, and the P non-3GPP network access nodes are the first nodes.

12. The method according to claim 9, characterized in that The method further comprises: receiving an identifier of the first node; Establish a connection with the first user plane function network element through the first node.

13. The method according to any one of claims 9 to 12, characterized in that The obtaining of the identifiers of the L non-3GPP network access nodes includes: A broadcast message is received from the L non-3GPP network access nodes, where the broadcast message includes identifiers of the L non-3GPP network access nodes.

14. The method according to any one of claims 9 to 13, characterized in that The obtaining of the identifiers of the L non-3GPP network access nodes includes: Receive the identifiers of the L non-3GPP network access nodes from an access and mobility management function network element.

15. The method according to claim 14, characterized in that Before receiving the identifiers of the L non-3GPP network access nodes from the access and mobility management function network element, the method further includes: Sending a first request message to the access and mobility management function network element, where the first request message is used to request obtaining information of non-3GPP network access nodes supporting ATSSS-lite within the service area of ​​the access and mobility management function network element.

16. The method according to any one of claims 9 to 11, characterized in that The obtaining of the identifiers of the L non-3GPP network access nodes includes: Receive identifiers of the L non-3GPP network access nodes from a unified data management network element.

17. The method according to claim 16, characterized in that The method further comprises: Send second indication information, where the second indication information indicates that the terminal device supports ASSSS-lite.

18. The method according to any one of claims 9 to 17, characterized in that The method further comprises: Send third indication information, where the third indication information instructs the access and mobility management function network element to select a session management function network element that supports ASSSS-lite.

19. A communication method, characterized in that: include: Obtaining identifiers of P non-3rd Generation Partnership Project 3GPP network access nodes, where the P non-3GPP network access nodes include a first node, the first node supports ATSSS-lite, and P is an integer greater than or equal to 1; Determine M non-3GPP network access nodes that support ASSSS-lite among the P non-3GPP network access nodes, where the M non-3GPP network access nodes include the first node, and 1≤M≤P; Sending the identifiers of the M non-3GPP network access nodes.

20. The method according to claim 19, wherein The sending the identifiers of the M non-3GPP network access nodes includes: Sending the identifiers of the M non-3GPP network access nodes to a session management function network element.

21. The method according to claim 20, characterized in that The method further comprises: Determine the session management function network element that supports ATSSS-lite.

22. The method according to any one of claims 19 to 21, characterized in that The method further comprises: Send a third indication message to instruct AMF to select a session management function network element that supports ATSSS-lite.

23. The method according to any one of claims 19 to 22, characterized in that The method further comprises: Send information about non-3GPP network access nodes supporting ASSSS-lite within the service area of ​​the access and mobility management function network element to the session management function network element.

24. A communication device, characterized in that: include: A unit for implementing the method of any one of claims 1 to 8; or a unit for implementing the method of any one of claims 9 to 18; or a unit for implementing the method of any one of claims 19 to 23.

25. A communication device, characterized in that: The method comprises a processor coupled to a memory, wherein the processor is configured to execute a computer program or instruction stored in the memory so as to cause the communication device to perform the method according to any one of claims 1 to 8, or the method according to any one of claims 9 to 18, or the method according to any one of claims 19 to 23.

26. A computer program product, characterized in that Contains instructions that, when executed on a computer, causing the method of any one of claims 1 to 8 to be performed; or, causing the method of any one of claims 9 to 18 to be performed; or, Such that the method of any one of claims 19 to 23 is performed.

27. A computer-readable storage medium, characterized in that The computer readable storage medium stores a computer program or instruction. When the computer program or instruction is executed, Performing the method according to any one of claims 1 to 8, or Performing the method according to any one of claims 9 to 18, or Perform the method according to any one of claims 19 to 23.

Images