Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The method comprises: sending a first session establishment request, wherein the first session establishment request carries first indication information, the first indication information indicating the establishment of a first type of session, and the first type of session being transmitted by means of a user plane for non-3GPP access; and establishing a connection with a user plane network element on the basis of address information of the user plane network element, wherein the user plane network element supports the transmission of the first type of session, the address information of the user plane network element is sent on the basis of the first indication information, and the connection is used for the transmission of the first type of session. By means of requesting that a network side establishes a first type of session, which is transmitted by means of a user plane for non-3GPP access, establishing a connection with a user plane network element on the basis of address information of the user plane network element, and transmitting the first type of session by means of the user plane for non-3GPP access, the flexibility of a session management method for non-3GPP access can be improved, thereby reducing signaling overheads.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411516997.6, filed on October 28, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] Existing standards define traffic steering, switching, splitting (ATSSS) features. User equipment (UE) can access the core network and obtain services through both 3GPP and non-3GPP connections. When a UE accesses the network through two different access types, it can establish a multi-access protocol data unit (MAPDU) session to obtain services. Through multi-access sessions, the UE can dynamically select and switch access networks according to different network conditions and needs to achieve optimal network connectivity and performance.

[0004] In existing solutions, the UE can transmit sessions with the user plane through multipath transmission connections, such as connections established through the multipath transmission control protocol (MPTCP) function and the multipath quick user datagram protocol internet connections (MPQUIC) function. However, the existing solutions lack flexibility through multipath transmission connections. Summary of the Invention

[0005] This application provides a communication method and a communication device that can improve the flexibility of session management methods for non-3GPP access and save signaling overhead.

[0006] In a first aspect, a communication method is provided, which can be executed by a terminal device or by a component of the terminal device (such as a chip or circuit), and this application does not limit the scope of the method.

[0007] The method includes: sending a first session establishment request, the first session establishment request carrying first indication information, the first indication information indicating the establishment of a first type of session, the first type of session being transmitted by a user plane that is not accessed by 3GPP; establishing a connection between the user plane network element and the user plane network element based on the address information of the user plane network element, the user plane network element supporting the transmission of the first type of session, the address information of the user plane network element being sent according to the first indication information, and the connection being used to transmit the first type of session.

[0008] Based on the above scheme, the terminal device can request the network side to establish a first type of session. This first type of session is transmitted through the user plane of non-3GPP access, and the terminal device establishes a connection with the user plane network element based on the address information of the user plane network element. Transmitting the first type of session through the user plane of non-3GPP access can improve the flexibility of the session management method for non-3GPP access and save signaling overhead.

[0009] In some implementations of the first aspect, a second indication is received, which indicates that, if non-3GPP access is available, a connection is established between the user plane and the user plane network element through the non-3GPP access; and if it is determined that non-3GPP access is available, a connection is established between the user plane and the user plane network element through the non-3GPP access.

[0010] In some implementations of the first aspect, the second instruction information also indicates that the session is transmitted via the user plane of 3GPP access when non-3GPP access is unavailable.

[0011] Based on the above scheme, when the N3GPP side is available, a connection is established between the user plane and the user plane network element through the non-3GPP access. At this time, the 3GPP side does not establish data plane transmission. The terminal device can establish data plane transmission between the non-3GPP side and the user plane network element through the address information of the user plane network element. That is, when the non-3GPP side is unavailable, the 3GPP side can be used as a backup.

[0012] In some implementations of the first aspect, a user routing selection policy (URSP) is received, the URSP indicating an access type including a first access type, which is a non-3GPP access registered in 3GPP; and a first session establishment request message is sent according to the URSP.

[0013] In some implementations of the first aspect, the address information of the user plane network element is received. For example, the terminal device receives the address information of the user plane network element from the user plane network element through a session management network element.

[0014] In some implementations of the first aspect, the address information of the access device is obtained, and the access device stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

[0015] In some implementations of the first aspect, the first session establishment request includes the address information of the access device, and a connection is established between the access device and the user plane network element, wherein the access device is used to receive the address information of the user plane network element.

[0016] Based on the above scheme, the terminal device can establish a connection between the access device and the user plane network element, thereby improving the security of the address information of the user plane network element during the session connection establishment process.

[0017] Secondly, a communication method is provided, which can be executed by a session management network element or by a component of the session management network element (such as a chip or circuit), and this application does not limit the method.

[0018] The method includes: receiving a session creation request, the session creation request carrying first indication information, the first indication information indicating the establishment of a first type of session, the first type of session being transmitted by a user plane not accessed by 3GPP; and sending address information of a user plane network element according to the first indication information, the address information of the user plane network element being used to establish a connection with the user plane, the connection being used to transmit the first type of session, the user plane network element supporting the transmission of the first type of session.

[0019] Based on the above scheme, the session management network element can allocate user plane network element address information to the terminal device according to the first indication information carried in the session creation message, so that the terminal device can establish a connection with the user plane network element according to the address information of the user plane network element, and transmit the first type of session with the user plane network element through the non-3GPP access user plane.

[0020] In some implementations of the second aspect, a second instruction message is sent, indicating that a connection should be established with the user plane network element when non-3GPP access is available.

[0021] In some implementations of the second aspect, the second instruction information also indicates that the session be transmitted via the user plane of 3GPP access in the event that the non-3GPP access is unavailable.

[0022] In some implementations of the second aspect, the method further includes: sending a second session establishment request to the user plane network element according to the first indication information, the second session establishment request carrying third indication information indicating the allocation of address information for the user plane network element; and receiving the address information of the user plane network element.

[0023] In some implementations of the second aspect, the second session establishment request also carries fourth indication information, which indicates that the first information is set to zero. The first information is used to allocate resources for 3GPP access. The method further includes receiving a second session establishment response, which carries the first information set to zero.

[0024] Based on the above scheme, by sending the fourth indication information to the user plane network element, the user plane network element can be prevented from allocating resources for 3GPP access, so that the first type of session of the terminal equipment can be transmitted through the user plane of non-3GPP access, thereby improving the flexibility of non-3GPP access and saving signaling overhead.

[0025] In some implementations of the second aspect, the address information of the access device is sent to the user plane network element. The address information of the access device is used by the user plane network element to establish a connection with the terminal device. The access device stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

[0026] Based on the above scheme, by sending the address information of the access device to the user plane network element, a connection can be established between the user plane network element and the terminal device based on the access device, thereby improving the security of the address information of the user plane network element during the session connection establishment process.

[0027] Thirdly, a communication method is provided, which can be executed by a user plane network element or by a component of the user plane network element (such as a chip or circuit), and this application does not limit the method.

[0028] The method includes: receiving a second session establishment request, the second session establishment request being sent according to a session creation request, the session creation request indicating the establishment of a first type of session, the first type of session being transmitted by a user plane that is not accessed by 3GPP; and sending address information of the user plane network element according to the second session establishment request, the address information of the user plane network element being used to establish a connection with a terminal device, the connection being used to transmit the first type of session.

[0029] Based on the above scheme, the user plane network element can allocate the address information of the user plane network element to the terminal device based on the session establishment request, thereby enabling the terminal device to establish a connection with the user plane network element based on the address information of the user plane network element, and to transmit the first type of session through the user plane accessed by a non-3GPP network.

[0030] In some implementations of the third aspect, the second session establishment request carries third instruction information, which indicates the allocation of address information for the user plane network element, and the address information of the user plane network element is sent according to the third instruction information.

[0031] In some implementations of the third aspect, the second session establishment request also carries fourth indication information, which indicates that the first information is set to zero. The first information is used to allocate 3GPP access resources and send a second session establishment response, which carries the first information set to zero.

[0032] In some implementations of the third aspect, the second session establishment request also includes the address information of the access device to which the terminal device is connected, and sends the address information of the user plane network element to the access device based on the address information of the access device. The access device stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

[0033] Based on the above scheme, by sending the address information of the user plane network element to the access device, the user plane network element can establish a connection between the access device and the terminal device, which can improve the security of the address information of the user plane network element during the session connection establishment process.

[0034] Fourthly, a communication apparatus is provided, comprising a transceiver unit and a processing unit. The transceiver unit is configured to send a first session establishment request, the first session establishment request carrying first indication information indicating the establishment of a first type of session, the first type of session being transmitted by a user plane not accessed by 3GPP. The processing unit is configured to establish a connection with a user plane network element based on address information of the user plane network element, the user plane network element supporting the transmission of the first type of session, the address information of the user plane network element being sent according to the first indication information, and the connection being used to transmit the first type of session.

[0035] In some implementations of the fourth aspect, the transceiver unit is further configured to receive second indication information, which indicates that when the non-3GPP access is available, a connection is established between the user plane of the non-3GPP access and the user plane network element; the processing unit is specifically configured to: establish a connection between the user plane of the non-3GPP access and the user plane network element when it is determined that the non-3GPP access is available.

[0036] In some implementations of the fourth aspect, the second instruction information also indicates that the session is transmitted via the user plane of 3GPP access when non-3GPP access is unavailable.

[0037] In some implementations of the fourth aspect, the transceiver unit is also used to receive a user route selection policy (URSP), the access type indicated by the URSP including a first access type, which is a non-3GPP access registered in 3GPP; the transceiver unit is specifically used to send the first session establishment request message according to the URSP.

[0038] In some implementations of the fourth aspect, the transceiver unit is also used to: receive the address information of the user plane network element.

[0039] In some implementations of the fourth aspect, the transceiver unit is also used to: obtain the address information of the access device, which stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

[0040] In some implementations of the fourth aspect, the first session establishment request includes the address information of the access device, and the processing unit is specifically used to: establish a connection between the access device and the user plane network element, wherein the access device is used to receive the address information of the user plane network element.

[0041] Fifthly, a communication apparatus is provided, comprising a transceiver unit and a processing unit. The transceiver unit is configured to receive a session creation request, the session creation request carrying first indication information indicating the establishment of a first type of session, the first type of session being transmitted by a user plane not accessed by 3GPP. The processing unit is configured to send address information of a user plane network element according to the first indication information, the address information of the user plane network element being used to establish a connection with the user plane, the connection being used to transmit the first type of session, and the user plane network element supporting the transmission of the first type of session.

[0042] In some implementations of the fifth aspect, a second instruction message is sent, indicating that a connection should be established with the user plane network element when non-3GPP access is available.

[0043] In some implementations of the fifth aspect, the second instruction information also indicates that, in the event that the non-3GPP access is unavailable, the session should be transmitted via the user plane of 3GPP access.

[0044] In some implementations of the fifth aspect, the transceiver unit is specifically used to send a second session establishment request to the user plane network element according to the first instruction information, the second session establishment request carrying third instruction information indicating the allocation of address information for the user plane network element; and to receive the address information of the user plane network element.

[0045] In some implementations of the fifth aspect, the second session establishment request also carries fourth indication information, which indicates that the first information is set to zero. The first information is used to allocate 3GPP access resources. The transceiver unit is specifically used to receive the second session establishment response, which carries the first information set to zero.

[0046] In some implementations of the fifth aspect, the second session establishment request also includes the address information of the access device to which the terminal device is connected. The transceiver unit is also used to send the address information of the access device to the user plane network element. The address information of the access device is used by the user plane network element to establish a connection with the terminal device. The access device stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

[0047] A sixth aspect provides a communication apparatus comprising a transceiver unit and a processing unit. The transceiver unit is configured to receive a second session establishment request, which is sent according to a session creation request. The session creation request indicates the establishment of a first type of session, which is transmitted by a user plane not accessed by 3GPP. The processing unit is configured to send address information of the user plane network element according to the second session establishment request. The address information of the user plane network element is used to establish a connection with a terminal device, and the connection is used to transmit the first type of session.

[0048] In some implementations of the sixth aspect, the second session establishment request carries third indication information, which indicates the allocation of address information for the user plane network element, and the transceiver unit is specifically used to send the address information of the user plane network element according to the third indication information.

[0049] In some implementations of the sixth aspect, the second session establishment request also carries fourth indication information, which indicates that the first information is set to zero. The first information is used to allocate 3GPP access resources. The transceiver unit is also used to send a second session establishment response, which carries the first information set to zero.

[0050] In some implementations of the sixth aspect, the second session establishment request also includes the address information of the access device to which the terminal device is connected, and the processing unit is further configured to: send the address information of the user plane network element to the access device according to the address information of the access device, wherein the access device stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

[0051] A seventh aspect provides a communication device including a processor configured to implement any one of the first to third aspects and the methods in any possible implementation of the first to third aspects by executing a computer program (or computer-executable instructions) stored in a memory and / or by logic circuitry.

[0052] Optionally, the device may also include a memory, which may be deployed separately from the processor or centrally.

[0053] Optionally, the device also includes a communication interface, to which the processor is coupled. This communication interface may be a transceiver or an input / output interface.

[0054] In one implementation, the device is a terminal device, or a chip configured within a terminal device, or a logic module or software capable of implementing all or part of the functions of the terminal device. When the device is a chip, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as a processing circuit or logic circuit.

[0055] In another implementation, the device is a session management network element, or a chip configured within a session management network element, or a logic module or software capable of implementing all or part of the functions of the session management network element. When the device is a chip, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as a processing circuit or logic circuit.

[0056] In another implementation, the device is a user plane network element, or a chip configured within a user plane network element, or a logic module or software capable of implementing all or part of the functions of the user plane network element. When the device is a chip, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as a processing circuit or logic circuit.

[0057] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0058] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be, but is not limited to, a signal received and input by a receiver, and the signal output by the output circuit can be, but is not limited to, an output to a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, used as both input and output circuits at different times. This application does not limit the specific implementation of the processor and various circuits.

[0059] Eighthly, a chip system is provided, the processor being configured to execute a computer program or instructions in the memory, such that the chip system implements any one of the first to third aspects described above, and the method in any possible implementation of the first to third aspects.

[0060] A ninth aspect provides a communication system comprising: a terminal device, a session management network element, and a user plane network element, wherein the terminal device is configured to perform the methods of the first aspect and any possible implementation thereof; the session management network element is configured to perform the methods of the second aspect and any possible implementation thereof; and the user plane network element is configured to perform the methods of the third aspect and any possible implementation thereof.

[0061] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform any one of the first to third aspects described above, and the method in any possible implementation of the first to third aspects.

[0062] Eleventhly, a computer program product is provided, comprising a computer program (also referred to as code or instructions) that, when run, causes a computer to perform any one of the first to third aspects described above, and the method in any possible implementation of the first to third aspects.

[0063] The beneficial effects of aspects four through eleven above can be referred to the descriptions of the beneficial effects in aspects one through three, and will not be repeated here. Attached Figure Description

[0064] Figure 1 is a schematic diagram of the network architecture applicable to this application.

[0065] Figure 2 is another schematic diagram of the network architecture applicable to this application.

[0066] Figures 3 and 4 are schematic diagrams of the ATSSS architecture.

[0067] Figure 5 is a schematic diagram of a PDU session establishment process.

[0068] Figure 6 shows a session management method for N3GPP access.

[0069] Figure 7 is a schematic flowchart of a communication method 700 provided in this application.

[0070] Figure 8 is a schematic flowchart of a communication method 800 provided in this application.

[0071] Figure 9 is a schematic flowchart of a communication method 900 provided in this application.

[0072] Figure 10 is a schematic flowchart of a communication method 1000 provided in this application.

[0073] Figure 11 is a schematic diagram of the communication device 1100 provided in this application.

[0074] Figure 12 is a schematic diagram of the communication device 1200 provided in this application.

[0075] Figure 13 is a schematic diagram of the chip system 1300 provided in this application. Detailed Implementation

[0076] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0077] The technical solutions of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication system (UMTS), or other evolved communication systems. The technical solutions provided in this application can also be applied to future communication systems.

[0078] The technical solutions of this application embodiment can also be applied to machine-type communication (MTC), long-term evolution-machine (LTE-M) technology, device-to-device (D2D) networks, machine-to-machine (M2M) networks, Internet of Things (IoT) networks, or other networks. Among them, IoT networks may include, for example, vehicle-to-everything (V2X) networks. The communication methods in V2X systems are collectively referred to as vehicle-to-other-device (V2X), where X can represent anything. For example, V2X may include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.

[0079] Figure 1 is a network architecture applicable to an embodiment of this application. As shown in Figure 1, the various parts involved in this network architecture will be described below.

[0080] 1. User equipment (UE): also known as terminal equipment, is a device that provides voice / data connectivity to users, such as handheld devices with wireless connectivity, vehicle-mounted devices, etc. Currently, examples of terminals include: mobile phones, tablets, computers with wireless transceiver capabilities (such as laptops, PDAs, etc.), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future PLMNs, etc.

[0081] Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they can also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large sizes, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses. They also include devices focused on a specific application function that require the use of other devices, such as smart bracelets and smart jewelry for vital sign monitoring.

[0082] Furthermore, terminal devices can also be terminal devices in Internet of Things (IoT) systems. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network that enables human-machine interconnection and machine-to-machine interconnection. IoT technology can achieve massive connectivity, deep coverage, and low power consumption at the terminal level through technologies such as narrowband (NB).

[0083] 2. Radio Access Network (RAN): The access network provides network access functionality for authorized users in a specific area. Terminal devices can access the core network using access networks employing different access technologies, such as 3rd Generation Partnership Project (3GPP) and non-3GPP technologies. As an example, and not a limitation, access technologies may include, for example, NR, Evolved Universal Mobile Telecommunication System (UMTS) Terrestrial Radio Access Network (E-UTRAN), Multefire, 3GPP access technologies, non-3GPP access technologies, 4G cellular access technologies, 5G cellular access technologies, trusted or untrusted WiFi access technologies, fixed or wired access technologies, etc. No limitation is imposed on this aspect.

[0084] Access networks employing non-3GPP technologies may include, but are not limited to: WiFi networks, WLANs, MulteFire networks, wired networks (e.g., wireless and wireline convergence (WWC) networks), or home base station networks. Correspondingly, access network equipment employing non-3GPP technologies may include, for example: access points (APs), trusted WLAN interworking function (TWIF) network elements, trusted non-3GPP gateway functions (TNGFs), wireline access gateway functions (W-AGFs), access gateway functions (AGFs), broadband network gateways (BNGs), fixed-mobile interworking functions (FMIFs), non-3GPP interworking functions (N3IWFs), and so on.

[0085] Access networks employing 3GPP technology may include, but are not limited to, LTE networks, NR networks, 5G networks, or subsequent evolved mobile communication networks. Correspondingly, access network equipment employing 3GPP technology may include, for example, radio access network (RAN) equipment, g-NodeB, e-NodeB, and home-NodeB.

[0086] An access network that implements access network functions based on wireless communication technology can be called a RAN (Radio Access Network). The RAN is responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. The RAN provides access services to terminal devices, thereby completing the forwarding of control signals and user data between the terminal and the core network.

[0087] The RAN node in this application embodiment may also be referred to as access network equipment, network equipment, RAN entity or access node, etc., and constitutes part of the communication system to help the terminal achieve wireless access.

[0088] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a future communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

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

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

[0091] Unless otherwise specified, RAN nodes will be referred to as access network devices in this application.

[0092] 3. User plane function (UPF): Used for packet routing and forwarding, quality of service (QoS) processing of user plane data, user plane data forwarding, session / flow-level billing and statistics, bandwidth limiting, and other functions.

[0093] In 5G communication systems, this user plane network element can be a user plane function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can have other names; this application does not limit this.

[0094] 4. Data network (DN): A network used to provide data transmission.

[0095] In 5G communication systems, after a terminal device accesses the network, it can establish a Protocol Data Unit (PDU) session and access the Network Node (DN) through the PDU session. This allows it to interact with application function network elements (such as application servers) deployed within the DN. Depending on the DN accessed by the user, the network can select the UPF (User-Defined Node) accessing the DN as the PDU Session Anchor (PSA) according to network policies, and access the application function network elements through the PSA's N6 interface.

[0096] 5. Access and Mobility Management Function (AMF): Primarily used for mobility and access management, responsible for transmitting user policies between user equipment and policy control function (PCF) network elements. It can be used to implement other functions in the mobility management entity (MME) besides session management, such as access authorization / authentication.

[0097] In 5G communication systems, the access management network element can be an AMF (Access Management Element). In future communication systems, the access management network element can still be an AMF, or it can have other names; this application does not limit this.

[0098] 6. Session Management Function (SMF): Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for user equipment, selection of manageable user plane functions, endpoints for policy control and billing function interfaces, and downlink data notification.

[0099] In 5G communication systems, the session management network element can be an SMF network element. In future communication systems, the session management network element can still be an SMF network element, or it can have other names; this application does not limit this.

[0100] 7. Policy control function (PCF): A unified policy framework used to guide network behavior, providing policy rule information to control plane function elements (such as AMF, SMF, etc.).

[0101] In fourth-generation (4G) communication systems, this policy control network element can be a policy and charging rules function (PCRF) network element. In 5G communication systems, this policy control network element can be a PCF network element. In future communication systems, the policy control network element can still be a PCF network element, or it can have other names; this application does not limit this.

[0102] 8. Authentication Server Function (AUSF): This is a core network control plane element primarily responsible for authenticating and authorizing users to ensure their legitimacy. In 5G communication systems, this authentication server function can be an AUSF element, which supports access authentication from both 3GPP and non-3GPP providers.

[0103] 9. Data Management Network Element: Used to handle user equipment identification, access authentication, registration, and mobility management, etc.

[0104] In 5G communication systems, the data management network element can be a unified data management (UDM) network element; in 4G communication systems, the data management network element can be a home subscriber server (HSS) network element. In future communication systems, the unified data management network element can still be a UDM network element, or it can have other names, which are not limited in this application.

[0105] 10. Application Function (AF): Application function network elements can interact with the 5G system to access network open function network elements or interact with the policy framework for policy control, etc.

[0106] In 5G communication systems, this application network element can be an AF (Active Front-End) network element. In future communication systems, the application network element can still be an AF network element, or it can have other names; this application does not limit this. The AF network element primarily transmits the application's requests to the network side, such as QoS requirements or user equipment status event subscriptions.

[0107] For example, the AF can be a third-party functional entity or an application service deployed by the operator (such as Internet Protocol Multimedia Subsystem (IMS) voice call service). For third-party application functional entities, when they interact with the core network, authorization processing can also be performed through network exposure function (NEF) elements. For example, the third-party application function can directly send a request message to the NEF. The NEF determines whether the AF is allowed to send the request message. If the verification is successful, the request message will be forwarded to the corresponding PCF or UDM.

[0108] In addition, the network architecture may also include network slice selection function (NSSF) network elements, network exposure function (NEF) network elements, network function (NF) repository function (NRF) entities, and other network elements.

[0109] Figure 1 shows Nnssf, Nnef, Nudr, Nausf, Namf, Npcf, Nsmf, Nudm, and Naf as the service interfaces provided by NSSF, NEF, UDR, AUSF, NEF, AMF, PCF, SMF, UDM, and AF, respectively, used to invoke the corresponding service operations. N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the 3rd Generation Partnership Project (3GPP) standard protocol, and are not limited here.

[0110] In this network architecture, the N1 interface serves as the reference point between the terminal and the AMF entity; the N2 interface serves as the reference point between the (R)AN and the AMF entity, used for sending non-access stratum (NAS) messages; the N3 interface serves as the reference point between the (R)AN and the UPF entity, used for transmitting user plane data; the N4 interface serves as the reference point between the SMF entity and the UPF entity, used for transmitting information such as tunnel identification information for the N3 connection, data buffer indication information, and downlink data notification messages; and the N6 interface serves as the reference point between the UPF entity and the DN, used for transmitting user plane data.

[0111] It should be understood that the 5G system described above is merely an example, and the network architecture applicable to the embodiments of this application is not limited to this. Any network architecture that includes the functions of the various network elements described above is applicable to the embodiments of this application. The communication method provided in the embodiments of this application may also involve network elements not shown in FIG1, and of course, the communication method provided in the embodiments of this application may also include only some of the network elements shown in FIG1.

[0112] It should also be understood that the AMF, SMF, UPF, PCF, NEF, etc. shown in Figure 1 can be understood as network elements used to implement different functions, such as network slices that can be combined as needed. These network elements can be independent devices or integrated into the same device to implement different functions. They can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., cloud platform). This application does not limit the specific form of the above network elements.

[0113] It should also be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in future communication systems, some or all of the above-mentioned network elements may use the terminology from 5G, or they may use other names, etc.

[0114] It should also be understood that the interface names between the various network elements in Figure 1 are merely examples, and the interface names in actual implementations may be different; this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0115] The aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network elements or functions can be implemented by a single device, multiple devices working together, or a functional module within a single device; there are no limitations on this.

[0116] This application describes embodiments of the application using a 5G communication system as an example, but the technical solution of this application is not limited to a 5G system. When this solution is used in an LTE system, a 5G system, or a future communication system, each network element in the solution can be replaced with other network elements with corresponding functions, and this application does not limit this.

[0117] Figure 2 is another schematic diagram of the network architecture applicable to embodiments of this application.

[0118] Figure 2 illustrates the system architecture for accessing a 5G network via untrusted non-3GPP access technology. Untrusted non-3GPP access refers to non-3GPP access technologies not trusted by the operator, such as user-deployed WiFi. The untrusted non-3GPP access point is the UE's signal access point, serving as the first-hop node for the UE to access the 5G network. The non-3GPP interworking function (N3IWF) network element is the operator-deployed untrusted non-3GPP access gateway, its network topology equivalent to the RAN when the UE accesses the 5G network via 3GPP access technology. The N3IWF network element supports establishing Internet Protocol Security (IPsec) tunnels with the UE, supports N2 and N3 interfaces with the 5G core network, and can relay NAS signaling between the UE and the AMF.

[0119] In the network architecture shown in Figure 3, Y1 is the reference point between the UE and the untrusted non-3GPP access; Y2 is the reference point between the untrusted non-3GPP access and the N3IWF network element; and NWu is the reference point between the UE and the N3IWF network element.

[0120] The UE and N3IWF can transmit UE signaling and data encrypted through the IPsec tunnel protocol layer. Through the "IP in IP" transmission mechanism, the outer IP is set to the N3IWF IP. The untrusted non-3GPP access node forwards data based on the outer IP and forwards the data to the N3IWF.

[0121] Furthermore, the 5G core network will also support trusted non-3GPP access and / or wired network access. Trusted non-3GPP networks include trusted WLAN networks, and wired networks include fixed home network access. The network architecture for trusted non-3GPP access and wired network access is similar to that for untrusted non-3GPP access: for example, replacing the untrusted non-3GPP access gateway (N3IWF in Figure 2) with a trusted non-3GPP gateway function (TNGF) in the untrusted non-3GPP access network architecture results in a trusted non-3GPP access network architecture. Similarly, replacing the N3IWF with a wired network access gateway function (W-AGF) in the untrusted non-3GPP access gateway network architecture results in a wired network access network architecture.

[0122] It should be noted that the access network equipment between the UE and the aforementioned access gateway may include WLAN APs, wired network access network (FAN) equipment, switches, routers, etc., and there are no restrictions on this.

[0123] Figures 3 and 4 are schematic diagrams of the access traffic steering, switching, splitting (ATSSS) architecture.

[0124] Existing standards define the ATSSS feature, which allows a UE to access the core network and obtain services through both a 3GPP connection and a non-3GPP (N3GPP) connection. Specifically, when the UE is not within the coverage area of ​​its home public land mobile network (HPLMN), it can access the visited public land mobile network (VPLMN) via 3GPP and simultaneously access the HPLMN via non-3GPP. After accessing the network through these two different access types, the UE can establish a multi-access protocol data unit (MA PDU) session to obtain services. The MA PDU session allows the UE to simultaneously establish and maintain sessions through multiple access networks. Through multiple access sessions, the UE can dynamically select and switch access networks based on different network conditions and needs to achieve optimal network connectivity and performance.

[0125] As shown in Figure 3, when the UE accesses the same public land mobile network (PLMN), since 3GPP and N3GPP select the same AMF, the UE can establish an MA PDU session on both the 3GPP side and the N3GPP side by sending a session establishment request at the same time.

[0126] As shown in Figure 4, when a UE accesses two different networks simultaneously, the UE needs to initiate a session establishment process on both sides when establishing an MA PDU session, and use the same PDU session ID to indicate that it is the same session.

[0127] The anchor point of an MA PDU session is at the UPF, and specific rules issued by the network side determine how the session traffic is routed. When a UE accesses two different PLMNs, the session anchor point is at the UPF (H-UPF) of the HPLMN. Therefore, the VPLMN session uses a hierarchical routing (HR) architecture.

[0128] The network elements in Figures 3 and 4 can communicate with each other through the interfaces shown in the figures. Some interfaces can be implemented using service-oriented interfaces. For example, the UE and AMF network elements can interact through the N1 interface, and the interaction messages can be called N1 messages. The RAN and AMF network elements can interact through the N2 interface, which can be used to send non-access stratum (NAS) messages. The RAN and UPF can interact through the N3 interface, which can be used to transmit user plane data. The SMF network element and UPF can interact through the N4 interface, which can be used to transmit information such as tunnel identification information for N3 connections, data buffer indication information, and downlink data notification messages. The UPF and DN can interact through the N6 interface, which can be used to transmit user plane data. The PCF and SMF network elements can interact through the N7 interface, which can be used to issue protocol data unit (PDU) session granularity and service data stream granularity control policies. The N9 interface is used for communication between UPFs, such as the interface between the home-user plane function (H-UPF) connected to the DN and the visited-user plane function (V-UPF) connected to the RAN, for transmitting user plane data between UPFs. SMF network elements and AMF network elements can interact through the N11 interface. The N11 interface can be used to transmit PDU session tunnel information between the RAN and UPF, transmit control messages sent to the UE, and transmit radio resource control information sent to the RAN. The N16 interface is used for communication between SMFs, such as the interface between the visited-session management function (V-SMF) and the home-session management function (H-SMF). The relationships between other interfaces and various network elements are shown in Figures 3 and 4, and will not be detailed here for simplicity.

[0129] Among them, the UE and UPF can have multipath transmission control protocol (MPTCP) function, multipath quick user datagram protocol internet connections (MPQUIC) function, ATSSS-low-layer (ATSSS-LL) function and performance measurement function (PMF).

[0130] For ease of understanding, some terms used in this application will be explained below.

[0131] 1. The terminal device's home public land mobile network (H-PLMN) and visit public land mobile network (V-PLMN).

[0132] The H-PLMN of the terminal device can also be called the home network of the terminal device. In the embodiments of this application, the H-PLMN of the terminal device can be understood as: the PLMN where the contract data of the terminal device is located.

[0133] The V-PLMN of the terminal device can also be called the visited network of the terminal device. In the embodiments of this application, the V-PLMN of the terminal device can be understood as: the PLMN that the terminal device accesses by using the subscription data roaming of the H-PLMN.

[0134] 2. Traffic Switching

[0135] Session handover refers to the process in multipath transmission of switching a session from one path to another based on changes in network conditions or policies. When network conditions change, such as congestion or instability on a certain path, session handover can switch data traffic from the affected path to other available paths, thereby maintaining session continuity and stability while optimizing data transmission performance and reliability.

[0136] 3. Traffic Steering

[0137] Session offloading refers to the process of distributing data traffic across different paths or sub-streams according to specific strategies. Unlike session switching, session offloading is a process that occurs during session establishment or continues, diverting data traffic across multiple paths. Through session offloading, load balancing, bandwidth utilization optimization, and efficient use of network resources can be achieved. Specific offloading strategies can be adjusted based on factors such as path characteristics, network load, and latency to achieve optimal data transmission performance.

[0138] 4. User Routing Selection Policy (URSP) Rules

[0139] As an example, the contents of the URSP rules are shown in Table 1:

[0140] Table 1

[0141] Figure 5 shows the process of a UE requesting PDU session establishment through the N3GPP side.

[0142] The UE and N3IWF establish an IPsec security association (SA) for non-access stratum (NAS) signaling.

[0143] S501, the UE sends a PDU Session Establishment Request to the AMF.

[0144] For example, the message should be sent to the N3IWF via signaling that transmits NAS messages based on IPsec SA, and then the N3IWF should forward it transparently to the AMF in the 5GC. This step is specifically referred to as step 1 in 4.3.2.2.1 of standard 23.502.

[0145] S502a, AMF and other control plane (CP) and user plane (UP) functions execute the corresponding procedures.

[0146] Specifically, for non-roaming or local breakout (LBO) roaming situations, steps 2 to 11 in section 4.3.2.2.1 of standard 23.502 can be performed according to the 3GPP access PDU session establishment procedure.

[0147] For home routed (HR) roaming, steps 2 to 14 in section 4.3.2.2.2 of standard 23.502 can be performed according to the 3GPP access PDU session establishment procedure.

[0148] S502b and AMF send an N2PDU Session Request to N3IWF.

[0149] For example, an N2PDU Session Request is used to establish access resources for this PDU session. This may include a QoS profile(s) and associated Quality Flow Indicator (QFI), PDU session ID, and a PDU session establishment accept message.

[0150] S503 and N3IWF determine the number of IPsec Child Security Associations (IPsec Child SAs) to be established.

[0151] For example, N3IWF determines the number of IPsec Child SAs to be established and the QoS policy associated with each IPsec Child SA based on its own policies and configurations, as well as the Quality of Service (QoS) policy received in S502b.

[0152] For example, N3IWF can determine to establish an IPsec Child SA and associate all QoS policies with that IPsec Child SA. In this case, all QoS flows of the PDU session will be transmitted through a single IPsec Child SA.

[0153] S504a and N3IWF send an Internet Key Exchange (IKE) Create_Child_SA Request to the UE.

[0154] For example, N3IWF sends an IKE Create_Child_SA Request to the UE according to the IKEv2 specification to establish the first IPsec Child SA for the PDU session.

[0155] The IKE Create_Child_SA Request can instruct the requested IPsec Child SA to operate in tunnel mode. This request may include a 3GPP-specific Notify payload containing: (a) the QFI associated with this IPsec Child SA, (b) the PDU session identifier associated with this IPsec Child SA, (c) optionally, the differentiated services code point (DSCP) value associated with this IPsec Child SA, (d) optionally, the default IPsec Child SA indication, and (e) optionally, other QoS information associated with this IPsec Child SA (refer to 4.12a.5 of standard 23.502). The 3GPP-specific Notify payload also includes UP_IP_ADDRESS.

[0156] S504b, UE sends an IKE Create_Child_SA response to N3IWF.

[0157] If the UE accepts the new IPsec Child SA, the UE sends an IKE Create_Child_SA response according to the IKEv2 specification in standard RFC 7296[3]. During the establishment of the IPsec Child SA, no IP address is assigned to the UE.

[0158] In S504c-S504d, if in S503 the N3IWF determines that multiple IPsec Child SAs should be established for the PDU session, then additional IPsec Child SAs should be established. The N3IWF sends an IKE Create_Child_SA Request to the UE (S504c), and optionally the UE sends an IKE Create_Child_SA response to the N3IWF.

[0159] Each IPsec Child SA is associated with one or more QFIs, optionally with a DSCP value, UP_IP_ADDRESS, and optionally with additional QoS information.

[0160] S505 and N3IWF send a PDU session establishment accept message to the UE.

[0161] After all IPsec Child SAs are established, the N3IWF forwards the PDU session establishment accept message received in step 2b to the UE via signaling the IPsec SA (refer to standard 23.502, 4.12.2.2).

[0162] S506 and N3IWF send N2PDU Session Response messages to AMF.

[0163] S507, AMF, and other CP and UP functions execute the corresponding processes.

[0164] For non-roaming or Local Breakout roaming scenarios, follow the 3GPP access PDU session establishment procedure and execute all procedures after step 14 in standard 23.502 4.3.2.2.1.

[0165] For home-routed roaming, follow the 3GPP access PDU session establishment procedure and execute all procedures after step 18 in 4.3.2.2.1 of standard 23.502.

[0166] S508a-S508b, QoS flow transmission.

[0167] When the UE transmits an uplink (UL) PDU, the UE determines the QFI associated with the UL PDU (by using the QoS rules of the PDU session) and encapsulates the UL PDU in a generic routing encapsulation (GRE) packet. The UE then forwards the GRE packet to the N3IWF via the IPsec Child SA associated with that QFI. The header of the GRE packet carries the QFI associated with the UL PDU. The UE encapsulates the GRE packet into an IP packet with its source address being the UE's "inner" IP address and its destination address being the UP_IP_ADDRESS associated with the IPsec Child SA.

[0168] When the N3IWF receives a downlink (DL) PDU via the N3, it uses the QFI and the PDU session identifier to determine the IPsec Child SA. Based on the selected IPsec Child SA, the N3IWF sends the DL PDU to the UE via the Nwu interface. The N3IWF encapsulates the DL PDU in a GRE packet and copies the QFI from the GRE packet header. The N3IWF can also include a Reflection QoS Indicator (RQI) in the GRE header, which the UE will use to enable reflection QoS. The N3IWF encapsulates the GRE packet into an IP packet with the source address being the UP_IP_ADDRESS associated with the IPsec Child SA and the destination address being the UE's "inner" IP address.

[0169] Figure 6 illustrates the session management method for N3GPP access with direct MPQUIC connection between the UE and UPF.

[0170] S601, the UE sends a PDU session establishment request message to the AMF.

[0171] For example, the PDU session establishment request message includes its supported ATSSS function (e.g., "Direct ATSSS via N3GPP access using MPQUIC function"), which may be network-supported and indicated to the UE during the registration process.

[0172] S602, AMF sends a PDU session creation request (Nsmf_PDUSession_Create Request) message to SMF.

[0173] The AMF selects an SMF that supports the specific ATSSS function indicated by the UE and sends an Nsmf_PDUSession_Create Request message, which carries a PDU session establishment request message.

[0174] S603, SMF and UDM interactive subscription retrieval or subscription for updates.

[0175] The interaction between SMF and UDM follows existing specifications.

[0176] S604. SMF replies to AMF with a PDU session creation response (Nsmf_PDUSession_Create Response).

[0177] S605, Session Management Policy Session Establishment between SMF and PCF (SM Policy Session Establishment).

[0178] For example, the SMF initiates an SM Policy Session Establishment and instructs the MA PDU session capability according to existing specifications.

[0179] For S606 and SMF, select UPF.

[0180] For example, the SMF selects a UPF that supports "direct ATSSS access via N3GPP using MPQUIC". The SMF can discover UPF capabilities through NRF or N4Association Establishment.

[0181] S607, SMF sends an N4 Session Establishment Request message to UPF.

[0182] This message may include information instructing the UPF to activate the ATSSS function. In this case, MPQUIC is indicated along with "Direct ATSSS via N3GPP access using MPQUIC".

[0183] S608, UPF sends an N4 Session Establishment Response message to SMF.

[0184] If a message from the SMF instructs the UPF to activate the MPQUIC function using "Direct ATSSS via non-3GPP access using MPQUIC", then the UPF allocates MPQUIC proxy information for the N3 Tunnel (3GPP access) and the Nx interface (non-3GPP access). That is, the UPF assigns separate IP addresses and ports for the MPQUIC proxy in the UPF to the N3 and Nx interfaces.

[0185] UPF also assigns the UE's "MPQUIC link-specific multipath" address / prefix for 3GPP access and provides it to SMF. UPF does not assign the UE's "MPQUIC link-specific multipath" address / prefix for non-3GPP access.

[0186] When the UE uses non-3GPP access, the assigned local IP address reaches the MPQUIC proxy through the non-3GPP access.

[0187] S609, SMF sends N1N2 message transfer request to AMF.

[0188] This includes receiving messages when establishing a PDU session.

[0189] S610, AMF sends a PDU session establishment accept message to UE.

[0190] The message contains the following information:

[0191] -3GPP access MPQUIC Proxy address information (IP address and port number)

[0192] -MPQUIC Proxy address information (IP address and port number) for N3GPP access

[0193] - Link-specific multipath IP addresses for 3GPP access, as described in Clause 5.32 of TS23.501. The MPQUIC function in the UE and the MPQUIC proxy function in the UPF shall use the "MPQUIC link-specific multipath" address / prefix to transmit service flows on 3GPP access, as described in Clause 5.32.6 of TS23.501.

[0194] The UE can use the local IP address assigned during non-3GPP access to reach the MPQUIC proxy.

[0195] S611. Continued PDU session establishment.

[0196] The remainder of the MA PDU session procedure is performed in accordance with TS23.502.

[0197] S612, MPQUIC connection established.

[0198] After the MA PDU session is established, it is determined that the UE has established at least one MPQUIC connection equal to the number of QoS flows in the MA PDU session, i.e., one MPQUIC connection per QoS flow, as described in TS23.501 and TS23.502. These MPQUIC connections are established via 3GPP access, allowing the UPF to associate MPQUIC connections with the PDU session / N3 tunnel.

[0199] As can be seen from the above, when a UE requests PDU session establishment through the N3GPP side, the method shown in Figure 6, compared to the method shown in Figure 5, does not rely on N3IWF, thus allowing operators to use N3GPP features without deploying additional network elements. However, in the MPQUIC direct connection scheme shown in Figure 6, establishing N3GPP data plane transmission requires transmission based on the established 3GPP side control plane and data plane. However, UEs accessing from the 3GPP side sometimes lack effective data transmission (e.g., for data security, effective signals are required to be transmitted only from the N3GPP side). Therefore, this MPQUIC direct connection scheme lacks flexibility.

[0200] In view of this, this application provides a communication method and a communication apparatus that can improve the flexibility of session management methods for N3GPP access and save signaling overhead. Furthermore, this solution can enhance the security of information transmission.

[0201] The methods provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the network architecture shown in Figure 1 above, and are not limited thereto.

[0202] Figure 7 is a schematic diagram of a communication method 700 provided in an embodiment of this application. Method 700 may include the following steps.

[0203] S710, the terminal device sends a first session establishment request to the session management network element. Correspondingly, the session management network element receives the first session establishment request message.

[0204] The first session establishment request (e.g., a PDU session establishment request message) can be used to request the establishment of a first type of session. For example, the first session establishment request can carry indication information #1 (an example of first indication information), which indicates the establishment of this first type of session. This first type of session is transmitted by user plane network elements accessed by N3GPP.

[0205] Optionally, depending on whether a 3GPP data plane needs to be established subsequently, the first type of session may include a type #1 session and a type #2 session.

[0206] For example, a Type #1 session is an MA PDU session transmitted via the N3GPP user plane (MA PDU session via non-3GPP UP only). That is, when both the 3GPP access user plane and the N3GPP user plane are available, this Type #1 session is transmitted only via the N3GPP access user plane. Alternatively, in the case of a request to establish a Type #1 session (an example of the first type), a 3GPP-side data plane can be subsequently established. This 3GPP-side data plane can serve as a backup, transmitting the Type #1 session if N3GPP access is unavailable.

[0207] Type #2 (another example of Type 1) sessions can be sessions transmitted only through the N3GPP user plane (N3GPP UP only). That is, in any case, this Type 1 session is transmitted only through the user plane accessed by N3GPP. In other words, when requesting the establishment of a Type #2 session, a 3GPP-side data plane may not be subsequently established; this Type #2 session is transmitted only through the user plane accessed by N3GPP.

[0208] The first session establishment request may also include the following information: session identifier (such as PDU session ID), request type, and access type (N3GPP).

[0209] For example, the terminal device can send the first session establishment request to the session management network element through the access and mobility management network element.

[0210] For ease of description, in the embodiments of this application, the access and mobility management network element can be an AMF network element or a functional module within an AMF network element, the session management network element can be an SMF network element or a functional module within an SMF network element, and the user plane network element can be a UPF network element or a functional module within a UPF network element. Further details will not be elaborated upon below.

[0211] Optionally, the first session establishment request carries information #1. This information #1 includes the address information of the access device.

[0212] The access device can be used for terminal devices to access the access gateway in N3GPP. There is no specific limitation on the access device. For example, the access device is a WLAN AP.

[0213] The address information of the access device can be used by the user plane network element to address the access device, thereby enabling the user plane network element to establish a connection with the terminal device based on the access device. For details, please refer to the description below.

[0214] For example, the access device stores a mapping relationship (denoted as mapping relationship #1) between the address information of the user plane network element and the identification information of the terminal device, meaning that the address information of the UPF can be considered as terminal device granularity. Therefore, the access device can send data from the user plane network element (e.g., a session of type #2) to the terminal device based on the address information of the user plane network element and the mapping relationship, and / or send data from the terminal device to the user plane network element based on the mapping relationship and the identification information of the terminal device.

[0215] The terminal device identification information may include the terminal device's address information, such as the terminal device's IP address; or, the terminal device identification information may include the terminal device's identifier. For example, the terminal device's identifier may be a globally unique temporary identifier (GUTI), a temporary mobile subscription identifier (TMSI), or a subscriber permanent identifier (SUPI), without restriction.

[0216] Optionally, before sending the first session establishment request message, the terminal device obtains information #2. This information #2 includes the address information of the access device; this information #2 may also include the address information of the terminal device (an example of the terminal device's identification information).

[0217] For example, the terminal device may request the information #2 from the access device, or the information #2 may be pre-configured in the terminal device, and the specific method of obtaining the information #2 is not limited.

[0218] Optionally, prior to S710, the method further includes: the policy control network element sending a user route selection policy (URSP) (denoted as URSP#1) to the terminal device. Accordingly, the terminal device receives the URSP#1.

[0219] This URSP is used by the terminal device to select a network slice. The access type indicated by this URSP includes a first access type, which is an N3GPP access registered in 3GPP. In S710, the terminal device can send a first session establishment request to the session management network element by sending the first session establishment request message to the session management network element according to URSP#1. That is, upon receiving URSP#1, the terminal device requests the session management network element to establish a session of this first type.

[0220] S720: The terminal device establishes a connection with the user plane network element based on the address information of the user plane network element.

[0221] In the first possible implementation, the terminal device receives the address information of the user plane network element and establishes a connection with the user plane network element based on the address information of the user plane network element.

[0222] For example, upon receiving the first session establishment request, the SMF instructs the UPF to allocate the address information of the UPF and sends the address information of the UPF to the terminal device. That is, the SMF can determine the address information of the UPF according to the indication information #1 carried in the first session establishment request, specifically including requesting the UPF to allocate the address information of the UPF according to the indication information #1 and sending the address information of the UPF to the UE.

[0223] Specifically, upon receiving the first session establishment request, the SMF can send a second session establishment request (e.g., an N4 session establishment request message) to the UPF based on indication information #1. This second session establishment request can carry indication information #2, which indicates the allocation of address information for the user plane network element; the UPF allocates and sends its address information to the SMF based on this indication information #2.

[0224] Specifically, the instruction information #2 can directly indicate the address information to be allocated to the UPF, or it can implicitly indicate the address information to be allocated to the UPF. For example, in the case of the first type of session being "MA PDU session via non-3GPP UP only", the instruction information #2 can indicate the activation of the MA PDU session function; the UPF allocates the address information of the UPF according to the instruction to activate the MA PDU session function.

[0225] Optionally, the method further includes: the session management network element sending indication information #3 (an example of the second indication information) to the terminal device. Indication information #3 indicates that, when N3GPP access is available, a connection is established between the user plane accessed via N3GPP and the user plane network element; indication information #3 may also indicate that, when N3GPP access is unavailable, the session is transmitted via the user plane accessed via 3GPP. In other words, indication information #3 indicates that the session is transmitted via the user plane accessed via 3GPP only when N3GPP access is unavailable; otherwise, a connection is established between the user plane accessed via N3GPP and the user plane network element.

[0226] As an example, the session management network element may send the indication information #3 when the first type of session is "MA PDU session via non-3GPP UP only". That is, when the terminal device requests to establish a "MA PDU session via non-3GPP UP only" type session, the 3GPP access user plane is available, and the indication information #3 can make the first type of session only transmitted from the N3GPP access user plane.

[0227] For example, the terminal device can establish a connection with the UPF based on the address information of the UPF through the user plane accessed by N3GPP; thus, the terminal device can transmit the first type of session through the user plane accessed by N3GPP.

[0228] In the case of the first type of session being "MA PDU session via non-3GPP UP only", the terminal device can also determine whether N3GPP access is available. If N3GPP is available, the terminal device can transmit the first type of session via the user plane of N3GPP access. Alternatively, if N3GPP access is unavailable, the terminal device can transmit the first type of session via the user plane of 3GPP access.

[0229] In this example, the connection can be a multipath transport connection. This multipath transport connection can be established using the Multipath Transmission Control Protocol (MPTCP) or Multipath Quick User Datagram Protocol Internet Connections (MPQUIC) functionality.

[0230] Based on the above scheme, when N3GPP access is available, the 3GPP side does not need to establish data plane transmission. The terminal device can establish data plane transmission between the N3GPP side and the UPF through the address information of the UPF sent by the SMF; and when the N3GPP side is unavailable, the 3GPP side can be used as a backup.

[0231] In the second possible implementation, the terminal device establishes a connection with the user plane network element based on the access device. The access device receives the address information of the user plane network element; the specific details of the access device can be found in the description in S710. That is, the terminal device can establish a connection with the access device based on the address information of the access device, and the access device can establish a connection with the user plane network element based on the received address information of the user plane network element; the access device can forward data transmitted between the terminal device and the user plane network element according to the stored mapping relationship #1.

[0232] For example, after obtaining the address information of the access device, the terminal device sends the access device's address information to the SMF. For instance, the access device's address information may be carried in the first session establishment request, or in other uplink messages; this is not limited. Upon receiving the first session establishment request, the SMF sends a second session establishment request to the UPF. This second session establishment request may carry indication information #2 (see the description in the first possible implementation) and the access device's address information; the UPF allocates address information based on the indication information #2 and sends its own address information to the access device based on the access device's address information.

[0233] In other words, if the access device stores the mapping relationship #1, the access device can send data (e.g., a session of type #2) from the user plane network element to the terminal device based on the address information of the user plane network element and the mapping relationship #1, and / or send data from the terminal device to the user plane network element based on the mapping relationship #1 and the identification information of the terminal device.

[0234] Optionally, the aforementioned second session establishment request message also carries indication information #4 (an example of the fourth indication information). Indication information #4 indicates core network (CN) tunnel information (CN tunnel info) (an example of the first information).

[0235] CN tunnel info can be used to represent resources allocated for 3GPP access. For example, CN tunnel info can include tunnel identifiers, endpoint addresses, routing information, etc. For details on CN tunnel info, please refer to existing related descriptions. Setting CN tunnel info to zero can also be understood as not allocating resources for 3GPP access.

[0236] Accordingly, the UPF sets the CN tunnel info to zero based on the instruction information #4, and sends the zeroed CN tunnel info to the SMF. Further, the SMF sends downlink data packets associated with the N3 tunnel to the access network equipment.

[0237] As an example, the second session establishment request carrying indication information #4 may be in the case where the first type of session is "N3GPP UP only". That is, when the terminal device requests to establish an "N3GPP UP only" type session, the network side may not allocate resources for 3GPP access, so that the first type of session can be transmitted only from the user plane of N3GPP access.

[0238] It should be understood that before sending the second session establishment request to the UPF network element, the SMF can select a UPF that supports the transmission of the first type of session.

[0239] Based on the above scheme, when the terminal device requests the establishment of a PDU session through the N3GPP side, the control plane related to N3GPP is transmitted through 3GPP, and the N3GPP side only transmits service data, thereby saving signaling overhead. In addition, by transmitting the session only from the user plane accessed through N3GPP, the security of information transmission can be improved.

[0240] The communication method provided in this application is described in detail below with reference to specific network elements. Figure 8 is an exemplary flowchart of another communication method provided in an embodiment of this application. The method may include the following steps.

[0241] S801, PCF sends URSP#1 to UE via AMF.

[0242] For example, after the UE registration process is completed, the PCF sends URSP#1 to the AMF via the Namf_Communication_N1N2MessageTransfer message, and then the AMF sends URSP#1 to the UE via the NAS message.

[0243] Among them, the RSD of URSP#1 includes a new access type: N3GPP access registered in 3GPP.

[0244] URSP#1 may also include other information, which can be found in existing descriptions. For example, the current RSD access types for UE URSPs are: 3GPP, non-3GPP, and Multi-Access.

[0245] In S802, the UE sends a PDU Session Establishment Request message (an example of a first session establishment request message) to the AMF. Correspondingly, the AMF receives the PDU Session Establishment Request.

[0246] For example, when a UE requests to establish a PDU session, the PDU Session Establishment Request message is contained within the N1SM container of the NAS message. Exemplarily, the PDU session establishment request message may include: SUPI, PDU Session ID, Request SSC mode, etc. It should be understood that the specific content included in the PDU session establishment request can be found in existing protocols.

[0247] The PDU Session Establishment Request message also includes indication information #1, which indicates the session type to be established corresponding to the newly added access type. For example, indication information #1 indicates the establishment of a session with the session type "MA PDU session via non-3GPP UP only".

[0248] When a UE requests to establish a new session type from an AMF, the selected AMF must support the new session type "MA PDU session via non-3GPP Up only" through the NF policy in the NRF.

[0249] S803, the AMF sends a PDU session creation request (Nsmf_PDUSession_Create Request) message to the SMF. Correspondingly, the SMF receives the Nsmf_PDUSession_Create Request.

[0250] For example, after receiving a PDU session establishment request message from the UE, the AMF can select an SMF that supports "MA PDU session via non-3GPP Up only" to provide services to the UE based on the indication information #1 in the PDU session establishment request message, and send an Nsmf_PDUSession_Create Request to that SMF.

[0251] The Nsmf_PDUSession_Create Request carries instruction information #2, which indicates the creation of a session of type "MA PDU session via non-3GPP Up only". Instruction information #2 can be the same as instruction information #1, and there is no restriction.

[0252] S804, SMF and UDM interact.

[0253] This step is mainly used by the SMF to obtain the UE's subscription retrieval from the UDM.

[0254] In step S805, the SMF sends a PDU session creation response (Nsmf_PDUSession_Create Response) message to the AMF. The AMF then receives the Nsmf_PDUSession_Create Response.

[0255] S806, SMF initiates SM policy session establishment.

[0256] SMF initiates SM policy session establishment according to existing specifications.

[0257] For S807, select UPF for SMF.

[0258] In step S808, the SMF sends an N4 session establishment request message (an example of a second session establishment request message) to the UPF. The UPF then receives the N4 session establishment request.

[0259] This message may include activating the MP PDU session function.

[0260] S809, the UPF sends an N4 session establishment response message to the SMF. The SMF then receives the N4 session establishment response.

[0261] After receiving the N4session establishment request message from the SMF, the UPF can return an N4session establishment response. This response may include the UPF's IP address information.

[0262] S810, the SMF sends Namf_Communication_N1N2MessageTransfer to the AMF. Correspondingly, the SMF receives Namf_Communication_N1N2MessageTransfer.

[0263] The message may contain the IP address information of the UPF.

[0264] S811, the AMF sends an N2PDU session request to the RAN. Correspondingly, the RAN receives the N2PDU session request.

[0265] The message contains the IP address information of the UPF.

[0266] In step S812, the RAN sends a PDU session establish accept message to the UE. Correspondingly, the UE receives the PDU session establish accept message.

[0267] The message carries the IP address information of the UPF.

[0268] The message also carries instruction #3, which indicates that when the N3GPP side is available, the MA PDU session via non-3GPP UP only session establishment request is accepted, so that the session is transmitted only from the N3GPP side data plane; instruction #3 can also indicate that when the N3GPP side is unavailable, the session can be switched to be transmitted from the 3GPP side.

[0269] S813, the RAN sends an N2PDU session response to the AMF. Correspondingly, the RAN receives the N2PDU session response.

[0270] S814, the UE and UPF interact by establishing a session of type "MA PDU session via non-3GPP UP only" through the N3GPP user plane.

[0271] For example, a UE uses the MPTCP or MPQUIC function to establish a "MA PDU session via non-3GPP UP only" type session. The UE's MPTCP or MPQUIC function can communicate with the MPTCP or MPQUIC proxy function in the UPF through the user plane of non-3GPP access. Specifically, the network will assign the UE an IP address / prefix for the "MA PDU session via non-3GPP UP only" type session, as well as an additional IP address / prefix, called the "MPTCP / MPQUIC Link-Specific Multipath" address / prefix, associated with N3GPP access.

[0272] It should be noted that the above process is for establishing a "MA PDU session via non-3GPP UP only" type session. For details not described in detail, please refer to the existing protocol, Figures 5 and 6, which will not be elaborated here.

[0273] Figure 9 is an exemplary flowchart of another communication method provided in an embodiment of this application. The method may include the following steps.

[0274] S901, PCF sends URSP#1 to UE via AMF.

[0275] Among them, the RSD of URSP#1 includes a new access type: N3GPP access registered in 3GPP.

[0276] This step is described in S801.

[0277] In S902, the UE sends a PDU Session Establishment Request message to the AMF. The AMF then receives the PDU Session Establishment Request.

[0278] The PDU Session Establishment Request message carries indication information #1, which indicates the session type corresponding to the newly added access type. For example, indication information #1 indicates the establishment of a session with the session type "N3GPP UP only".

[0279] When a UE requests to establish a new session type from an AMF, the selected AMF must support the new session type "N3GPP Up only" through the NF policy in the NRF.

[0280] S903, the AMF sends an Nsmf_PDUSession_Create Request message to the SMF. Correspondingly, the SMF receives the Nsmf_PDUSession_Create Request.

[0281] The Nsmf_PDUSession_Create Request carries instruction information #2, which indicates the creation of a session of type "N3GPP Up only". Instruction information #2 can be the same as instruction information #1, and there is no restriction.

[0282] When the AMF requests the SMF to establish a new session type, the selected SMF needs to support the new session type "N3GPP Up only" through the NF policy in the NRF.

[0283] S904, SMF and UDM interact.

[0284] This step is mainly used by the SMF to obtain the UE's subscription retrieval from the UDM.

[0285] S905, the SMF sends an Nsmf_PDUSession_Create Response message to the AMF. Correspondingly, the AMF receives the Nsmf_PDUSession_Create Response.

[0286] S906, SMF initiates SM policy session establishment.

[0287] SMF initiates SM policy session establishment according to existing specifications.

[0288] For S907, the SMF should be UPF.

[0289] The selection of the UPF is also executed by the NF policy in the NRF. The UPF can register with the NRF or update to support new session types: 'N3GPP UP only'. The SMF uses the NRF to select the UPF that supports the 'N3GPP UP only' session type.

[0290] S908, the SMF sends an N4 session establishment request to the UPF. The UPF then receives the N4 session establishment request.

[0291] The message includes instruction #3, which instructs the UPF to perform IP address allocation and set the CN Tunnel Info allocation to zero. The CN tunnel info can represent the CN resource used by the RAN to send uplink data to the UPF.

[0292] S909, UPF performs IP address allocation according to instruction information #3, and sets CN Tunnel Info to zero.

[0293] When CN Tunnel Info is set to zero, data plane transmission will no longer be established on the 3GPP side; on the N3GPP side, the UE can establish data plane transmission with the UPF through the IP address information of the UPF sent by the SMF.

[0294] S910, the UPF sends an N4 session establishment response message to the SMF. Correspondingly, the SMF receives the N4 session establishment response message.

[0295] The message contains the requested UPF's IP address information and a zeroed CN Tunnel Info.

[0296] S911, the SMF sends an N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) to the AMF. Correspondingly, the AMF receives the Namf_Communication_N1N2MessageTransfer.

[0297] The message contains the UPF's IP address information and downlink data packets associated with the N3 tunnel (N3 tunnel with the DL packet).

[0298] S912, the AMF sends a PDU session establish accept message to the UE through the RAN.

[0299] The message includes the IP address information of the UPF.

[0300] S913, the UE and UPF interact by establishing a session of type "N3GPP UP only" through the N3GPP user plane.

[0301] For details, please refer to the description in S814.

[0302] Figure 10 is an exemplary flowchart of another communication method provided in an embodiment of this application. The method may include the following steps.

[0303] S1001, PCF sends UE route selection policy (URSP)#1 to UE through AMF.

[0304] Among them, the RSD of URSP#1 includes a new access type: N3GPP access registered in 3GPP.

[0305] This step is described in S801.

[0306] S1002, the UE sends request message #1 to the WLAN AP (an example of an access device). Accordingly, the WLAN AP receives the request message #1.

[0307] This request message #1 is used to request the IP address information of the WLAN AP and the IP address information of the UE (an example of terminal device identification information).

[0308] S1003, the WLAN AP sends response message #1 to the UE. Correspondingly, the UE receives response message #1.

[0309] The response message includes the IP address information of the WLAN AP and the IP address information of the UE.

[0310] S1004, the UE sends a PDU Session Establishment Request message to the AMF. Correspondingly, the AMF receives the PDU Session Establishment Request.

[0311] The PDU Session Establishment Request message carries indication information #1, which indicates the session type corresponding to the newly added access type. For example, indication information #1 indicates the establishment of a session with the session type "N3GPP UP only".

[0312] When a UE requests to establish a new session type from an AMF, the selected AMF must support the new session type "N3GPP Up only" through the NF policy in the NRF.

[0313] The message also includes the IP address information of the WLAN AP and the IP address information of the UE.

[0314] S1005, AMF selects to support SMF with "N3GPP UP only" session type.

[0315] The SMF can register with the NRF or update to support new session types: N3GPP UP only. The AMF can use the NRF to discover SMFs or configure an SMF ID that supports "N3GPP UP only" on a selected AMF that supports the new session type.

[0316] S1006, AMF sends an Nsmf_PDUSession_Create Request to SMF. Correspondingly, SMF receives the Nsmf_PDUSession_Create Request.

[0317] The message includes the “N3GPP UP only” session indication information #2, as well as the IP address information of the WLAN AP and the UE reported by the AMF to the SMF.

[0318] S1007, Interaction between SMF and UDM.

[0319] This step is mainly used by the SMF to obtain the UE's subscription retrieval from the UDM.

[0320] S1008, the SMF sends an Nsmf_PDUSession_Create Response message to the AMF. Correspondingly, the AMF receives the Nsmf_PDUSession_Create Response.

[0321] S1009, SMF initiates SM policy session establishment.

[0322] SMF initiates SM policy session establishment according to existing specifications.

[0323] S1010, SMF should be set to UPF.

[0324] SMF selects to support UPF with the "N3GPP UP only" session type.

[0325] S1011, the SMF sends an N4 session establishment request to the UPF. The UPF then receives the N4 session establishment request.

[0326] The message includes instruction #3, which instructs the UPF to perform IP address allocation (UE granularity) and set the CN Tunnel Info allocation to zero. The message also includes the IP address information of the WLAN AP and the IP address information of the UE.

[0327] S1012, according to instruction information #3, the UPF performs IP address allocation (UE granularity) and sets CN Tunnel Info to zero.

[0328] S1013, the UPF sends an N4 session establishment response message to the SMF. Correspondingly, the SMF receives the N4 session establishment response message.

[0329] The message contains a zeroed-out CN Tunnel Info.

[0330] S1014, the UPF sends the UPF's IP address information at the UE level to the WLAN AP.

[0331] That is, the WLAN AP can obtain the IP address information of the uplink channel UPF for data plane transmission on the N3GPP side.

[0332] S1015, the WLAN AP stores the mapping relationship between the UE identification information's IP address information and the UPF IP address information.

[0333] S1016, SMF sends N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) to AMF. Correspondingly, AMF receives Namf_Communication_N1N2MessageTransfer.

[0334] The message contains downlink data packets associated with the N3 tunnel.

[0335] S1017, the AMF sends a PDU session establish accept message to the UE through the RAN.

[0336] S1018, the UE and UPF interact by establishing a session of type "N3GPP UP only" through the N3GPP user plane.

[0337] For example, a UE can send a session of type "N3GPP UP only" to a UPF via a WLAN AP, and a UPF can send a session of type "N3GPP UP only" to a UE via a WLAN AP.

[0338] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 1 to 10. The communication apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 11 to 13. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0339] Figure 11 shows a schematic diagram of a communication device 1100 provided in an embodiment of this application. The device 1100 includes an interface unit 1110, which can be used to implement corresponding communication functions. The interface unit 1110 can also be referred to as a communication interface, a communication unit, or a transceiver unit.

[0340] Optionally, the device 1100 may further include a processing unit 1120, which can be used for data processing.

[0341] Optionally, the device 1100 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 1120 can read the instructions and / or data in the storage unit so that the device can perform the actions of different devices in the foregoing method embodiments.

[0342] In one possible design, the device 1100 can be a session management network element (such as an SMF) as described in the foregoing embodiments, or it can be a component of the session management network element (such as a chip). The device 1100 can implement the steps or processes corresponding to those executed by the session management network element in the above method embodiments. Specifically, the interface unit 1110 can be used to perform operations related to the transmission and reception of the session management network element in the above method embodiments; the processing unit 1120 can be used to perform processing-related operations of the session management network element in the above method embodiments.

[0343] In another possible design, the device 1100 can be a user plane network element in the foregoing embodiments, or a component of the user plane network element (such as a chip). The device 1100 can implement the steps or processes performed by the user plane network element corresponding to the method embodiments described above. Specifically, the interface unit 1110 can be used to perform operations related to the transmission and reception of the user plane network element in the method embodiments described above; the processing unit 1120 can be used to perform processing-related operations of the user plane network element in the method embodiments described above.

[0344] In another possible design, the device 1100 can be the terminal device in the foregoing embodiments, or it can be a component of the terminal device (such as a chip). The device 1100 can implement the steps or processes executed by the terminal device corresponding to the method embodiments described above. Specifically, the interface unit 1110 can be used to perform the transmit / receive related operations of the terminal device in the method embodiments described above; the processing unit 1120 can be used to perform the processing related operations of the terminal device in the method embodiments described above.

[0345] Figure 12 is a schematic block diagram of a communication device 1200 provided in an embodiment of this application. The device 1200 includes a processor 1210 coupled to a memory 1220. Optionally, it also includes a memory 1220. The memory 1220 is used to store computer programs or instructions and / or data, and the processor 1210 is used to execute the computer programs or instructions stored in the memory 1220, or to read the data stored in the memory 1220, to execute the methods in the above-described method embodiments.

[0346] Optionally, there may be one or more processors 1210.

[0347] Optionally, the memory 1220 may be one or more.

[0348] Alternatively, the memory 1220 can be integrated with the processor 1210, or it can be set separately.

[0349] Optionally, as shown in FIG12, the device 1200 further includes a transceiver 1230 for receiving and / or transmitting signals. For example, a processor 1210 is used to control the transceiver 1230 to receive and / or transmit signals. The transceiver 1230 may also be referred to as an interface.

[0350] As one approach, the device 1200 is used to implement the operations performed by the session management network element in the various method embodiments described above.

[0351] For example, processor 1210 is used to execute computer programs or instructions stored in memory 1220 to implement the relevant operations of the session management network element in the various method embodiments described above.

[0352] As an alternative, the device 1200 is used to implement the operations performed by the user plane network element in the various method embodiments described above.

[0353] For example, processor 1210 is used to execute computer programs or instructions stored in memory 1220 to implement the relevant operations of user plane network elements in the various method embodiments described above.

[0354] As an alternative, the device 1200 is used to implement the operations performed by the terminal device in the various method embodiments described above.

[0355] For example, processor 1210 is used to execute computer programs or instructions stored in memory 1220 to implement the relevant operations of the terminal device in the various method embodiments described above.

[0356] In implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware in the processor 1210 or by instructions in software form. The method disclosed in the embodiments of this application can be directly implemented by the hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory 1220, and the processor 1210 reads the information in memory 1220 and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0357] It should be understood that in the embodiments of this application, the processor may be one or more integrated circuits used to execute relevant programs to perform the method embodiments of this application.

[0358] A processor (e.g., processor 1210) may include one or more processors and be implemented as a combination of computing devices. The processor may include one or more of the following: microprocessor, microcontroller, digital signal processor (DSP), digital signal processing device (DSPD), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), programmable logic device (PLD), gating logic, transistor logic, discrete hardware circuitry, processing circuitry, or other suitable hardware, firmware, and / or combinations of hardware and software, for performing the various functions described in this disclosure. The processor may be a general-purpose processor or a special-purpose processor. For example, processor 1210 may be a baseband processor or a central processing unit (CPU). A baseband processor may be used to process communication protocols and communication data. A CPU may be used to enable the device to execute software programs and process data within the software programs. Furthermore, a portion of the processor may include non-volatile random access memory. For example, the processor may also store information about the device type.

[0359] The term "program" in this application is used broadly to refer to software. Non-limiting examples of software include: program code, program, subroutine, instructions, instruction sets, code, code segments, software modules, application programs, or software application programs, etc. Programs can run in a processor and / or computer to cause devices to perform the various functions and / or processes described in this application.

[0360] The memory (e.g., memory 1220) may store data required by the processor (e.g., processor 1210) when executing software. The memory may be implemented using any suitable storage technology. For example, the memory may be any available storage medium that the processor and / or computer can access. Non-limiting examples of storage media include: random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disc-ROM (CD-ROM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM), removable media, optical disc storage, magnetic disk storage media, magnetic storage devices, flash memory, registers, state memory, remotely mounted memory, local or remote memory components, or any other medium capable of carrying or storing software, data, or information and accessible by a processor / computer. It should be noted that the memory described in this article is intended to include, but is not limited to, these and any other suitable types of memory.

[0361] Memory (e.g., memory 1220) and processor (e.g., processor 1210) can be disposed separately or integrated together. Memory can be used to connect to the processor, enabling the processor to read information from, store, and / or write information to the memory. Memory can be integrated into the processor. Memory and processor can be disposed in an integrated circuit (e.g., the integrated circuit can be disposed in the UE or other network node).

[0362] Figure 13 is a schematic block diagram of a chip system 1300 provided in an embodiment of this application. The chip system 1300 (or may also be referred to as a processing system) includes logic circuitry 1310 and an input / output interface 1320.

[0363] The logic circuit 1310 can be a processing circuit in the chip system 1300. The logic circuit 1310 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 1300 to implement the methods and functions of the embodiments of this application. The input / output interface 1320 can be an input / output circuit in the chip system 1300, outputting processed information from the chip system 1300, or inputting data or signaling information to be processed into the chip system 1300 for processing.

[0364] As one approach, the chip system 1300 is used to implement the operations performed by the session management network element in the various method embodiments described above.

[0365] For example, logic circuit 1310 is used to implement processing-related operations performed by the session management network element in the above method embodiment; input / output interface 1320 is used to implement sending and / or receiving-related operations performed by the session management network element in the above method embodiment.

[0366] As an alternative, the chip system 1300 is used to implement the operations performed by the user plane network elements in the various method embodiments described above.

[0367] For example, logic circuit 1310 is used to implement processing-related operations performed by user plane network elements in the above method embodiments; input / output interface 1320 is used to implement transmission and / or reception-related operations performed by user plane network elements in the above method embodiments.

[0368] As an alternative, the chip system 1300 is used to implement the operations performed by the terminal device in the various method embodiments described above.

[0369] For example, logic circuit 1310 is used to implement processing-related operations performed by the terminal device in the above method embodiments; input / output interface 1320 is used to implement sending and / or receiving-related operations performed by the terminal device in the above method embodiments.

[0370] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by communication devices (such as session management network elements, user plane network elements, and terminal devices) in the above-described method embodiments.

[0371] This application also provides a computer program product containing instructions that, when executed by a computer, implement the methods described above, which are executed by communication devices (such as session management network elements, user plane network elements, and terminal devices).

[0372] This application also provides a communication system, which includes at least one of the functions described in the above embodiments, such as a session management network element, a user plane network element, and a terminal device.

[0373] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0374] In the above embodiments, 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.

[0375] In the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0376] It should be understood that the term "embodiment" used throughout this specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0377] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. All node and message names in this application are merely names set for the convenience of description, and the names in the actual network may be different. It should not be understood that this application limits 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 the method or equivalent substitution of this application and is within the protection scope of this application.

[0378] It should also be understood that in this application, “when…”, “if” and “if” all refer to the network element making a corresponding processing under certain objective circumstances, and are not time-limited, nor do they require the network element to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0379] It should be noted that in the embodiments of this application, "pre-setting" and "pre-configuration" can be implemented by pre-saving the corresponding code, table or other means that can be used to indicate relevant information in the device (e.g., terminal device). This application does not limit the specific implementation method, such as the preset rules and preset constants in the embodiments of this application.

[0380] In addition, the terms “system” and “network” are often used interchangeably in this article.

[0381] In this document, the terms "at least one of..." or "at least one of..." refer to all or any combination of the listed items. For example, "at least one of A, B, and C" can represent six possibilities: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, and A, B, and C exist simultaneously. "At least one" in this document means one or more. "More than one" means two or more.

[0382] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0383] Furthermore, the terms "of," "corresponding (relevant)," "corresponding," and "associate" are sometimes used interchangeably. It should be noted that their intended meanings are consistent unless otherwise emphasized. The terms "including," "containing," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0384] It should be understood that in the various embodiments of this application, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, they can be used to distinguish different information.

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

[0386] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0387] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0388] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0389] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0390] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: Send a first session establishment request, the first session establishment request carrying first indication information, the first indication information indicating the establishment of a first type of session, the first type of session being transmitted by a user plane that is not accessed by the third generation partner program; A connection is established between the user plane network element and the user plane network element based on the address information of the user plane network element. The user plane network element supports the transmission of the first type of session. The address information of the user plane network element is determined based on the first indication information. The connection is used to transmit the first type of session.

2. The method according to claim 1, characterized in that, The method further includes: Receive a second instruction message, which indicates that, if the non-3rd Generation Partner Program access is available, a connection shall be established between the user plane and the user plane network element through the non-3rd Generation Partner Program access; Establishing a connection with the user plane network element includes: If it is determined that the non-3rd Generation Partner Program access is available, a connection is established between the user plane accessed through the non-3rd Generation Partner Program and the user plane network element.

3. The method according to claim 2, characterized in that, The second instruction information also indicates that, in the event that the non-3rd Generation Partner Program access is unavailable, the session shall be transmitted via the user plane of the 3rd Generation Partner Program access.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Receive user routing policy URSP, wherein the access type indicated by the URSP includes a first access type, wherein the first access type is non-third generation partner program access registered in the third generation partner program; Sending the first session establishment request message includes: The first session establishment request message is sent according to the URSP.

5. The method according to any one of claims 1 to 4, characterized in that, Before establishing a connection between the address information based on the user plane network element and the user plane network element, the method further includes: Receive the address information of the user plane network element.

6. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Obtain the address information of the access device, wherein the access device stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

7. The method according to claim 6, characterized in that, The first session establishment request includes the address information of the access device, and the establishment of a connection between the address information of the user plane network element and the user plane network element includes: Based on the connection established between the access device and the user plane network element, the access device is used to receive the address information of the user plane network element.

8. A communication method, characterized in that, include: Receive a session creation request, the session creation request carrying first indication information, the first indication information indicating the establishment of a first type of session, the first type of session being transmitted by a user plane that is not accessed by the third generation partner program; According to the first instruction information, the address information of the user plane network element is sent. The address information of the user plane network element is used to establish a connection with the user plane. The connection is used to transmit the first type of session. The user plane network element supports the transmission of the first type of session.

9. The method according to claim 8, characterized in that, The method further includes: Send a second instruction message, which indicates that a connection should be established with the user plane network element if the non-3rd generation partner program access is available.

10. The method according to claim 8, characterized in that, The second instruction information also indicates that, in the event that the non-3rd Generation Partner Program access is unavailable, the session shall be transmitted via the user plane of the 3rd Generation Partner Program access.

11. The method according to any one of claims 8 to 10, characterized in that, The method further includes: A second session establishment request is sent to the user plane network element according to the first indication information. The second session establishment request carries third indication information, which indicates the allocation of address information for the user plane network element. Receive the address information of the user plane network element.

12. The method according to claim 11, characterized in that, The second session establishment request also carries fourth indication information, which indicates that the first information is set to zero. The first information is used to allocate resources for third-generation partner program access. The method further includes: Receive a second session establishment response, which carries the first information set to zero.

13. The method according to any one of claims 8 to 12, characterized in that, The session creation request also includes the address information of the access device to which the terminal device is connected, and the method further includes: The address information of the access device is sent to the user plane network element. The address information of the access device is used to establish a connection between the user plane network element and the terminal device. The access device stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

14. A communication method, characterized in that, Applied to user plane network elements, the method includes: Receive a second session establishment request, which is sent in accordance with a session creation request, the session creation request indicating the establishment of a first type of session, the first type of session being transmitted by a user plane that is not accessed by the third generation partner program; The address information of the user plane network element is sent according to the second session establishment request. The address information of the user plane network element is used to establish a connection with the terminal device. The connection is used to transmit the first type of session.

15. The method according to claim 14, characterized in that, The second session establishment request carries third indication information, which indicates the allocation of address information for the user plane network element. Sending the address information of the user plane network element according to the second session establishment request includes: The address information of the user plane network element is sent according to the third instruction information.

16. The method according to claim 14 or 15, characterized in that, The second session establishment request also carries fourth indication information, which indicates that the first information is set to zero. The first information is used to allocate resources for third-generation partner program access. The method further includes: Send a second session establishment response, which carries the first information set to zero.

17. The method according to any one of claims 14 to 16, characterized in that, The second session establishment request also includes the address information of the access device to which the terminal device is connected, and the step of sending the address information of the user plane network element according to the second session establishment request includes: The address information of the user plane network element is sent to the access device according to the address information of the access device. The access device stores the mapping relationship between the address information of the user plane network element and the identification information of the terminal device.

18. A communication device, characterized in that, The apparatus includes a unit or module for performing the method as described in any one of claims 1 to 17.

19. A communication device, characterized in that, include: A processor, the processor being configured to cause the apparatus to perform the method as described in any one of claims 1 to 17 by executing a computer program stored in a memory and / or by means of logic circuitry.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 17.

Images