Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus, for use in solving the problem of reduced transmission efficiency of a user equipment (UE) when accessing a network through at least two paths of the same access type. The method comprises: a first network element receives capability information from a first path, the capability information indicating that a UE supports multi-connectivity; on the basis of the capability information, the first network element allocates a first path identifier corresponding to the first path; and the first network element sends the first path identifier to the UE through the first path, such that the UE can determine the first path from among at least two paths by means of the first path identifier.

Description

Communication method and communication device

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

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

[0003] User equipment (UE) and user plane function (UPF) network elements can establish multiple access sessions to transmit the service flow data that needs to be sent through the third generation partnership project (3GPP) access network and / or non-3GPP access network at the same time to improve transmission efficiency.

[0004] Currently, multi-access sessions support transmission through a 3GPP access type path and a non-3GPP access type path, that is, the access network device in one path is an access network device of the 3GPP access type, and the access network device in the other path is an access network device of the non-3GPP access type. Therefore, the UE can distinguish different paths through different access types.

[0005] In the future, multi-access sessions will support transmission over multiple 3GPP paths or multiple non-3GPP paths. For example, when a UE accesses a network through two 3GPP access types, since the access network devices in both paths are 3GPP access type access network devices, the UE will randomly select at least one path to transmit data based on the 3GPP access type, resulting in reduced transmission efficiency.

[0006] Therefore, how to improve transmission efficiency for the same access type in multi-access sessions is an urgent problem to be solved. Summary of the Invention

[0007] The present application provides a communication method and a communication device, which enable a UE and a network to distinguish two paths of the same access type through different path identifiers, thereby improving transmission efficiency.

[0008] To achieve the above objectives, this application adopts the following technical solutions:

[0009] In a first aspect, a communication method is provided. The method may be executed by a first network element, or may be executed by a chip or circuit of the first network element, which is not limited in this application. For ease of description, the following description is based on an example of execution by the first network element.

[0010] The method includes: a first network element obtains capability information, where the capability information indicates that a communication device supports multiple connections, where the multiple connections include at least two paths of the same access type, and the at least two paths include a first path connecting the communication device and a first radio access network device; the first network element allocates a first path identifier corresponding to the first path according to the capability information; and the first network element sends the first path identifier to the communication device via the first path, where the first path identifier is used by the communication device to determine the first path among the at least two paths.

[0011] In the communication method provided based on the first aspect, the first network element obtains the capability information of the communication device to support multiple connections, so that the first network element allocates a first path identifier, and then sends the first path identifier to the communication device through the first path, so that the communication device can determine the first path among at least two paths through the first path identifier, and then the communication device and the network distinguish two paths of the same access type through different path identifiers, and transmit data through the path corresponding to the path identifier negotiated by the network and the communication device, thereby improving transmission efficiency.

[0012] In one possible implementation, the first network element receives capability information from the first path, such as by receiving capability information sent by the communication device. Alternatively, the first network element obtains capability information from subscription data of the communication device, such as by receiving subscription data from a data management network element, where the subscription data includes capability information of the communication device. Alternatively, when the first network element is a data management network element, the capability information of the communication device is obtained directly from the subscription data.

[0013] In a possible implementation manner, the first network element receives a registration request message from the first path, where the registration request message includes capability information.

[0014] In a possible implementation manner, the first network element sends a registration reception message to the communication device through the first path, and the registration reception message includes the first path identifier.

[0015] In one possible implementation, the first network element is an access and mobility management network element, which sends a first path identifier to a session management network element; receives a diversion rule including the first path identifier from the session management network element; and sends the diversion rule to a communication device, where the diversion rule is used by the communication device to determine a transmission path for a service flow, where the transmission path is one or more of at least two paths. By sending the first path identifier to the session management network element via the access and mobility management network element, the session management network element generates a diversion rule including the first path identifier. The communication device can then, based on the diversion rule corresponding to the service data, transmit the service data along the path corresponding to the path identifier, thereby improving transmission efficiency.

[0016] In one possible implementation, the access and mobility management network element selects a session management network element that supports multiple connections based on the capability information; the session management network element that supports multiple connections is a session management network element that supports generating a diversion rule that includes a first path identifier. A session management network element that supports multiple connections can be understood as a session management network element that can recognize newly added parameters, such as a path identifier, and supports generating a diversion rule that includes a path identifier.

[0017] In a possible implementation, the first network element is an access and mobility management network element, and the access and mobility management network element obtains information for distinguishing paths, where the information for distinguishing paths is different in at least two paths.

[0018] In one possible implementation, the access and mobility management network element obtains information for distinguishing paths, including: the access and mobility management network element receives information for distinguishing paths from the first wireless access network device; or the access and mobility management network element determines the information for distinguishing paths based on the first wireless access network device.

[0019] In one possible implementation, the access and mobility management network element stores the first path identifier and information used to distinguish paths. Alternatively, the access and mobility management network element stores an association between the first path identifier and the information used to distinguish paths. Thus, the corresponding information used to distinguish paths can be determined based on the first path identifier, and data can be sent to the corresponding path based on the information used to distinguish paths.

[0020] In a possible implementation, the access and mobility management network element selects a data management network element supporting multiple connections based on capability information; wherein the data management network element supporting multiple connections is a data management network element supporting storage of multiple contexts of the communication device.

[0021] In one possible implementation, the information used to distinguish paths is one or more of the following: location information, access technology type, registration type, and an identifier of the first radio access network device; wherein the location information indicates information about the access node through which the communication device accesses the network; the access technology type indicates the type of access technology used by the communication device to access the network via the first path; and the registration type indicates the registration type used by the communication device to register with the network via the first path. The access node information may include, for example, a radio access network device identifier or a cell identifier.

[0022] In one possible implementation, the first network element is a data management network element. Before the first network element assigns a first path identifier corresponding to the first path based on the capability information, the method further includes: the data management network element querying the contract data of the communication device; and assigning the first path identifier if the contract data of the communication device indicates that the communication device is authorized to access the network through multiple connections. The data management network element first queries the contract data of the communication device to confirm whether the communication device is authorized to access the network through multiple connections, thereby avoiding assigning a path identifier to a communication device that is not allowed to access the network through multiple connections.

[0023] In a possible implementation, the data management network element receives information for distinguishing paths from the access and mobility management network element, and the information for distinguishing paths is different in at least two paths.

[0024] In a possible implementation manner, the data management network element stores the first path identifier and information for distinguishing paths.

[0025] In a possible implementation, the data management network element sends the first path identifier and information for distinguishing paths to the session management network element and / or the data storage network element. The information for distinguishing paths is used by the session management network element to distinguish different paths.

[0026] In a possible implementation, the first network element is a session management network element, and the method further includes: the session management network element receiving information for distinguishing paths from the access and mobility management network element, where the information for distinguishing paths is different in at least two paths.

[0027] In a possible implementation manner, the session management network element stores the first path identifier and information used to distinguish paths.

[0028] In a possible implementation manner, the session management network element sends the first path identifier and information used to distinguish paths to the access and mobility management network element.

[0029] In a possible implementation, the session management network element generates a diversion rule including a first path identifier; sends the diversion rule to the communication device, and the diversion rule is used by the communication device to determine a transmission path for the service flow.

[0030] In a possible implementation, the diversion rule includes a priority of the first path, and the information used to distinguish the paths is used to determine the priority of the first path.

[0031] In one possible implementation, the session management network element selects a user plane network element that supports multiple connections based on capability information; wherein the user plane network element that supports multiple connections is a user plane network element that supports data diversion according to a diversion rule including a first path identifier.

[0032] In one possible implementation, the information used to distinguish the path is one or more of the following information: location information, access technology type, registration type, identification of the first wireless access network device, identification of the access and mobility management network element; wherein the location information indicates information of the access node through which the communication device accesses the network; the access technology type indicates the access technology type through which the communication device accesses the network through the first path; and the registration type indicates the registration type through which the communication device registers to the network through the first path.

[0033] In a possible implementation, the first network element is a policy control network element, and the method further includes: the policy control network element receiving information for distinguishing paths, where the information for distinguishing paths is different in at least two paths.

[0034] In a possible implementation, the first network element allocates the first path identifier corresponding to the first path according to the capability information, including: the policy control network element allocates the first path identifier corresponding to the first path according to the information distinguishing the paths and the capability information.

[0035] In a possible implementation manner, the policy control network element stores the first path identifier and information used to distinguish paths.

[0036] In a possible implementation manner, a policy control network element generates a policy rule or a routing rule, where the policy rule or the routing rule includes a first path identifier; and sends the policy rule or the routing rule to the communication device.

[0037] In a possible implementation manner, the access type corresponding to the at least two paths with the same access type is a 3rd Generation Partnership Project 3GPP access type or a non-3rd Generation Partnership Project 3GPP access type.

[0038] In a second aspect, a communication method is provided, which can be executed by a communication device, or by a chip or circuit of the communication device, which is not limited in this application. For ease of description, the following description is based on an example of execution by a communication device.

[0039] The method includes: a communication device receives a first path identifier through a first path connecting the communication device and a first wireless access network device, and receives a second path identifier through a second path connecting the communication device and a second wireless access network device; the communication device receives a diversion rule, the diversion rule including service flow information, and the first path identifier and / or the second path identifier; and the communication device determines a transmission path of a service flow corresponding to the service flow information based on the first path identifier and / or the second path identifier.

[0040] In the communication method provided based on the second aspect, the communication device receives a first path identifier through a first path and receives a second path identifier through a second path; then, the communication device transmits the business flow data through the path corresponding to the path identifier according to the diversion rule corresponding to the business flow and the first path identifier and / or the second path identifier in the diversion rule, thereby improving transmission efficiency.

[0041] In one possible implementation, before a communication device receives the first path identifier and the second path identifier, the communication device transmits capability information indicating that the communication device supports multiple connections, where the multiple connections include at least two paths of the same access type, where the at least two paths include the first path and the second path. By transmitting the capability information supporting multiple connections, the network assigns different path identifiers to the communication device based on the different paths through which the communication device accesses the network. For example, the network assigns the first path identifier to the first path and the second path identifier to the second path.

[0042] In one possible implementation, the communication device sends a first registration request message to the network via a first path, and / or sends a second registration request message to the network via a second path; the communication device receives a first path identifier via the first path, and receives a second transmission path identifier via the second path, including: the communication device receives a first registration acceptance message via the first path, the first registration acceptance message includes the first path identifier; and receives a second registration acceptance message via the second path, the second registration request acceptance message includes the second path identifier.

[0043] In one possible implementation, the diversion rules include the priority of the first path and / or the priority of the second path. Before the communication device determines the transmission path of the service flow based on the first path identifier and / or the second path identifier, the method also includes: the communication device determines the path identifier of the transmission path of the service flow based on the priority of the first path and / or the priority of the second path.

[0044] In one possible implementation, the communication device determines the transmission path of the business flow corresponding to the business flow information based on the first path identifier and / or the second path identifier, including: the communication device determines that the business flow corresponding to the business flow information is transmitted on the first path based on the first path identifier; and / or, determines that the business flow corresponding to the business flow information is transmitted on the second path based on the second path identifier.

[0045] In one possible implementation, the communication device stores a first path identifier and first path information, and a second path identifier and second path information; wherein the first path information is used by the communication device to determine the first path, and the second path information is used by the communication device to determine the second path.

[0046] In one possible implementation, the first path information is one or more of the following information: the access technology type corresponding to the first path, the registration type of the first path, the protocol stack used by the first path, the port corresponding to the first path, the interface corresponding to the first path, the link corresponding to the first path, or the identifier of the first wireless access network device; the second path information is one or more of the following information: the access technology type corresponding to the second path, the registration type of the second path, the protocol stack used by the second path, the port corresponding to the second path, the interface corresponding to the second path, the link corresponding to the second path, or the identifier of the second wireless access network device.

[0047] In a possible implementation manner, the access type corresponding to the at least two paths with the same access type is a 3rd Generation Partnership Project 3GPP access type or a non-3rd Generation Partnership Project 3GPP access type.

[0048] In a third aspect, a communication device is provided, comprising: a module for executing any of the communication methods described above for execution by the first network element, such as a transceiver module and a processing module. The transceiver module is configured to execute corresponding message sending and receiving actions, and the processing module is configured to execute all actions except sending and receiving messages.

[0049] Optionally, the communication device described in the third aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device can execute any communication method executed by the first network element in the above description.

[0050] In a fourth aspect, a communication device is provided, comprising: a module for executing any of the communication methods described above, such as a transceiver module and a processing module. The transceiver module is configured to execute corresponding message sending and receiving actions, and the processing module is configured to execute all actions except sending and receiving messages.

[0051] Optionally, the communication device described in the fourth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device can execute any communication method executed by the communication device described above.

[0052] In a fifth aspect, a communication system is provided, including: a first network element, the first network element being configured to execute the method in the above-mentioned first aspect and any possible implementation manner thereof.

[0053] Optionally, the communication system further includes a communication device, which is used to execute the method in the above-mentioned second aspect and any possible implementation manner thereof.

[0054] In the sixth aspect, a computer-readable storage medium is provided, which stores a computer program or code. When the computer program or code is run on a computer, the computer executes the method in any one of the above-mentioned first to second aspects and any possible implementation thereof.

[0055] In the seventh aspect, a chip is provided, comprising at least one processor, wherein the at least one processor is coupled to a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program from the memory, so that a device equipped with the chip system executes the method in any one of the above-mentioned first to second aspects and any possible implementation thereof.

[0056] The chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0057] In an eighth aspect, a computer program product is provided, comprising: a computer program code, which, when the computer program code is run on the computer, executes the method of any one of the first to second aspects above and any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application.

[0059] FIG2 is a schematic diagram of a registration process under a 3GPP access technology provided in an embodiment of the present application.

[0060] FIG3 is a schematic diagram of a multi-access session establishment process provided in an embodiment of the present application.

[0061] FIG4 is a possible form of providing a UE access to a network and / or establishing a multi-access session according to an embodiment of the present application.

[0062] FIG5 is another possible form of providing UE access to a network and / or establishing a multi-access session according to an embodiment of the present application.

[0063] FIG6 is a flow chart of a communication method 600 provided in an embodiment of the present application.

[0064] FIG7 is a flow chart of a communication method 700 provided in an embodiment of the present application.

[0065] FIG8 is a flow chart of a communication method 800 provided in an embodiment of the present application.

[0066] FIG9 is a flow chart of a communication method 900 provided in an embodiment of the present application.

[0067] FIG10 is a flow chart of a communication method 1000 provided in an embodiment of the present application.

[0068] FIG11 is a flow chart of a communication method 1100 provided in an embodiment of the present application.

[0069] FIG12 is a flow chart of a communication method 1200 provided in an embodiment of the present application.

[0070] FIG13 is a flow chart of a communication method 1300 provided in an embodiment of the present application.

[0071] FIG14 is a flow chart of a communication method 1400 provided in an embodiment of the present application.

[0072] FIG15 is a flow chart of a communication method 1500 provided in an embodiment of the present application.

[0073] FIG16 is a flow chart of a communication method 1600 provided in an embodiment of the present application.

[0074] FIG17 is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application.

[0075] FIG18 is a schematic structural diagram of a communication device 2000 provided in an embodiment of the present application.

[0076] FIG19 is a schematic structural diagram of a chip system 3000 provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

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

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

[0083] The terminal equipment portion may include UE 110, which is a device that provides voice and / or data connectivity to users. UE 110 may also be referred to as user equipment (UE). In this application, UE 110 is a device with wireless transceiver capabilities that can communicate with one or more CN devices via access network equipment (or access equipment) in (radio) access network (R)AN 120. UE 110 may also be referred to as an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, or user device. UE 110 may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water (e.g., on ships); or in the air (e.g., on airplanes, balloons, and satellites). UE 110 may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a smartphone, a mobile phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or the like. Alternatively, UE 110 may also be a handheld device with wireless communication capabilities, a computing device, or other device connected to a wireless modem, an in-vehicle device, a wearable device, a drone device, or a terminal in the Internet of Things, the Internet of Vehicles, a terminal of any form in a 5G network and future networks, a relay user device, or a terminal in a future evolved 6G network, etc. Among them, the relay user device may be, for example, a 5G residential gateway (RG). For example, UE 110 may be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The terminal device here refers to a 3GPP terminal. In this application, the terminal device may include a terminal device with one or more subscription data, or a terminal device including one or more Universal Subscriber Identity Modules (USIMs), or a terminal device including one or more UEs. For example, the terminal device may be called a Dual Steer device. In one possible implementation, the terminal device can access the network and perform registration separately using different subscription data to establish multiple connections or paths. The embodiments of the present application do not limit the type or category of the terminal device. For ease of explanation, the following description of the present application uses UE to refer to the terminal device as an example.

[0084] (R)AN 120 may include one or more access network elements or access network devices, and the interface between the access network device and the terminal device may be a Uu interface (or air interface, that is, the messages exchanged between the access network device and the terminal device may be called air interface messages). Of course, in future communications, the interface name may remain unchanged or may be replaced by other names, and this application is not limited to this. (R)AN 120 is a device that provides wireless communication functions for the terminal device 110, and can connect the terminal device to a node or device of a wireless network, and may also be called a network device. (R)AN 120 can be regarded as a subnetwork of the operator network, and is an implementation system between a service node in the operator network and the terminal device 110. For example, the terminal device 110 can connect to a service node of the operator network through (R)AN 120, thereby obtaining the services provided by the service node. (R)AN 120 includes but is not limited to: the next generation node base station (gNB) in the 5G system, the evolved node B (eNB) in the long term evolution (LTE), the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home base station (for example, home evolved node B, or home node B, HNB), the base band unit (BBU), the transmitting and receiving point (TRP), the transmitting point (TP), the small base station equipment, the mobile switching center, or the network equipment in the future network, etc.The access network device may also be a module or unit that performs the functions of a base station, such as a centralized unit (CU) and a distributed unit (DU); in a possible network structure, the CU may be used to support communications under protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); and the DU may be used to support communications under radio link control (RLC) layer protocols, media access control (MAC) layer protocols, and physical layer protocols. The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device. In systems using different wireless access technologies, the names of devices having access network device functions may be different. For the convenience of description, in all embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal device 110 are collectively referred to as access network devices or RAN for short. It should be understood that this document does not limit the specific type of access network device.

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

[0086] The data network DN 140 is usually a network outside the operator's network, such as a third-party network or an Internet service.

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

[0088] 1. UPF 130 is a gateway provided by the operator and serves as the gateway for communication between the operator network and DN 140. UPF 130 network functions include packet routing and transmission, packet inspection, service usage reporting, Quality of Service (QoS) processing, lawful interception, uplink packet inspection, downlink packet storage, and other user-plane-related functions. In future communication systems, the user plane function network element may still be a UPF network element, or may have other names, which are not limited in this application.

[0089] 2. PCF 131 is a control plane function provided by the operator. It mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network function, and is responsible for obtaining user subscription information related to policy decisions. Exemplarily, PCF 131 can be divided into two PCFs with different functions. For example, the PCF is divided into two functions: UE-PCF and AMF-PCF. Among them, UE-PCF can be used to generate UE policy (UE policy), that is, the policy sent to UE 110. The sending path is: UE-PCF--->AMF--->UE. At this time, AMF does not parse the content of UE policy, that is, AMF transparently transmits UE policy. AM-PCF can be used to generate AM policy, that is, the policy for access management sent to AMF. The sending path is: AMF-PCF--->AMF. Furthermore, AMF can also send part or all of the access management policy to RAN 120. In another example, PCF 131 can be divided into AM-PCF and SM-PCF. AM-PCF and SM-PCF can be located on the same PCF or different PCFs. AM-PCF is primarily responsible for access mobility policy control, for example, it can generate UE route selection policy (URSP). SM-PCF is primarily responsible for session management policy control, for example, it can generate policy and charging control rule (PCC rule). In future communication systems, the policy control function network element can still be a PCF network element, or it can have other names, which are not limited in this application.

[0090] 3. The UDM 132 is a control plane function provided by the operator and is responsible for storing information such as the subscriber permanent identifier (SUPI) of subscribers in the operator network, the publicly available general public subscription identifier (GPSI) of subscribers, and credentials. The SUPI is encrypted during transmission, and the encrypted SUPI is called a hidden subscriber subscription identifier (SUCI). This information stored by the UDM network function 132 can be used for authentication and authorization of UE 110 accessing the operator network. Subscribers of the operator network may specifically be users who use services provided by the operator network, such as users using China Telecom's SIM cards or China Mobile's SIM cards. The subscriber's credentials may be a small file containing a long-term key stored in a mobile phone SIM card or information related to mobile phone SIM card encryption, used for authentication and / or authorization. In future communication systems, the unified data management function network element may still be a UDM network element, or may have other names, which are not limited in this application.

[0091] 4. UDR 133 is a control plane function provided by the operator. It provides the UDM with the ability to store and retrieve subscription data, the PCF with the ability to store and retrieve policy data, and the user's NF group ID information. In future communication systems, the unified data repository function network element may still be a UDR network element, or may have other names, which are not limited in this application.

[0092] 5. AUSF 134 is a control plane function provided by the operator, which is usually used for level one authentication, that is, authentication between UE 110 (subscriber) and the operator network. After the AUSF network function 134 receives the authentication request initiated by the subscriber, it can authenticate and / or authorize the subscriber through the authentication information and / or authorization information stored in the UDM network function 134, or generate authentication and / or authorization information of the subscriber through the UDM network function 134. The AUSF network function 134 can feedback authentication information and / or authorization information to the subscriber. In future communication systems, the authentication server function network element can still be an AUSF network element, or it can have other names, which are not limited in this application.

[0093] 6. The AMF 135 is a control plane network function provided by the operator network. It is responsible for access control and mobility management for UE 110 accessing the operator network. For example, it includes functions such as mobility state management, allocating temporary user identities, authenticating and authorizing users, etc. In future communication systems, the access management network element may still be the AMF network element, or it may have other names, which are not limited in this application.

[0094] 7. SMF 136 is a control plane network function provided by the operator network. It is responsible for managing UE 110's protocol data unit (PDU) sessions (including session establishment, modification, and release). It is used for user plane function network element selection and reselection, terminal device Internet Protocol (IP) address allocation, and quality of service (QoS) control. A PDU session is a channel for transmitting PDUs. Terminal devices use PDU sessions to transfer PDUs to and from DN 140. SMF network function 136 is responsible for establishing, maintaining, and deleting PDU sessions. SMF network function 136 includes session management (e.g., session establishment, modification, and release, including tunnel maintenance between user plane function (UPF) 130 and (R)AN 120), selection and control of UPF network function 130, service and session continuity (SSC) mode selection, roaming, and other session-related functions. In future communication systems, the session management function network element may still be an SMF network element, or may have other names, which are not limited in this application.

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

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

[0097] It should be noted that in the architecture shown in Figure 1, the interface between the radio access network and the 5G core network is called the NG interface (not shown in the figure). gNBs are connected to each other via the Xn interface, and the gNB and 5GC are connected via the NG interface. The NG interface includes the NG-C interface and the NG-U interface. The NG-C interface is a control plane interface that connects the gNB and the AMF and transmits control plane data. The NG-U interface is a user plane interface that connects the gNB and the UPF and transmits user plane data. The main functions of the NG interface include but are not limited to: paging, UE context connection, UE mobility management, PDU session management, NAS signaling transmission, etc.

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

[0099] For ease of explanation, in the embodiments of this application, network functions (such as UPF 130 ... SMF 136) are collectively referred to as NFs. This means that the NFs described later in the embodiments of this application can be replaced with any network function. Furthermore, in the embodiments of this application, UE 110 is referred to as UE. This means that the UEs described later in the embodiments of this application can be replaced with terminal devices. Figure 1 only schematically illustrates some network functions, and the NFs described later are not limited to the network functions shown in Figure 1.

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

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

[0102] To facilitate understanding of the embodiments of the present application, some terms used in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

[0103] 1) Access type and access technology type:

[0104] The access type includes a 3GPP access type and a non-3GPP access type.

[0105] 3GPP access types include, but are not limited to, the following access technologies: LTE access technology (corresponding to 4G cellular networks), NR access technology (corresponding to 5G cellular networks), 3GPP-defined satellite access technology, or subsequently evolved cellular access technologies; 3GPP-defined satellite access technologies can be further categorized as low-orbit satellites, medium-orbit satellites, and geostationary satellites. A 3GPP access network refers to an access network with a 3GPP access type (also referred to as an access method).

[0106] Non-3GPP access types include, but are not limited to, the following access technologies: untrusted non-3GPP access technology (for example, accessing the core network through wireless access nodes purchased by individuals), trusted non-3GPP access technology (for example, accessing the core network through wireless access nodes deployed by operators), wireline access technology (for example, Broadband Forum (BBF) access technology, Cable access technology, etc.), IEEE802.11 access technology, and non-3GPP access technology connected through a standalone non-public network (SNPN). For example, access methods using non-3GPP access technology may include wired, Wireless Fidelity (WiFi), Bluetooth, ZigBee, and other access methods. A non-3GPP access network refers to an access network whose access type is a non-3GPP access type.

[0107] 2) Registration process, including but not limited to: registration process under 3GPP access type, registration process under untrusted non-3GPP access technology, registration process under trusted non-3GPP access technology, and registration process under wired access technology.

[0108] FIG2 shows a possible registration process of a UE under a 3GPP access type in the current technology.

[0109] Step 201: The UE sends an access network (AN) message to the RAN.

[0110] Among them, the AN message includes AN parameters and a registration request (Registration Request) message. The AN parameters include parameter information used by the RAN to select the AMF, and the parameter information may include one or more of the following: a globally unique AMF identifier (GUAMI), a public land mobile network (PLMN) identifier, a network identification (NID), etc. The registration request message includes a registration type (Registration Type), a UE identifier, etc. Among them, the registration type may be an initial registration or a mobility registration update, etc. The UE identifier may be a Subscription Concealed Identifier (SUCI) or a 5G globally unique temporary identity (5G-GUTI), etc.

[0111] Step 202: RAN selects AMF based on AN parameters.

[0112] The AN parameter is the AN parameter in the AN message in step 201 .

[0113] Step 203: The RAN sends the registration request message received in step 201 to the AMF selected in step 202.

[0114] Step 204: UE, AMF, AUSF, UDM, etc. interact to perform authentication and security procedures.

[0115] For example, first, the AMF selects the AUSF and sends an authentication request message to the AUSF. The AUSF performs the authentication process on the UE and obtains authentication data or information used for authentication from the UDM. After the authentication is completed, the AUSF sends the security anchor functionality (SEAF) key to the AMF. The AMF can derive the NAS security key based on the SEAF key.

[0116] The AMF then indicates to the UE that the authentication was successful. For example, the AMF sends a NAS Security Mode Command to the UE to activate NAS security. The NAS Security Mode Command includes an EAP-Success indication, indicating that the EAP-authentication and key agreement (EAP-AKA') authentication performed by the core network was successful. The RAN forwards the NAS Security Mode Command sent by the AMF to the UE and sends the NAS Security Mode Complete message sent by the UE to the AMF.

[0117] Step 205: AMF interacts with UDM to obtain the UE's subscription data.

[0118] The AMF can obtain relevant service information based on the UE's subscription data, such as at least one of the UE's service level, service traffic limit, and service fee. This information can be used to control the UE's service access and restriction, as well as billing and settlement.

[0119] Step 206: The AMF sends a NAS Registration Accept message to the RAN.

[0120] The NAS Registration Accept message may be included in the N2 message.

[0121] Step 207: The RAN forwards the NAS registration accept message sent by the AMF to the UE.

[0122] In one possible implementation, taking the dual-connection scenario as an example, both paths for the UE to connect to the network are 3GPP access types. The UE can register for 3GPP access types twice on the two paths respectively, thereby establishing connections for the two 3GPP access type paths.

[0123] 3) The process of determining the access type and access technology type.

[0124] As described in step 201 above, when the UE performs the registration process, it sends an AN message to the access network device.

[0125] The access network device may be a 3GPP access network device or a non-3GPP access network device. For example, the 3GPP access network device includes a radio access network (RAN) device. The non-3GPP access network device includes: a non-3GPP interworking function (N3IWF) network element, a trusted non-3GPP gateway function (TNGF) network element, a trusted WLAN interworking function (TWIF) network element, or a wireline access gateway function (W-AGF) network element, where W-AGF may also be referred to as AGF.

[0126] As described in step 203 above, the access network device sends a registration request message to the AMF. After the AMF receives the registration request message, the AMF can determine the access type and access technology registered by the UE based on the information of the access network device.

[0127] In one example, the AMF determines the access type registered by the UE based on the access network device. For example, if the registration request message is sent or forwarded by a 3GPP access network device (such as RAN), the AMF can determine that the access type registered by the UE is a 3GPP access type. For another example, if the registration request message is sent or forwarded by a non-3GPP access network device, such as N3IWF, TNGF, TWIF, W-AGF, etc., the AMF can determine that the access type used by the UE is a non-3GPP access type.

[0128] In another example, the AMF can further determine the access technology registered by the UE. For example, for the 3GPP access type, the AMF can further determine that the access technology is LTE access technology, NR access technology, satellite access technology, etc. based on the radio access network device information, such as the global radio access network node identifier (Global RAN Node IDs) associated with the N2 interface and the tracking area (tracking area) indicated by the radio access network device. For another example, when the 5G access network node has a global N3IWF node identifier (Global N3IWF Node ID), the access technology is untrusted non-3GPP. When the 5G access network node has a global TNGF node identifier (Global TNGF Node ID) or a global TWIF node identifier (Global TWIF Node ID), the access technology is trusted non-3GPP, etc.

[0129] In a multi-connectivity scenario, after a UE registers multiple times, the UE may register for one or more access types. For example, in a dual-connectivity scenario, the UE may register twice using the 3GPP access type. In this case, the UE registers for the 3GPP access type. In another example, the UE registers for the first time using the 3GPP access type and the second time using the non-3GPP access type. In this case, the UE registers for both the 3GPP access type and the non-3GPP access type.

[0130] 4) Single access PDU Session and Multi Access PDU Session:

[0131] In a single-access PDU session, the UE accesses the network through the user plane channel of only one access network device (which can be a 3GPP access network device or a non-3GPP access network device). For example, the UE can send uplink data to the UPF through the radio access network (RAN); and the UPF can send downlink data to the UE through the RAN. However, the user plane channel of the current multi-access PDU session can include two access network devices (a 3GPP access network device and a non-3GPP access network device), and the two access network devices are connected to the same UPF (or connected to the same UPF through another UPF). For example, the UE can send uplink data to the UPF through the RAN and / or the non-3GPP interworking function (N3IWF); and the UPF can send downlink data to the UE through the RAN and / or the N3IWF.

[0132] In a multi-access PDU session, whether the data to be sent is transmitted through the path of the 3GPP access network, the path of the non-3GPP access network, or the paths of both access networks is determined by the offload mode.

[0133] 5) MA PDU session establishment process:

[0134] As shown in Figure 3, a possible MA PDU session establishment process in the current technology is introduced. This example is applicable to the scenario where one path in the multi-access PDU session established by the UE is a 3GPP access type path and the other path is a non-3GPP access type path.

[0135] Step 301: The UE sends a PDU Session Establishment Request message to the AMF.

[0136] The PDU session establishment request is a NAS message that includes one or more of the following: request type, PDU session identifier, UE requested data network name (UE Requested DNN), slice information (S-NSSAI), etc. Among them, the request type is multi-access session request (MA PDU Request), indicating that the session establishment request message is used to request the establishment of a multi-access PDU session.

[0137] Step 302: AMF sends a PDU session creation session context request (Nsmf_PDU Session_CreateSMContext Request) message to SMF.

[0138] The PDU session creation session context request includes one or more of the following: UE identifier (e.g., SUPI), DNN requested by the UE, PDU session identifier, request type is a multi-access session request, access type, radio access technology type (RAT type), etc. The access type is the access type used by the UE to register with the core network, such as a 3GPP access type and a non-3GPP access type. The radio access technology type may include a wireless access technology or a wired access technology. The access technology that may correspond to the 3GPP access type and the access technology that may correspond to the non-3GPP access type have been introduced above.

[0139] Step 303 (optional): The SMF interacts with the UDM to obtain session management contract data. The session management contract data may include information about whether to allow or disallow the establishment of a multi-access PDU session. For example, the SMF may obtain the session management contract data using a subscription retrieval or subscription for updates method.

[0140] Step 304: SMF sends a PDU session creation session context response (Nsmf_PDU Session_CreateSMContext Response) message to AMF.

[0141] The PDU session creation session context response includes one or more of the following: session context identifier, cause, which is used to indicate the reason for the failure of PDU session creation, such as unknown PDU session type (Unknown PDU Session Type), indicating that the requested PDU session type is unknown or not supported.

[0142] Step 305 (optional): Execute PDU session authentication or authorization process.

[0143] Step 306: The SMF sends a policy association establishment request (SM Policy Association Establishment Request) message to the PCF.

[0144] The policy association establishment request message includes one or more of the following: UE identity (SUPI), DNN requested by UE, PDU session identifier, request type is multi-access session request, etc.

[0145] For example, if dynamic policy control and charging (PCC) rules are required, the SMF selects the PCF, and the SMF sends the policy association establishment request message to the PCF to establish a session policy association with the PCF.

[0146] Step 307: The PCF sends a policy association establishment response (SM Policy Association Establishment Response) message to the SMF.

[0147] The policy association establishment response message includes PCC rules. The PCC rules include multi-access PDU session control information, which includes but is not limited to one or more of the following: steering mode, steering functionality, threshold value, etc. The steering function can be a multipath transmission control protocol (MPTCP) function, and the threshold value can be a round trip time (RTT) threshold value and / or a packet loss rate threshold value.

[0148] Step 308: The SMF selects a suitable UPF.

[0149] Step 309a: The SMF sends an N4 Session Establishment Request message to the UPF.

[0150] Here, UPF is the UPF selected by SMF in step 308.

[0151] The N4 session establishment request includes N4 rules, which include but are not limited to one or more of the following rules: packet detection rule (PDR): contains information used to classify data packets arriving at the UPF; forwarding action rule (FAR): contains information on whether to forward, drop, or cache the service flow identified by the PDR; multi access rule (MAR): contains information on how to handle offloading, switching, or offloading in the MA PDU session; usage reporting rule (URR): contains information used to define how to count the service flows identified by the PDR and how to report measurements; quality of service enforcement rule (QER): contains information related to QoS enforcement for service flows identified by the PDR; session reporting rule (SRR): contains information on events requested for user plane function detection and reporting, which are not related to a specific PDR in the PDU session or usage measurement. Among them, MAR rules include but are not limited to one or more of the following: offloading mode, offloading function, and other information.

[0152] Step 309b: UPF sends an N4 Session Establishment Response message to SMF.

[0153] The N4 session establishment response includes tunnel information, such as tunnel information on the core network side (CN tunnels info).

[0154] Through steps 309a and 309b, the SMF establishes an N4 connection with the UPF selected in step 308.

[0155] Step 310: SMF sends an N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) message to AMF.

[0156] The N1N2 message transmission message includes one or more of the following: N2 interface session management information (N2 SM information), N1 interface session management container (N1 SM Container), access type and other information.

[0157] The N2 interface session management information includes, but is not limited to, one or more of the following: PDU Session ID (reported by the UE in step 301), core network tunnel information (CN Tunnel Info) (from a CN Tunnel Info in step 309b), etc. The SMF sends the core network tunnel information to the RAN through the AMF for the RAN to determine the destination address of the uplink data.

[0158] The N1 interface session management container includes but is not limited to one or more of the following: a PDU Session Establishment Accept message (which can be regarded as a reply / response to the PDU session establishment request in step 301), access traffic control, switching, and diversion (ATSSS) rules, and other session-related information. Among them, the ATSSS rules include but are not limited to one or more of the following: diversion mode, diversion function, threshold value, and other information. Subsequently, the information in the N1 interface session management container is sent by the SMF to the UE via the AMF, for example, the AMF sends it to the UE via a NAS message.

[0159] The access type indicates to the AMF the access type path through which the message is transmitted (for example, 3GPP access or non-3GPP access), so that the AMF can send the N1N2 message to the access network device corresponding to the access type path.

[0160] The AMF device may also send a response to the SMF device, indicating receipt of information from the SMF device.

[0161] Step 311: AMF sends an N2 PDU Session Request message to the RAN.

[0162] The AMF sends the N2 interface session management information (from step 310) and a NAS message (the NAS message needs to be sent to the UE) to the RAN. The NAS message includes the PDU Session ID (from the N2 interface session management information in step 310) and the N1 interface session management container (from step 310).

[0163] The AMF can determine whether this information is sent to a 3GPP access network device or a non-3GPP access network device based on the access type indicated by the SMF. For example, when the access type in step 310 is a 3GPP access type, the AMF sends the information to the RAN.

[0164] Step 312: The RAN establishes air interface resources with the UE, and the access network performs AN-specific resource setup to establish a data radio bearer (DRB).

[0165] The RAN sends the NAS message to the UE. The NAS message includes but is not limited to one or more of the following: PDU Session ID, PDU Session Establishment Accept message, and ATSSS rule. The ATSSS rule includes, for example, information such as offload mode, offload function, and threshold value.

[0166] Step 313: RAN sends an N2 PDU Session Response message to AMF.

[0167] The N2 PDU Session Response message includes the RAN access network tunnel information (AN tunnels info). This RAN access network tunnel information is used to inform the UPF of the destination of the downlink data (which can be understood as the destination address of the downlink data through the 3GPP transmission path). The RAN AN tunnels info will subsequently be sent to the UPF via the AMF and SMF. Please refer to steps 313, 314, and 315.

[0168] Step 314: AMF sends a PDU session update session context request (Nsmf_PDU Session_UpdateSMContext Request) message to SMF.

[0169] The PDU Session Update Session Context Request message includes the access network tunnel information (AN tunnels info) on the RAN side (from step 313 ).

[0170] Step 315: The SMF sends the access network tunnel information (AN tunnels info) on the RAN side to the UPF through the N4 Session Modification process.

[0171] Step 316: SMF sends a PDU session update session context response (Nsmf_PDU Session_UpdateSMContext Response) message to AMF.

[0172] The PDU Session Update Session Context Response message includes an indication of whether the update is successful or failed. If it fails, the SMF may also send a failure cause value to the AMF.

[0173] Step 317: SMF sends an N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) message to AMF.

[0174] The N1N2 message transmission message includes one or more of the following: N2 interface session management information (N2 SM information), N1 interface session management container (N1 SM Container), access type and other information.

[0175] The N2 interface session management information includes but is not limited to one or more of the following: PDU session identifier (PDU Session ID) (reported by the UE in step 301), tunnel endpoint information (CN Tunnel Info) on the core network side. SMF sends the tunnel information on the core network side to N3IWF through AMF, which is used by N3IWF to determine the destination address of the uplink data.

[0176] The AMF may also send a response to the SMF to indicate receipt of information from the SMF.

[0177] Step 318: AMF sends an N2 PDU Session Request message to N3IWF.

[0178] The request message carries the N2 SM information (from step 317). The AMF can determine whether this information is sent to a 3GPP access network device or a non-3GPP access network device based on the access type indicated by the SMF. For example, if the access type in step 317 is a non-3GPP access type, this information is sent to a non-3GPP access gateway device (e.g., N3IWF).

[0179] Step 319: The N3IWF establishes an Internet Protocol Security Protocol Sub-alliance (IPSec Child SA) with the UE for transmitting user plane data.

[0180] During this process, the N3IWF assigns the UE an IP address (e.g., UP_IP_ADDRESS) for the IPSec Child SA. When the UE sends uplink data, the destination IP address should be the UP_IP_ADDRESS, and the source IP address should be the assigned internal IP address, which is used to identify the UE within the network. The number of IPSec Child SAs established between the UE and the N3IWF, as well as the Quality of Service (QoS) flows transmitted by each IPSec Child SA, are determined based on N3IWF policies and configurations.

[0181] Step 320: N3IWF sends an N2 PDU session response message to AMF.

[0182] The N2 PDU session response message includes the access network tunnel information (AN tunnels info) on the N3IWF side. The access network tunnel information on the N3IWF side is used to notify the UPF of the destination of the downlink data (which can be understood as the destination address of the downlink data through the non-3GPP transmission path). The access network tunnel information on the N3IWF side will subsequently be sent to the UPF through the AMF and SMF. Please refer to steps 320, 321 and 322.

[0183] Step 321: AMF sends a PDU session update session context request (Nsmf_PDU Session_UpdateSMContext Request) message to SMF.

[0184] The PDU Session Update Session Context Request includes the access network tunnel information on the N3IWF side (from step 320).

[0185] Step 322: SMF sends the AN tunnel information on the N3IWF side to UPF through the N4 Session Modification process.

[0186] N4 session modification includes tunnel information (AN tunnels info) on the access network side of N3IWF side.

[0187] Step 323: SMF sends a PDU session update session context response (Nsmf_PDU Session_UpdateSMContext Response) message to AMF.

[0188] The response message includes an indication of whether the update is successful or failed. If it fails, the SMF may also send a failure reason value to the AMF.

[0189] FIG3 illustrates a process in which a session establishment process is first performed on the 3GPP access side (e.g., see steps 310 to 316 in FIG3 ), and then a session establishment process is performed on the non-3GPP access side (e.g., see steps 317 to 323 in FIG3 ). In another example, the session establishment process may be performed first on the non-3GPP access side, and then on the 3GPP access side. This process is similar to the above diagram and will not be described in detail.

[0190] Figure 3 illustrates an example of a UE sending a session establishment request message. In another example, the UE may send session establishment request messages on both the 3GPP side and the non-3GPP side. For example, between steps 316 and 317, a process similar to steps 301 and 302 may be performed again, which will not be described in detail.

[0191] 6) Policy and charging control rule (PCC rule)

[0192] PCC rules are generated by the policy control function (PCF), and mainly involve some policy information and charging information. For example, in step 307 of Figure 3, after the PCF generates the PCC rules, it will send them to the SMF. Based on the information in the PCC rules, the SMF can further generate other rules. For example, the SMF can generate ATSSS rules (to be introduced later) and N4 rules (to be introduced later) based on the information in the PCC rules, and send them to the UE in steps 310-312 of Figure 3 and to the UPF in step 309a of Figure 3 respectively. The PCC rules can include Multi-Access PDU (MA PDU) Session Control information, which allows the PCF to control one or more of the following: diversion mode, diversion function, diversion mode indication, threshold value, charging information, and usage monitoring information.

[0193] Traffic diversion modes include but are not limited to: Active Standby mode, Smallest Delay mode, Load-Balancing mode, and Priority-based mode. The following describes the mechanism of each traffic diversion mode:

[0194] Active Standby: When two transmission paths are available, one is designated as Active (3GPP access or non-3GPP access) and the other as Standby. When the Active path is available, all data for that service flow is transmitted to the peer end over the Active path. If the Active path is unavailable, all data for that service flow is switched to the Standby path for transmission.

[0195] Smallest Delay: Select the transmission path with the shortest delay to transmit the data of the service flow. In this mode, the UE or UPF needs to monitor the transmission delay of the path in real time. This can be achieved by the transport layer protocol (such as MPTCP) which has the function of detecting the round-trip time (RTT)), or by the performance measurement function (PMF) module in the UPF.

[0196] Load-Balancing: Business flow data is distributed proportionally to different transmission paths. The distribution ratio is determined by the load of multiple (two or even more) transmission paths in the network (for example, paths with heavier loads receive a smaller distribution ratio, while paths with lighter loads receive a larger distribution ratio).

[0197] Priority-based: Designate one of the transmission paths as a high-priority transmission path, and the other transmission paths as second-highest priority (or medium priority, low priority, etc.) transmission paths. When the high-priority transmission path is not congested, all data of the service flow is transmitted through the high-priority transmission path. When the high-priority transmission path is congested, part of the data of the service flow will be transmitted through the second-highest priority (or medium priority, low priority, etc.) transmission path, or any one or more of the remaining paths. When the high-priority transmission path is unavailable, all data of the service flow will be transmitted through the second-highest priority (or medium priority, low priority, etc.) transmission path, or any one or more of the remaining paths.

[0198] The offload function can be understood as which function is used to perform multi-path offload, such as the MPTCP function defined by 3GPP.

[0199] When the offload mode is load-balancing, the steering mode indicator can be autonomous load-balance or UE-assistance. Autonomous load-balance means that the UE or UPF can independently determine the offload ratio. UE-assistance means that the UE can independently determine the offload ratio and send the offload ratio to the UPF, allowing the UPF to send downlink data based on the offload ratio.

[0200] Thresholds, including but not limited to RTT thresholds and / or packet loss rate thresholds, can be used in conjunction with load-balancing or priority-based traffic diversion modes to assist in making decisions on how to divert traffic.

[0201] Billing information: In mobile communication networks, communication service providers need to bill users for their communication activities. The billing information in the MA PDU can record user communication activities, such as call duration, number of text messages, and data traffic, for billing purposes. Communication service providers can also bill for the paths along which service flows are transmitted.

[0202] Usage Monitoring Information: Mobile communication network resources are limited, and communication service providers need to allocate and manage them appropriately. The usage monitoring information in the MA PDU records user communication behavior, such as data traffic and bandwidth usage, to facilitate resource management and optimization. This information depends on the access path used by the service flow.

[0203] In addition, the MA PDU session control information may also include application descriptors, which are used to identify a service flow, thereby determining which offloading function and offloading mode should be adopted for the service flow.

[0204] 7) ATSSS Rules

[0205] The SMF generates ATSSS rules based on the PCC rules and sends them to the UE via the AMF. The ATSSS rules may include one or more of the following:

[0206] Rule identifier, used to uniquely identify the ATSSS rule.

[0207] Rule Precedence is used to determine the order of ATSSS rules.

[0208] Traffic descriptor is used to define the traffic flow. It can include one or more of the following information: Application descriptor, IP descriptor, and Non-IP descriptor. The application descriptor includes one or more application identifiers to identify the application that produces the traffic flow. The IP descriptor includes one or more quintuples to identify the destination of the IP traffic flow. The non-IP descriptor includes one or more descriptors to identify the destination of non-IP traffic flows, such as Ethernet data packets.

[0209] The Access Selection Descriptor (ASD) defines the access selection process. It includes the following information: offload mode, offload mode indication, threshold, and offload function. For more information, refer to the PCC rules.

[0210] 8) System architecture for multi-access PDU sessions:

[0211] Currently, a multi-access PDU session supports transmission through two paths: a 3GPP path and a non-3GPP path.

[0212] However, in the future, multi-access PDU sessions will support transmission via multiple paths with 3GPP access type and / or multiple paths with non-3GPP access type. In this case, different paths cannot be accurately identified by access type alone (e.g., 3GPP access type, non-3GPP access type). For example, if both paths are 3GPP access paths, the AMF cannot accurately determine which 3GPP access network device to send information to based solely on the access type (e.g., 3GPP access type) parameter.

[0213] Figure 4 introduces a possible form of UE accessing the network and / or establishing a multi-access session: the UE accesses the PLMN through 3GPP transmission path 1 (for example, cellular network 1 (RAN1)) and the core network, that is, the UE accesses the PLMN through the 3GPP access type. And the UE accesses the PLMN through 3GPP transmission path 2 (for example, cellular network 2 (RAN2)) and the core network. Therefore, from the perspective of the core network, the UE accesses the PLMN through two 3GPP transmission paths. If the UE establishes a multi-access session through the two paths, then the multi-access session is a path of two 3GPP access types. It should be noted that in addition to accessing the PLMN, the UE can also access a non-public network (NPN), such as a public network integrated non-public network (PNI-NPN).

[0214] Figure 5 illustrates another possible method for UE accessing the network and / or establishing a multi-access session: the UE accesses the core network via 3GPP transmission path 1 (e.g., satellite base station) through a gNB, and the UE accesses the core network via 3GPP transmission path 2 (e.g., terrestrial cellular network (gNB)). From the core network's perspective, the UE accesses the PLMN via two 3GPP transmission paths. If the core network (e.g., AMF) can distinguish between satellite access technology and terrestrial cellular access technology, the AMF can distinguish between the two paths based on the access technology. However, from the perspective of current registration management, mobility management, and session management, both paths belong to the same 3GPP access type.

[0215] According to the above-mentioned possible new forms of UE accessing the network and / or establishing multiple access sessions, that is, the paths for UE accessing the network and / or establishing multiple access sessions can be multiple paths belonging to the same access type (for example, multiple 3GPP access types or multiple non-3GPP access types), or a multiple access session in which the number of paths is greater than two paths.

[0216] 9) Dual connection scenario:

[0217] Taking Figure 4 as an example, the dual connection scenario used in the embodiment of the present application is introduced. For example, the dual connection can be called Dual Steer. In this scenario, the UE simultaneously accesses the same network through two connections of the 3GPP access type. Among them, the two 3GPP access network devices corresponding to the 3GPP access type can be RANs. For example, the UE can use a SIM card to access the same PLMN through two different RANs at the same time. Exemplarily, the two connections of the 3GPP access type correspond to two paths. As shown in Figure 4, the first path is for the UE to connect to the core network through RAN1. The second path is for the UE to connect to the core network through RAN2 and AMF.

[0218] It should be noted that accessing the same network through two connections of the 3GPP access type at the same time does not mean that the UE must send or receive data through two paths at the same time. Instead, it means that the UE can access the network and send or receive data through the first path, and can also access the network and send or receive data through the second path.

[0219] It should be noted that in this application, the names of dual connections or multi-connections can be further extended as follows:

[0220] 1: Dual / multiple radio capability. Dual / multiple radio capability indicates that the UE supports the ability to access the network through dual / multiple radios.

[0221] 2: Dual / multiple 3GPP RAT: Dual / multiple 3GPP RAT indicates that the UE accesses the network through dual / multiple 3GPP RAT.

[0222] 3: Dual / multiple steer: Dual / multiple steer indicates that the UE accesses the network through a dual / multiple steer path.

[0223] 4: Dual / multiple 3GPP access: Dual / multiple 3GPP access indicates that the UE accesses the network through dual / multiple 3GPP paths.

[0224] 5: Dual / multiple 3GPP access type: The dual / multiple 3GPP access type indicates that the UE accesses the network through the dual / multiple 3GPP access type.

[0225] 6: Dual / multiple connectivity: Dual / multiple connectivity indicates that the UE accesses the network through dual / multiple different paths.

[0226] 7: Dual / multiple registration: Dual / multiple registration indicates that the UE registers with the network through dual / multiple different paths.

[0227] 8: Same access type: The same access type indicates that the UE accesses the network through two or more paths of the same access type.

[0228] 9: Same access technology (same RAT): Same access technology indicates that the UE accesses the network through dual / multiple paths using the same access technology.

[0229] 10: Same access network: The same access network indicates that the UE accesses the same network through dual / multiple paths.

[0230] 11: Dual / multiple registration within same access type. Dual / multiple registration within same access type indicates that the UE registers to the network through dual / multiple paths of the same access type.

[0231] 12: Dual / multiple air interface capability: The dual / multiple air interface capability indicates the UE's ability to access the network via dual / multiple air interfaces.

[0232] In this embodiment, the UE supporting dual radio capability is taken as an example for introduction. It should be noted that other names of the above extensions are also applicable. In other words, the names of the above extensions can be replaced with each other.

[0233] However, in this dual connectivity scenario, when a UE accesses the network through two 3GPP access types, because the access network devices in both paths are 3GPP access type devices, the UE cannot distinguish which path the data is transmitted on using the same access type. As a result, the UE will arbitrarily select at least one of the two paths to transmit data based on the 3GPP access type, resulting in reduced transmission efficiency.

[0234] In order to solve the above problem, the present application proposes the following method, so that the UE and the network can accurately identify different transmission paths with the same access type to achieve multi-connection management, or multi-path management.

[0235] As shown in Figure 6, a method 600 applicable to the present application is described. This method is applicable to a UE accessing a network via multiple paths of the same access type (e.g., two 3GPP access type paths). In method 600, the AMF assigns a path identifier to the UE during the registration process and sends it to the UE. Method 600 enables the UE to determine the transmission path based on the path identifier. The method includes the following steps:

[0236] Step 601: UE sends an access network (AN) message to RAN1.

[0237] In one possible implementation, the AN message includes capability information, and the capability information indicates the connection capabilities supported by the UE, such as support for multiple connections or dual connections. The dual connection / multi-connection capability indicates that the UE can establish connections or transmit data with two / multiple RANs at the same time. Alternatively, the dual connection / multi-connection capability indicates that the UE has two / multiple user plane protocol stacks and can perform dual transmission and dual reception / multiple transmission and multi-reception of data at the same time. The data transmitted and received at the same time can be forwarded to the core network user plane device (such as UPF) through different RANs respectively; optionally, the user plane device can receive data from multiple access network devices, aggregate it, and send the aggregated data to the data network (or server), such as DN 140 in Figure 1. In one possible implementation, the capability information indicates that the UE supports establishing connections or transmitting data with two / multiple RANs at the same time. Alternatively, the capability information indicates that the UE supports two / multiple user plane protocol stacks and can perform dual transmission and dual reception / multiple transmission and multi-reception of data at the same time. This application does not limit the name of the capability information. It can be support dual connection or support multiple connection, or it can be an extension of the name of the above dual connection or multiple connection. In this embodiment, the UE capability information is UE supports dual connection as an example for illustration.

[0238] In one possible implementation, the capability information is a field in the AN message that the AMF can parse, so that the AMF can obtain the capability information and assign a path identifier based on the capability information. For example, the registration request message in the AN message includes the capability information. For another example, the capability information can be included in the AN message alongside the AN parameters and the registration request message.

[0239] Optionally, the capability information is a field in the AN message that the RAN can parse, allowing the RAN to obtain the capability information and select an AMF based on the capability information. For example, the AN parameter in the AN message includes the capability information. For another example, the capability information can be included in the AN message alongside the AN parameter and the registration request message.

[0240] In a possible implementation, when the UE determines that it has dual connectivity capability, or the UE wishes to access the network through two different paths of 3GPP access type at the same time, the AN message sent in step 601 includes capability information.

[0241] In one possible implementation, the UE determines, based on dual connectivity information (e.g., DualSteer information), that it can access the network via two paths, or that it desires to access the network simultaneously via two different paths. Exemplarily, the dual connectivity information may be obtained by the UE based on a service. For example, if one path cannot meet the rate requirements of a service (e.g., a video service), the UE may determine, based on the service, that it wants to access the network using two paths, thereby executing step 601.

[0242] In one possible implementation, the UE may obtain dual connectivity information (e.g., DualSteer information) based on a user's operating instructions. For example, the user may turn on the DualSteer switch on the UE. Further, the UE may enter the DualSteer state based on the user's operating instructions, thereby executing step 601.

[0243] In another possible implementation, the UE may obtain dual connectivity support information (e.g., DualSteer information) based on pre-configured information. For example, the UE factory configuration may pre-configure information that the UE supports DualSteer, e.g., the UE supports simultaneous access to the network through two different paths, thereby executing step 601.

[0244] This embodiment is described by taking the example of the UE selecting RAN1 as the first path to initiate the registration process and sending an AN message to RAN1. In another possible implementation, the description of the AN message is as shown in step 201 in FIG2 , that is, the AN message may not include the capability information.

[0245] Step 602: RAN1 selects AMF.

[0246] In one possible implementation, the capability information is a field that can be parsed by RAN in the AN message, and RAN1 selects an AMF that supports dual connectivity based on the capability information. In other words, it selects an AMF that supports the management of "UEs that support dual connectivity". It can be understood that the AMF can retain two path connections for the same UE, or it can be understood that the AMF can maintain a connection with the UE through two paths at the same time, or it can be understood that the AMF can identify newly added parameters, such as the capability information of the UE. Among them, "UEs that support dual connectivity" can be understood as UEs that can access the network through the same access type. For example, the UE can access the same AMF or different AMFs through two 3GPP paths corresponding to two different RANs. When accessing the same AMF, the AMF can simultaneously maintain the connection status / context information of the UE corresponding to the two 3GPP paths, or it can be understood that the AMF supports dual registration. The AMF supports multiple registrations, which is also applicable in this embodiment. It should be noted that the names of those that support dual registration or multiple registrations can be further extended as follows:

[0247] 1: Support dual / multi-registration management. Support dual / multi-registration management indicates that the AMF supports managing the UE to the network through dual / multi-registration.

[0248] 2: Support dual / multiple registration under the same access type. Support dual / multiple registration under the same access type indicates that the AMF supports the management of UEs registered to the network through dual / multiple paths of the same access type.

[0249] 3: Support dual / multiple registration under the same access technology. Support dual / multiple registration under the same access technology indicates that the AMF supports the management of UEs registered to the network through dual / multiple paths of the same access technology.

[0250] 4: Support dual / multi-connection management. Support dual / multi-connection management indicates that the AMF supports managing UEs connected to the network via dual / multiple paths.

[0251] 5: Support dual / multiple connections under the same access type. Support dual / multiple connections under the same access type indicates that the AMF supports managing UEs connected to the network via dual / multiple paths of the same access type.

[0252] 6: Support dual / multiple connections under the same access technology. Support dual / multiple connections under the same access technology indicates that the AMF supports managing UEs connected to the network through dual / multiple paths of the same access technology.

[0253] In this embodiment, RAN1 selects AMF1 as an example for description.

[0254] Step 603: RAN1 sends a registration request message to AMF1.

[0255] The registration request message includes capability information, which is used by AMF1 to allocate a path identifier.

[0256] Optionally, RAN1 sends information for distinguishing paths to AMF1. In one possible implementation, the information for distinguishing paths is one or more of location information, access type, access technology type, registration type, and RAN identifier. The location information is, for example, user location information (ULI). The ULI includes a cell identifier, which is an identifier of a cell in RAN1 accessed by the UE. Because the UE accesses different cells along different paths, different paths can be identified by the ULI.

[0257] In one possible implementation, RAN1 sends a Next Generation Application Protocol (NGAP) message, also referred to as an N2 message, to AMF1. The N2 message includes a registration request message and information for distinguishing paths. This means that the registration request message and the information for distinguishing paths are presented side by side in the N2 message.

[0258] In another possible implementation, RAN 1 may send a registration request message and information for distinguishing paths to AMF 1 through two N2 messages respectively.

[0259] In another possible implementation, RAN1 may send a registration request message to AMF 1 through an N2 message, where the registration request message includes UE capability information and information for distinguishing paths.

[0260] Step 604 (optional): AMF1 triggers the authentication and security procedure with the UE, AUSF, and UDM.

[0261] For related descriptions, please refer to the relevant instructions in step 204 in Figure 2, which will not be repeated here.

[0262] Step 605: AMF1 allocates a path identifier (eg, path identifier).

[0263] In one possible implementation, AMF1 indicates support for dual connectivity based on the UE's capability information and allocates a path identifier.

[0264] In one possible implementation, when different AMFs are on different paths, in order to ensure that different AMFs assign different path identifiers to the same UE, the AMF may assign path identifiers in the following two ways:

[0265] Method a: The path identifier includes the AMF identifier. For example, if the AMF identifier is AMF1 and AMF1 assigns path identifier 1 to the first path, the path identifiers for the first path may include AMF1 and 1. If the other AMF identifier is AMF2 and AMF2 assigns path identifier 1 to the second path, the path identifiers for the second path may include AMF2 and 1. This ensures that the path identifiers assigned by AMF1 and AMF2 are different.

[0266] Method b: Path identifiers are selected from an identifier set. The network assigns different identifier sets to different AMFs. For example, if the network assigns a set of 1-32 to AMF1, AMF1 selects the path identifier from the set of 1-32 for the first path, for example, path identifier 1. If the network assigns a set of 33-64 to AMF2, AMF2 selects the path identifier from the set of 33-64 for the second path, for example, path identifier 33. This ensures that the path identifiers assigned by AMF1 and AMF2 are different.

[0267] In another possible implementation, when the AMFs on different paths are the same, the AMF allocates different path identifiers for the same UE on different paths.

[0268] In this embodiment, description is made by taking AMF1 assigning path identifier 1 to the first path as an example.

[0269] In one possible implementation, AMF1 obtains information used to distinguish paths, such as location information, access type, access technology type, registration type, and RAN identifier. AMF1 can determine the access type, access technology type, and RAN identifier based on access network device information, and obtain the location information and registration type based on a message sent by RAN1. For example, RAN1 sends an N2 message to AMF1, which includes location information and a registration request message, and the registration request message includes the registration type. It should be noted that the information used to distinguish paths is information used to distinguish the first path or to identify the first path.

[0270] In one possible implementation, AMF1 stores the path identifier in the UE context, or stores the path identifier 1 and information used to distinguish the first path (such as one or more of location information, access type, access technology type, registration type, and RAN identifier) ​​in the UE context, or stores the association between the path identifier 1 and the information used to distinguish the first path in the UE context. In this way, after subsequently receiving downlink data, AMF1 can determine the first path based on the path identifier 1 and send the data to the UE through the first path.

[0271] Step 606: AMF1 sends a registration request to UDM.

[0272] The registration request is used by AMF1 to register with UDM as the AMF serving the UE. Exemplarily, the registration request is Nudm_UECM_Registration request.

[0273] Optionally, the registration request includes path identifier 1 and information used to distinguish the first path (such as one or more of location information, access type, access technology type, registration type, and identifier of the AMF serving the UE). Path identifier 1 is used to subsequently notify the SMF that the path identifier of the path corresponding to the information used to distinguish the first path is 1.

[0274] Optionally, the registration request includes capability information, where the capability information indicates that the UE supports dual connectivity.

[0275] In one possible implementation, AMF 1 may select a UDM that supports dual registration based on capability information or registration type. For example, the registration type is a newly added registration type that indicates that the UE registers for two paths. Exemplarily, the newly added registration type may be named DualSteer Registration, but the name is not limited here. It is understood that the UDM selected by the AMF is a UDM that supports storing multiple contexts for the same UE.

[0276] Step 607: UDM queries the contract data.

[0277] Optionally, the UDM may query the subscription data of the UE based on the UE identifier, where the subscription data of the UE includes the capability information of the UE, thereby determining whether the UE is allowed to access the network through dual connectivity. If the subscription data of the UE indicates that the UE is allowed to access the network through dual connectivity, the information for distinguishing the first path and the path identifier 1 are stored. If the subscription data of the UE indicates that the UE is not allowed to access the network through dual connectivity, the information for distinguishing the first path and the path identifier 1 are not stored.

[0278] In a possible implementation, the UDM may store the information used to distinguish the first path and the path identifier 1, or the correspondence between the information used to distinguish the first path and the path identifier 1, in the subscription data or context information corresponding to the UE.

[0279] Step 608: UDM sends a registration response to AMF 1.

[0280] Exemplarily, the registration response is Nudm_UECM_Registration Response.

[0281] In one possible implementation, the UDM sends the UE's capability information to the AMF1, where the capability information indicates that the UE supports dual connectivity. The AMF1 allocates a path identifier based on the UE's capability information. That is, step 605 may be performed after step 608.

[0282] Step 609: AMF1 sends a Registration Accept message to the UE through RAN1.

[0283] The registration accept message includes the path identifier 1, and the path identifier 1 is used by the UE to determine / identify / recognize / mark the first path.

[0284] In one possible implementation, the UE stores the path identifier 1. Exemplarily, the UE associates / maps the path identifier 1 with one or more of the access technology type, RAN identifier, access type, or protocol stack, interface, or link corresponding to the current path. That is, the UE may associate / map the path identifier 1 with the currently connected RAN 1. For example, the UE may associate / map the path identifier 1 with the currently connected RAN 1 through circuit logic, line logic, protocol stack logic, etc. Subsequently, the UE may determine the first path corresponding to RAN 1 based on the path identifier 1 and the association / mapping relationship.

[0285] Step 610: The UE sends an AN message to RAN2.

[0286] The AN message includes capability information. For description related to the capability information, please refer to step 601 in FIG6 , which will not be repeated here.

[0287] It should be noted that when the UE determines that it wishes to access the network simultaneously via two different paths, step 610 is executed. Exemplarily, before the UE sends the AN message to RAN2, the UE determines that it can access the network via two paths, and the UE determines that it has already accessed the network via the first path. Exemplarily, the UE can determine that it can access the network via two paths based on the dual connectivity information. For a description of dual connectivity, please refer to step 601 in Figure 6.

[0288] This embodiment is described by taking an example where the UE selects RAN2 as the second path to initiate a registration process and sends an AN message to RAN2.

[0289] Step 611: RAN2 selects AMF.

[0290] For the description of selecting AMF, please refer to step 602 and will not be repeated here.

[0291] It should be noted that the AMF selected by RAN2 can be AMF1 or AMF2 which is different from AMF1.

[0292] In this embodiment, RAN2 selects AMF2 as an example for description.

[0293] Step 612: RAN2 sends a registration request message to AMF2.

[0294] For related descriptions, please refer to step 603 and will not be repeated here.

[0295] Step 613: AMF2 triggers the authentication and security procedure with the UE, AUSF, and UDM.

[0296] For related descriptions, please refer to the relevant instructions in step 204 in Figure 2, which will not be repeated here.

[0297] Step 614: AMF2 allocates a path identifier (eg, path identifier).

[0298] For related descriptions, please refer to the relevant instructions in step 605 and will not be repeated here.

[0299] In this embodiment, description is made by taking AMF2 assigning path identifier 2 to the second path as an example.

[0300] Step 615: AMF 2 sends a registration request to UDM.

[0301] For related descriptions, please refer to the relevant instructions in step 606 and will not be repeated here.

[0302] Step 616: UDM queries the contract data.

[0303] For related descriptions, please refer to the relevant instructions in step 607 and will not be repeated here.

[0304] Step 617: UDM sends a registration response to AMF 2.

[0305] Step 618: AMF2 sends a Registration Accept message to the UE through RAN2.

[0306] The registration accept message includes the path identifier 2, and the path identifier 2 is used by the UE to determine / identify / recognize / mark the second path.

[0307] In one possible implementation, the UE stores path identifier 2. Exemplarily, the UE associates / maps path identifier 2 with one or more of the access technology type, RAN identifier, access type, or protocol stack, interface, or link corresponding to the current path. That is, the UE may associate / map path identifier 2 with the currently connected RAN 2. For example, the UE may associate / map path identifier 2 with the currently connected RAN 2 through circuit logic, line logic, protocol stack logic, etc. Subsequently, the UE may determine the second path corresponding to RAN 2 based on path identifier 2 and the association / mapping relationship.

[0308] Step 619 (optional): The UDM sends the path identifier and information for distinguishing the path to the UDR.

[0309] Exemplarily, the UDM sends the path identifier and information for distinguishing the path to the UDR via a data management create / update request message (eg, Nudr_DM_Create / Update request).

[0310] In one possible implementation, the UDM can send one or more path identifiers and information used to distinguish paths to the UDR. For example, the information used to distinguish paths is the AMF identifier, i.e., the information used to distinguish the first path is the AMF1 identifier, and the information used to distinguish the second path is the AMF2 identifier. The UDM sends the AMF1 identifier and path identifier 1, and / or the AMF2 identifier and path identifier 2 to the UDR. In the subsequent session establishment process, the PCF can obtain the path identifier and the corresponding information used to distinguish paths from the UDR.

[0311] In another possible implementation, the UDM may send the UE's identification information, as well as the path identification corresponding to the UE and information for distinguishing paths to the UDR.

[0312] It should be noted that the present application does not limit the execution order of step 619. For example, step 619 may be executed after step 616. Alternatively, the UDM may send the first path identifier and information for distinguishing the first path to the UDR, which may be executed after step 607.

[0313] Step 620 (optional): The UDR sends the path identifier and information for distinguishing the paths to the PCF.

[0314] In one possible implementation, the PCF generates a routing rule (e.g., a URSP) based on the path identifier and information for distinguishing paths. The routing rule includes the path identifier. The information for distinguishing paths can be used to determine path priority. The routing rule is subsequently sent to the UE, which uses the routing rule to select the path corresponding to the path identifier from multiple paths under the same access type for service transmission. When the routing rule is a URSP, it can be understood that an enhanced URSP is generated here.

[0315] In another possible implementation, the PCF receives path identifier 1 and information used to distinguish the first path from AMF1, and receives path identifier 2 and information used to distinguish the second path from AMF2. It should be noted that when the AMFs in the first and second paths are the same, for example, both are AMF1, the PCF may receive path identifier 1 and information used to distinguish the first path, as well as path identifier 2 and information used to distinguish the second path, from AMF1.

[0316] In a possible implementation, the PCF is an AM-PCF, which is mainly responsible for access mobility policy control.

[0317] Through the steps of method 600, when a UE accesses a network through two 3GPP access type paths, the AMF allocates a path identifier, and the UE receives a first path identifier from the first path and a second path identifier from the second path. Thus, both the UE and the network can distinguish between the two different paths based on the path identifiers.

[0318] As shown in Figure 7, in combination with Figure 6 above, a method 700 applicable to the present application is introduced, which is applicable to UE accessing the network through multiple paths of the same access type (for example, two paths of 3GPP access type). The AMF first allocates a path identifier for the UE in the registration process and sends it to the UE. In the session establishment process, the SMF generates a diversion rule based on the path identifier, and the UE obtains the diversion rule. In one possible implementation, the UE executes the steps in method 700 after the registration process is completed on both paths. In another possible implementation, the UE executes steps 701-713 of method 700 after the first path completes registration, and the UE executes steps 714-720 of method 700 after the second path completes registration. Through method 700, the UE can determine the transmission path of the service data based on the path identifier. The method includes the following steps:

[0319] Step 701: The UE sends a session establishment request message to AMF1 through RAN1.

[0320] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0321] This embodiment is described by taking as an example that the UE selects RAN1 as the first path to initiate a session establishment process, and sends a session establishment request message to AMF1 through RAN1.

[0322] Step 702: AMF selects SMF.

[0323] In one possible implementation, AMF1 selects an SMF that supports dual connectivity based on capability information (e.g., UE supports dual connectivity). An SMF that supports dual connectivity can be understood as an SMF that can recognize newly added parameters in a message, such as a path identifier, information used to distinguish paths, and the like. The SMF supports the generation of a diversion rule including a path identifier (e.g., an enhanced diversion rule). The diversion rule including the path identifier can select a path transmission service corresponding to the path identifier from multiple paths under the same access type. For a description of capability information, refer to step 601 in FIG6 .

[0324] Step 703: AMF1 sends a session context request message to SMF.

[0325] The session context request message includes path identifier 1 and / or information used to distinguish the first path. Path identifier 1 is assigned by AMF1 in step 605 of Figure 6 . The information used to distinguish the first path may be one or more of location information, access type, access technology type, registration type, RAN identifier, and AMF identifier. The location information may include, for example, a ULI, which includes a cell identifier. The cell identifier is the identifier of the cell accessed by the UE in RAN1. Because the UE accesses different cells along different paths, the different paths can be identified by the ULI.

[0326] In a possible implementation, the session context request message includes the path identifier 1. The SMF can obtain the path identifier 1 through the AMF1, so that the SMF can subsequently determine to send data to the AMF1 based on the path identifier 1.

[0327] In another possible implementation, the session context request message includes path identifier 1 and information used to distinguish the first path. The information used to distinguish the first path includes, for example, the RAT type. For example, the RAT type corresponding to the first path connecting RAN1 and AMF1 is 6G, and the RAT type corresponding to the second path connecting RAN2 and AMF2 is 5G. Thus, the SMF can subsequently determine to send data to AMF1 on the first path corresponding to 6G based on path identifier 1.

[0328] In another possible implementation, the session context request message includes information for distinguishing the first path, so that the SMF can obtain the path identifier 1 corresponding to the first path from the UDM or PCF according to the information for distinguishing the first path.

[0329] In a possible implementation, the session context request message is a PDU session create session management context request (Nsmf_PDUSession_CreateSMContext Request) message, or a PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) message.

[0330] Step 704: SMF obtains the contract data from UDM.

[0331] The subscription data (e.g., session management subscription data) may include a path identifier, or a path identifier and information for distinguishing paths. The path identifier and information for distinguishing paths may include path identifier 1 and information for distinguishing a first path, and path identifier 2 and information for distinguishing a second path. Path identifier 1 and information for distinguishing the first path are stored by the UDM in step 607 of FIG. 6 , and path identifier 2 and information for distinguishing the second path are stored by the UDM in step 616 of FIG. 6 . Exemplarily, the UDM may store the path identifier and information for distinguishing paths in the subscription data or context information corresponding to the UE.

[0332] In one possible implementation, the subscription data includes a path identifier. Exemplarily, the SMF sends information for distinguishing the first path to the UDM, which is the information obtained by the SMF from AMF1 in step 703. The UDM determines the corresponding path identifier, i.e., path identifier 1, based on the information for distinguishing the first path, and sends the path identifier to the SMF. Exemplarily, the information for distinguishing the first path is the identifier of the AMF, i.e., AMF1. The SMF sends the SUPI of the UE and AMF1 to the UDM. The UDM queries the subscription data or context information corresponding to the UE based on the SUPI, and sends the path identifier (i.e., path identifier 1) corresponding to the AMF1 to the SMF based on the association between the stored path identifier and the information for distinguishing the first path.

[0333] In another possible implementation, the subscription data includes a path identifier and information for distinguishing the paths. Exemplarily, the information for distinguishing the paths is an AMF identifier, i.e., the above information indicates that path identifier 1 corresponds to AMF1 and path identifier 2 corresponds to AMF2. The SMF receives the session context request message from AMF1 in step 703, so that the SMF can subsequently determine whether to send data to AMF1 based on path identifier 1.

[0334] It should be noted that, when the above-mentioned session context request message includes the path identifier 1, the subscription data may also not include the path identifier and the information used to distinguish the path. For the relevant description of the subscription data, please refer to step 303 in Figure 3.

[0335] In a possible implementation, after receiving the path identifier, the SMF may store the path identifier in the context information of the UE. Exemplarily, the SMF may store the association relationship between the path identifier 1 and the information used to distinguish the first path in the context information of the UE.

[0336] Step 705: SMF sends a session context response message to AMF1.

[0337] In a possible implementation, the session context response message is a PDU session create session context response (Nsmf_PDU Session_CreateSMContext Response) message, or a PDU session update session management context response message (Nsmf_PDUSession_UpdateSMContext Response).

[0338] Step 706: The SMF sends a policy request message to the PCF.

[0339] The policy request message includes a path identifier and / or information for distinguishing paths.

[0340] In a possible implementation, the policy request message includes a path identifier, or a path identifier and information for distinguishing paths, so that the PCF can obtain the path identifier, for example, path identifier 1.

[0341] In another possible implementation, when the policy request message includes information for distinguishing paths, the PCF may obtain the path identifier from the UDR.

[0342] In one possible implementation, the SMF selects a PCF that supports multiple connections based on the path identifier and sends a policy request message to the PCF that supports multiple connections. A PCF that supports multiple connections can be understood as one that can recognize newly added parameters, such as path identifiers. The PCF supports the generation of policy rules (e.g., enhanced PCC rules) that include path identifiers. The policy rules are used to select the path transmission service corresponding to the path identifier among multiple paths under the same access type.

[0343] In a possible implementation, the policy request message is a policy association establishment request message (SM Policy Association Establishment Request) message, or a policy association modification request message (SM Policy Association Modification Request) message.

[0344] Step 707 (optional): PCF interacts with UDR to obtain the path identifier.

[0345] It should be noted that the UDR can obtain the association between the path identifier and the information used to distinguish the path through step 619 in method 600.

[0346] In one possible implementation, the PCF sends information used to distinguish paths to the UDR. The UDR determines a path identifier based on the aforementioned association and sends the path identifier to the PCF. For example, information used to distinguish paths may include RAT type. For example, the RAT type corresponding to the first path connecting RAN1 and AMF1 is 6G, and the RAT type corresponding to the second path connecting RAN2 and AMF2 is 5G. The PCF sends 6G to the UDR. The UDR can determine path identifier 1 based on the association between 5G and path identifier 1. The UDR then sends path identifier 1 to the PCF, or the UDR sends path identifier 1 and 6G to the PCF.

[0347] In one possible implementation, the PCF sends a query message to the UDR, such as a data management query message (Nudr_DM_Query), which includes the above information for distinguishing paths, and the UDR sends a data management response message (Nudr_DM_Query_Response) to the PCF, which includes the above path identifier.

[0348] Step 708: The PCF sends a policy response message to the SMF.

[0349] The policy response message includes the policy rules.

[0350] In one possible implementation, the policy rule (e.g., PCC rule) in the policy response message may include a path identifier. Exemplarily, when the policy rule is a PCC rule, it can be understood that an enhanced PCC rule is generated. Based on this policy information, the UE or UPF can select the path corresponding to the path identifier from among multiple paths under the same access type for service transmission.

[0351] In one possible implementation, the PCF can generate policy rules based on the path identifier and the information used to distinguish the path. The information used to distinguish the path can be used to determine the path priority. For example, the MA PDU Session Control information in the policy rule is generated, and the MA PDU Session Control information allows the PCF to control one or more of the following: diversion mode, diversion function, diversion mode indication, threshold value, billing information, and usage monitoring information. For example, here, the information corresponding to the path identifier 1 for distinguishing the first path is 6G, and the diversion mode is Active standby mode. Assuming that 6G is higher than 5G and 4G, the PCF can determine that the path is an Active path based on the higher priority of 6G. The policy rules containing the path identifier 1 generated by the PCF based on the path identifier 1 can be represented using Table 1:

[0352] Table 1 Policy rules (including path identifier 1)

[0353] The service descriptor is used to define a service flow. This rule indicates that for the service flow corresponding to the service descriptor, the active standby traffic diversion mode is adopted, where the active path is the transmission path identified by path identifier 1. That is, when the transmission path identified by path identifier 1 is available, the transmission path identified by path identifier 1 is used to transmit the above service flow.

[0354] It should be noted that when the policy rules generated by the PCF do not include a path identifier, the relevant description of the policy rules can refer to the PCC rules. This embodiment is described with the diversion mode in the policy rules being active standby. The policy rules generated by the PCF that do not include a path identifier can be represented using Table 2:

[0355] Table 2 Policy rules (excluding path identifiers)

[0356] In one possible implementation, the PCF is an SM-PCF, which is primarily responsible for session management policy control. It should be noted that the SM-PCF and the AM-PCF may be different PCFs.

[0357] In a possible implementation, the policy response message is a policy association establishment response (SM Policy Association Establishment Response) message or a policy association modification response (SM Policy Association Modification Response) message.

[0358] Step 709: SMF selects UPF.

[0359] In one possible implementation, the UPF selected by the SMF supports storing multiple contexts of the same UE. It can be understood that the UPF supports performing data (or service) offloading for multiple paths for the UE to connect to the network. For example, the UPF supports performing data offloading for the path for the UE to connect to the network through dual 3GPP access types. Or the UPF supports offloading rules including path identifiers (such as enhanced N4 rules), and the offloading rules including path identifiers can be used by the UPF to select the path corresponding to the path identifier in multiple paths under the same access type to transmit services.

[0360] Step 710: SMF sends diversion rules to UPF.

[0361] The SMF can generate a diversion rule (e.g., N4 rule) used by the UPF based on the policy rules. The diversion rule includes a path identifier. For example, the Multi-Access Rule (MAR) includes a path identifier. When the diversion rule is the N4 rule, it can be understood that an enhanced N4 rule is generated here. The diversion rule is used by the UPF to select the path corresponding to the path identifier from multiple paths under the same access type to transmit downlink service data.

[0362] In one possible implementation, the policy information does not include a path identifier. The SMF may generate a diversion rule based on the path identifier and the information used to distinguish the path. For example, taking the case where the information corresponding to path identifier 1 used to distinguish the first path is 6G and the diversion mode is Active Standby mode, the SMF may determine that the path is an Active path based on the higher priority of 6G. The diversion rule generated by the SMF based on path identifier 1 and including path identifier 1 may be represented using Table 3:

[0363] Table 3 Diversion rules

[0364] In another possible implementation, the policy rule includes a path identifier, and the SMF generates a diversion rule including the path identifier according to the policy rule. The diversion rule can be represented by the above Table 3.

[0365] In one possible implementation, the SMF sends an N4 Session Establishment Request message to the UPF, which includes the above-mentioned diversion rules.

[0366] Step 711: SMF sends an N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) message to AMF1.

[0367] The SMF can generate a diversion rule (e.g., an ATSSS rule) for use by the UE based on policy rules. This diversion rule includes a path identifier. When the diversion rule is an ATSSS rule, it can be understood that an enhanced ATSSS rule is generated here. This diversion rule is used by the UE to select the path corresponding to the path identifier for service transmission among multiple paths under the same access type. Exemplarily, the diversion rule can be represented using Table 3 above. It should be noted that the diversion rule used by the UPF is for downlink data transmission, while the diversion rule used by the UE is for uplink data transmission. The IP address in the service descriptor in the diversion rule used by the UE and the diversion rule used by the UPF is different. This IP address is used to identify the destination of the IP service flow. The N1N2 message transmission message includes path identifier 1 and the diversion rule. Path identifier 1 is used by AMF 1 to determine the RAN corresponding to path identifier 1. For example, if the UE is connected to AMF 1 via RAN 1 and RAN 2, that is, the AMF on the first and second paths is the same, namely, AMF 1. AMF 1 can determine the first path where RAN 1 is located based on path identifier 1.

[0368] In a possible implementation, the N1 interface session management container (N1 SM Container) in the N1N2 message transmission message includes a diversion rule and a session establishment accept (Session Establishment Accept) message (which can be regarded as a response to the session establishment request in step 701).

[0369] Step 712: AMF1 sends an N2 session request message to RAN1.

[0370] The N2 session request message includes a diversion rule.

[0371] In one possible implementation, AMF1 can determine to which access network device (e.g., RAN) the above information is sent based on the path identifier sent by SMF. For example, AMF1 determines to send the N2 session request message to RAN1 in the first path based on path identifier 1.

[0372] In a possible implementation, the N2 session request message is an N2 PDU session request message. The N1 interface session management container in the N2 PDU session request message includes a diversion rule.

[0373] Step 713: RAN1 sends the offload rule to the UE.

[0374] In one possible implementation, the diversion rule includes path identifier 1 and a service descriptor. The UE can determine the path through which service data should be transmitted based on the diversion rule. For example, in the default active standby mode, the UE identifies the path corresponding to path identifier 1 as the active path. When the first path corresponding to path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor along the first path.

[0375] In another possible implementation, the offload rule includes path identifier 1, an offload mode, and a service descriptor. The UE can determine the path through which service data should be transmitted based on the offload rule. For example, if the UE is in active standby mode based on the offload mode and the path corresponding to path identifier 1 is the active path, the UE transmits the service flow corresponding to the service descriptor over the first path when the first path corresponding to path identifier 1 is available.

[0376] Exemplarily, the UE determines the corresponding first path according to the path identifier 1. For a description of the association / mapping between the path identifier and the path, refer to step 609.

[0377] In a possible implementation, during the process of establishing air interface resources between RAN1 and UE, RAN1 sends a traffic diversion rule to the UE.

[0378] It should be noted that the subsequent steps of the UE establishing the user plane channel of the first path through RAN1 and AMF1 refer to steps 313 to 318 in Figure 3, which will not be repeated here.

[0379] Step 714: The UE sends a session establishment request message to AMF2 through RAN 2.

[0380] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0381] This embodiment is introduced by taking an example in which the UE selects RAN2 as the second path to initiate a session establishment process and sends a session establishment request message to AMF2 through RAN2.

[0382] Step 715: AMF2 sends path identifier 2 and / or information used to distinguish the second path to SMF.

[0383] Path identifier 2 is assigned by AMF2 in step 614 of Figure 6 . The information used to distinguish the second path may be one or more of location information, access type, access technology, registration type, RAN identifier, and AMF identifier. The location information may be, for example, a ULI, which includes a cell identifier. The cell identifier is the identifier of the cell accessed by the UE in RAN1. Because the UE accesses different cells along different paths, the ULI can be used to identify different paths.

[0384] In one possible implementation, AMF2 sends path identifier 2 to SMF. SMF can obtain path identifier 2 through AMF2, so that SMF can subsequently determine to send data to AMF2 based on path identifier 2.

[0385] In another possible implementation, AMF2 sends path identifier 2 and information for distinguishing the second path to SMF. The information for distinguishing the second path may be, for example, the RAT type. For example, the RAT type corresponding to the first path connecting RAN1 and AMF1 is 6G, and the RAT type corresponding to the second path connecting RAN2 and AMF2 is 5G. Thus, SMF can subsequently determine to send data to AMF2 on the second path corresponding to 5G based on path identifier 2.

[0386] In another possible implementation, AMF2 sends information for distinguishing the second path to SMF, so that SMF can obtain the path identifier 2 corresponding to the second path from UDM or PCF based on the information for distinguishing the second path.

[0387] In one possible implementation, the path identifier 2 and / or the information used to distinguish the second path is sent via a session context request or update message, such as a PDU session create session management context request (Nsmf_PDUSession_CreateSMContext Request) message or a PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) message.

[0388] Step 716 (optional): The SMF sends the path identifier 2 and / or information used to distinguish the second path to the PCF.

[0389] In a possible implementation, when the SMF sends the path identifier 2, or the path identifier 2 and the information used to distinguish the second path, to the PCF, the PCF obtains the path identifier 2.

[0390] In another possible implementation, when the SMF sends information for distinguishing the second path to the PCF, the PCF may obtain the path identifier 2 from the UDR.

[0391] In a possible implementation, the path identifier 2 and / or the information used to distinguish the second path is sent via a policy request message, such as a SM Policy Association Establishment Request message or a SM Policy Association Modification Request message.

[0392] Step 717 (optional): PCF sends a policy update message to SMF.

[0393] In a possible implementation, the policy update message includes an updated policy rule, and the policy rule (eg, PCC rule) includes a path identifier 2 .

[0394] In one possible implementation, the PCF may generate a policy rule based on a path identifier and information for distinguishing paths. The information for distinguishing paths may be used to determine path priority. For example, taking the information for distinguishing the first path corresponding to path identifier 1 as 6G, the information for distinguishing the second path corresponding to path identifier 2 as 5G, and the offload mode as Active Standby mode as an example, the PCF may determine that the first path is the Active path and the second path is the Standby path based on the higher priority of 6G relative to 5G. The policy rule generated by the PCF based on the path identifiers and including path identifier 1 and path identifier 2 may be represented using Table 4:

[0395] Table 4 Policy rules (including path identifiers 1 and 2)

[0396] Among them, the service descriptor is used to define the service flow. This rule indicates that: for the service flow corresponding to the service descriptor, the active standby diversion mode is adopted, wherein the active path is the transmission path identified by path identifier 1, that is, when the transmission path identified by path identifier 1 is available, the transmission path identified by path identifier 1 is used to transmit the above service flow. The standby path is the transmission path identified by path identifier 2. That is, when the transmission path identified by path identifier 1 is unavailable and the transmission path identified by path identifier 2 is available, the transmission path identified by path identifier 2 is used to transmit the above service flow.

[0397] Step 718: SMF sends the diversion rules to UPF.

[0398] The SMF may generate a diversion rule (eg, N4 rule) used by the UPF, which includes the path identifier 2.

[0399] In a possible implementation, when step 717 is not performed, the SMF can generate a diversion rule based on the path identifier and the information used to distinguish the path. For example, taking the case where the information corresponding to path identifier 1 for distinguishing the first path is 6G, the information corresponding to path identifier 2 for distinguishing the second path is 5G, and the diversion mode is the Active standby mode as an example, the SMF can determine that the first path is the Active path and the second path is the Standby path based on the higher priority of 6G relative to 5G. The diversion rule generated by the SMF based on the path identifier and including path identifier 1 and path identifier 2 can be represented using the above-mentioned Table 4, which will not be repeated here.

[0400] In another possible implementation, when step 717 is executed, SMF can obtain the updated policy rules sent by PCF, and thus generate a diversion rule including path identifiers 1 and 2 according to the updated policy rules. The diversion rule can be represented using Table 4 above and will not be repeated here.

[0401] In one possible implementation, the SMF sends an N4 Session Establishment Request message to the UPF, which includes the above-mentioned diversion rules.

[0402] Step 719: SMF sends path identifier 2 and diversion rules to AMF2.

[0403] The SMF can generate a diversion rule (such as an ATSSS rule) used by the UE, which includes a path identifier 2. Exemplarily, the diversion rule can be represented by the above Table 4. It should be noted that the diversion rule used by the UPF is for downlink data transmission, and the diversion rule used by the UE is for uplink data transmission. The IP address in the service descriptor in the diversion rule used by the UE and the diversion rule used by the UPF is different. The IP address is used to identify the destination of the IP service flow.

[0404] The path identifier 2 is used by AMF 2 to determine the RAN corresponding to the path identifier 2. For example, the UE is connected to AMF2 through RAN1 and RAN2, that is, the AMF on the first path and the second path is the same, namely AMF2. AMF2 can determine that it is the second path where RAN 2 is located based on the path identifier 2.

[0405] In a possible implementation, the path identifier 2 and the diversion rule are sent via an N1N2 message transfer message (Namf_Communication_N1N2MessageTransfer).

[0406] Step 720: AMF2 sends the offload rules to the UE through RAN2.

[0407] In one possible implementation, AMF2 can determine to which access network device (e.g., RAN) the above information is sent based on the path identifier sent by SMF. For example, AMF2 determines to send the diversion rule to RAN2 in the second path based on path identifier 2.

[0408] In one possible implementation, the diversion rule includes path identifier 1, path identifier 2, and a service descriptor. Based on the diversion rule, the UE can determine which path the service data should be transmitted through. For example, in the default active standby mode, the UE identifies the path corresponding to path identifier 1 as the active path. When the first path corresponding to path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor along the first path. Alternatively, when the first path is unavailable and the second path identified by path identifier 2 is available, the UE uses the second path to transmit the service flow corresponding to the service descriptor.

[0409] In another possible implementation, the diversion rules include path identifier 1, path identifier 2, diversion mode, and service descriptor. The UE can determine which path the service data should be transmitted through based on the diversion rules. For example, if the UE is in active standby mode based on the diversion mode, the path corresponding to path identifier 1 is the active path, and the path corresponding to path identifier 2 is the standby path, the UE transmits the service flow corresponding to the service descriptor along the first path when the first path corresponding to path identifier 1 is available. Alternatively, when the first path is unavailable and the second path identified by path identifier 2 is available, the UE uses the second path to transmit the service flow corresponding to the service descriptor.

[0410] Exemplarily, the UE determines the corresponding first path according to the path identifier 1, and the relevant description is referred to step 609. The UE determines the corresponding second path according to the path identifier 2, and the relevant description is referred to step 618.

[0411] It should be noted that the subsequent steps of the UE establishing the user plane channel of the second path through RAN2 and AMF2 refer to steps 313 to 318 in Figure 3 and are not repeated here.

[0412] Through the steps of method 700, when the UE accesses the network through two 3GPP access type paths, the UE first obtains the path identifiers corresponding to different paths under the same access type through the registration process. When the UE establishes a session through multiple different paths under the same access type, it can obtain the path through which the service data should be transmitted by receiving the diversion rules containing the path identifier, thereby better performing service transmission.

[0413] Through the steps of method 700, when a UE accesses the network via two 3GPP access-type paths, the AMF assigns a path identifier, and the UE receives a first path identifier from the first path and a second path identifier from the second path. Thus, both the UE and the network can distinguish between the two different paths based on the path identifier. Furthermore, the UE receives a diversion rule including the path identifier, and can then, based on the diversion rule corresponding to the service data, transmit the service data via the path corresponding to the path identifier, thereby improving transmission efficiency.

[0414] As shown in Figure 8, a method 800 applicable to the present application is described. This method is applicable to a UE accessing a network via multiple paths of the same access type (e.g., two 3GPP access type paths). In method 800, the UDM assigns a path identifier to the UE during the registration process and sends it to the UE. Method 800 enables the UE to determine the transmission path based on the path identifier. The method includes the following steps: Step 801: The UE sends an AN message to RAN1.

[0415] In a possible implementation, the AN message includes capability information. For a description of the capability information, refer to step 601 in FIG. 6 and will not be repeated here.

[0416] In one possible implementation, when the UE determines that it has dual connectivity capability, or the UE wishes to access the network through two different paths of 3GPP access type at the same time, the AN message sent in step 801 includes capability information. For related descriptions, refer to step 601 in Figure 6 and will not be repeated here.

[0417] This embodiment is described by taking an example in which the UE selects RAN1 as the first path to initiate a registration process and sends an AN message to RAN1.

[0418] In another possible implementation, the relevant description of the AN message refers to step 201 in FIG. 2 , that is, the AN message may not include the above capability information.

[0419] Step 802: RAN1 selects AMF.

[0420] In one possible implementation, the capability information is a field in the AN message that the RAN can parse, and RAN1 selects an AMF that supports dual connectivity based on the capability information. For a description of the AMF that supports dual connectivity, refer to step 602 in FIG6 and will not be repeated here.

[0421] Step 803: RAN1 sends a registration request message to AMF1.

[0422] The registration request message includes capability information.

[0423] Optionally, RAN1 sends information for distinguishing paths to AMF1. In one possible implementation, the information for distinguishing paths includes one or more of location information, access type, access technology type, registration type, and RAN identifier. The location information is, for example, a ULI. The ULI includes a cell identifier, which is the identifier of the cell in RAN1 accessed by the UE. Because the UE accesses different cells along different paths, the ULI can be used to identify different paths.

[0424] In one possible implementation, RAN1 sends an NGAP message, also called an N2 message, to AMF1. The N2 message includes a registration request message and information for distinguishing paths. This means that the registration request message and the information for distinguishing paths are presented side by side in the N2 message.

[0425] In another possible implementation, RAN 1 may send a registration request message and information for distinguishing paths to AMF 1 through two N2 messages respectively.

[0426] In another possible implementation, RAN1 may send a registration request message to AMF 1 through an N2 message, where the registration request message includes UE capability information and information for distinguishing paths.

[0427] Step 804 (optional): AMF1 triggers the authentication and security procedure with the UE, AUSF, and UDM.

[0428] For related descriptions, please refer to the relevant instructions in step 204 in Figure 2, which will not be repeated here.

[0429] Step 805: AMF1 sends a registration request to UDM.

[0430] The registration request is used by AMF1 to register with UDM as the AMF serving the UE. Exemplarily, the registration request is Nudm_UECM_Registration request.

[0431] The registration request includes indication information. The indication information indicates that the UE supports multi-radio capabilities; or, indicates that the UE supports multi-registration capabilities, or indicates that the UE accesses the network through multi-connection. It should be noted that the indication information may be the same as the capability information reported by the UE in step 801, or it may be different. For example, when they are different, it can be understood that AMF1 processes the information reported by the UE. For example, the capability information reported by the UE indicates that the UE supports dual connection, and the indication information sent by AMF1 to UDM indicates that the UE accesses the network through multi-connection. It should be noted that the name of the multi-radio capability can also be replaced by any one of the names of the extended dual connection or multi-connection in the above-mentioned dual connection architecture.

[0432] Optionally, the registration request also includes information for distinguishing paths (such as one or more of location information, access type, access technology type, registration type, RAN identifier, and AMF identifier). AMF1 can determine the access type, access technology, and RAN identifier based on the access network device information, and AMF1 can obtain the location information and registration type based on the registration request message. For example, RAN1 sends an N2 message to AMF1, and the N2 message includes location information and a registration request message, and the registration request message includes a registration type. It should be noted that the information for distinguishing paths is information for distinguishing the first path or information for identifying the first path.

[0433] In one possible implementation, AMF 1 may select a UDM that supports dual registration based on capability information or registration type. For example, the registration type is a newly added registration type that indicates that the UE registers for two paths. Exemplarily, the newly added registration type may be named DualSteer Registration, which is not limited here.

[0434] Step 806: The UDM allocates a path identifier (eg, a path identifier).

[0435] In a possible implementation, the UDM allocates a path identifier according to the instruction information.

[0436] Optionally, the UDM may query the UE's subscription data based on the UE's identifier, where the UE's subscription data includes the UE's capability information, thereby determining whether the UE is allowed to access the network via dual connectivity. If the UE's subscription data indicates that the UE is allowed to access the network via dual connectivity, a path identifier is assigned. It is understood that if the UDM determines, based on the UE's subscription data, that the UE is not allowed to access the network using dual connectivity, the UDM will not assign a path identifier.

[0437] In a possible implementation, the UDM may store the information used to distinguish the first path and the path identifier 1, or the correspondence between the information used to distinguish the first path and the path identifier 1, in the subscription data or context information corresponding to the UE.

[0438] In this embodiment, description is made by taking the example of the UDM assigning the path identifier 1 to the first path where the AMF1 is located.

[0439] Step 807: UDM sends a registration response to AMF 1.

[0440] The registration response message includes path identifier 1.

[0441] Optionally, the registration response message also includes information used to distinguish the first path, such as a RAN identifier, so that the AMF can determine the corresponding path based on the information about distinguishing the path.

[0442] Exemplarily, the registration response is Nudm_UECM_Registration Response.

[0443] Step 808: AMF1 sends a registration accept (eg, Registration Accept) message to the UE through RAN1.

[0444] The registration accept message includes the path identifier 1, and the path identifier 1 is used by the UE to determine / identify / recognize / mark the first path.

[0445] In one possible implementation, after AMF 1 receives the path identifier, AMF 1 may store the information used to distinguish the first path and the path identifier 1, or the correspondence between the information used to distinguish the first path and the path identifier 1, in the context information of the UE.

[0446] In one possible implementation, the UE stores the path identifier 1. Exemplarily, the UE associates / maps the path identifier 1 with one or more of the access technology type, RAN identifier, access type, or protocol stack, interface, or link corresponding to the current path. That is, the UE may associate / map the path identifier 1 with the currently connected RAN 1. For example, the UE may associate / map the path identifier 1 with the currently connected RAN 1 through circuit logic, line logic, protocol stack logic, etc. Subsequently, the UE may determine the first path corresponding to RAN 1 based on the path identifier 1 and the association / mapping relationship.

[0447] Step 809: The UE sends an AN message to RAN2.

[0448] The AN message includes capability information. For description related to the capability information, please refer to step 601 in FIG6 , which will not be repeated here.

[0449] It should be noted that when the UE determines that it wishes to access the network simultaneously via two different paths, step 809 is executed. Exemplarily, before the UE sends the AN message to RAN2, the UE determines that it can access the network via two paths, and the UE determines that it has already accessed the network via the first path. Exemplarily, the UE can determine that it can access the network via two paths based on the dual connectivity information. For a description of dual connectivity, please refer to step 601 in Figure 6.

[0450] This embodiment is described by taking an example where the UE selects RAN2 as the second path to initiate a registration process and sends an AN message to RAN2.

[0451] Step 810: RAN2 selects AMF.

[0452] For the description of selecting AMF, please refer to step 602 and will not be repeated here.

[0453] It should be noted that the AMF selected by RAN2 can be AMF1 or AMF2 which is different from AMF1.

[0454] In this embodiment, RAN2 selects AMF2 as an example for description.

[0455] Step 811: RAN2 sends a registration request message to AMF2.

[0456] The registration request message includes capability information. For related description, refer to step 803 and will not be repeated here.

[0457] Step 812: AMF2 triggers the authentication and security procedure with the UE, AUSF, and UDM.

[0458] For related descriptions, please refer to the relevant instructions in step 204 in Figure 2, which will not be repeated here.

[0459] Step 813: AMF 2 sends a registration request to UDM.

[0460] The registration request includes instruction information. For related descriptions, please refer to the relevant descriptions in step 805 and will not be repeated here.

[0461] Step 814: The UDM allocates a path identifier (eg, a path identifier).

[0462] In one possible implementation, the UDM assigns a path identifier based on the indication information. For example, the UDM assigns different path identifiers to different paths for the same UE (e.g., the UE has the same SUPI on different paths). Alternatively, the UDM assigns a globally unique identifier to each path, i.e., the UDM does not distinguish between paths for the same or different UEs when assigning paths.

[0463] Optionally, the UDM may query the UE's subscription data based on the UE's identifier to determine whether the UE is allowed to access the network via dual connectivity. If the UE's subscription data indicates that the UE is allowed to access the network via dual connectivity, a path identifier is assigned. It is understood that if the UDM determines, based on the UE's subscription data, that the UE is not allowed to access the network using dual connectivity, the UDM will not assign a path identifier.

[0464] In a possible implementation, the UDM may store the information for distinguishing the second path and the path identifier 2, or the correspondence between the information for distinguishing the second path and the path identifier 2, in the subscription data or context information corresponding to the UE.

[0465] In this embodiment, description is made by taking the example in which the UDM assigns the path identifier 2 to the second path where the AMF2 is located.

[0466] Step 815: UDM sends a registration response to AMF2.

[0467] The registration response message includes path identifier 2.

[0468] Optionally, the registration response message also includes information used to distinguish the second path, such as a RAN identifier, so that the AMF can determine the corresponding second path based on the information used to distinguish the second path.

[0469] Exemplarily, the registration response is Nudm_UECM_Registration Response.

[0470] Step 816: AMF2 sends a Registration Accept message to the UE through RAN2.

[0471] The registration accept message includes the path identifier 2, and the path identifier 2 is used by the UE to determine / identify / recognize / mark the second path.

[0472] In one possible implementation, after AMF2 receives the path identifier, AMF2 may store the information used to distinguish the second path and the path identifier 2, or the correspondence between the information used to distinguish the second path and the path identifier 2, in the context information of the UE.

[0473] In one possible implementation, the UE stores path identifier 2. Exemplarily, the UE associates / maps path identifier 2 with one or more of the access technology type, RAN identifier, access type, or protocol stack, interface, or link corresponding to the current path. That is, the UE may associate / map path identifier 2 with the currently connected RAN 2. For example, the UE may associate / map path identifier 2 with the currently connected RAN 2 through circuit logic, line logic, protocol stack logic, etc. Subsequently, the UE may determine the second path corresponding to RAN 2 based on path identifier 2 and the association / mapping relationship.

[0474] Step 817 (optional): The UDM sends the path identifier and information for distinguishing the path to the UDR.

[0475] Exemplarily, the UDM sends the path identifier and information for distinguishing the path to the UDR via a data management create / update request message (eg, Nudr_DM_Create / Update request).

[0476] In one possible implementation, the path identifier and the information used to distinguish the paths include path identifier 1 and information used to distinguish the first path, and path identifier 2 and information used to distinguish the second path. For example, the information used to distinguish the paths is the AMF identifier, that is, the information used to distinguish the first path is the AMF1 identifier, and the information used to distinguish the second path is the AMF2 identifier. The UDM sends the AMF1 identifier and path identifier 1, as well as the AMF2 identifier and path identifier 2 to the UDR. In the subsequent session establishment process, the PCF can obtain the path identifier and the corresponding information used to distinguish the paths through the UDR.

[0477] It should be noted that this application does not limit the execution order of step 817. For example, step 817 can be executed after step 814.

[0478] Step 818 (optional): The UDR sends the path identifier and information for distinguishing the paths to the PCF.

[0479] In one possible implementation, the PCF generates a routing rule (e.g., a URSP) based on the path identifier and information for distinguishing paths. The routing rule includes the path identifier. The information for distinguishing paths can be used to determine path priority. The routing rule is subsequently sent to the UE, which uses the routing rule to select the path corresponding to the path identifier from multiple paths under the same access type for service transmission. When the routing rule is a URSP, it can be understood that an enhanced URSP is generated here.

[0480] In another possible implementation, the PCF receives path identifier 1 and information used to distinguish the first path from AMF1, and receives path identifier 2 and information used to distinguish the second path from AMF2. It should be noted that when the AMFs in the first and second paths are the same, for example, both are AMF1, the PCF may receive path identifier 1 and information used to distinguish the first path, as well as path identifier 2 and information used to distinguish the second path, from AMF1.

[0481] In a possible implementation, the PCF is an AM-PCF, which is mainly responsible for access mobility policy control.

[0482] Through the steps of method 800, when a UE accesses a network through two 3GPP access-type paths, the UDM assigns a path identifier, and the UE receives a first path identifier from the first path and a second path identifier from the second path. Thus, both the UE and the network can distinguish between the two different paths based on the path identifiers.

[0483] As shown in Figure 9, in combination with Figure 8 above, a method 900 applicable to the present application is introduced, which is applicable to UE accessing the network through multiple paths of the same access type (for example, two paths of 3GPP access type). The UDM first allocates a path identifier for the UE in the registration process and sends it to the UE. In the session establishment process, the SMF generates a diversion rule based on the path identifier, and the UE obtains the diversion rule. In one possible implementation, the UE executes the steps in method 900 after the registration process is completed on both paths. In another possible implementation, the UE executes the session establishment process of the first path of method 900 after the first path completes registration, and the UE executes the session establishment process of the second path of method 900 after the second path completes registration. Through method 900, the UE can determine the transmission path of the service data based on the path identifier. The method includes the following steps:

[0484] Step 901: The UE sends a session establishment request message to AMF1 through RAN1.

[0485] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0486] This embodiment is described by taking as an example that the UE selects RAN1 as the first path to initiate a session establishment process, and sends a session establishment request message to AMF1 through RAN1.

[0487] Step 902: AMF selects SMF.

[0488] In one possible implementation, AMF1 selects an SMF that supports dual connectivity based on capability information (e.g., UE supports dual connectivity). An SMF that supports dual connectivity can be understood as an SMF that can recognize newly added parameters in a message, such as a path identifier, information used to distinguish paths, and the like. The SMF supports the generation of a diversion rule including a path identifier (e.g., an enhanced diversion rule). The diversion rule including the path identifier can select a path transmission service corresponding to the path identifier from multiple paths under the same access type. For a description of capability information, refer to step 601 in FIG6 .

[0489] Step 903: AMF1 sends a session context request message to SMF.

[0490] Optionally, the session context request message includes a path identifier 1 and / or information for distinguishing the first path. Path identifier 1 is assigned by the UDM in step 806 in FIG8 , and the information for distinguishing the first path may be one or more of location information, access type, access technology, registration type, RAN identifier, and AMF identifier. The location information is, for example, a ULI, which includes a cell identifier, and the cell identifier is an identifier of the cell in RAN1 accessed by the UE. Since the cells accessed by the UE are different along different paths, different paths can be identified by the ULI. For related descriptions, refer to step 703 and will not be repeated here.

[0491] It should be noted that the session context request message may not include the path identifier 1 and / or the information used to distinguish the first path. Subsequently, the SMF obtains the path identifier and the information used to distinguish the path from the UDM.

[0492] In a possible implementation, the session context request message is a PDU session create session management context request (Nsmf_PDUSession_CreateSMContext Request) message, or a PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) message.

[0493] Step 904: SMF obtains the contract data from UDM.

[0494] Subscription data (e.g., session management subscription data) may include a path identifier and / or information for distinguishing a path. The path identifier and information for distinguishing a path may include path identifier 1 and information for distinguishing a first path, and path identifier 2 and information for distinguishing a second path. Path identifier 1 and information for distinguishing the first path are stored by the UDM in step 806 of FIG. 8 , while path identifier 2 and information for distinguishing the second path are stored by the UDM in step 814 of FIG. 8 .

[0495] In one possible implementation, the subscription data includes a path identifier. Exemplarily, the SMF sends information for distinguishing the first path to the UDM, which is information obtained by the SMF from AMF1 in step 903. The UDM determines the corresponding path identifier, i.e., path identifier 1, based on the information for distinguishing the first path, and sends the path identifier to the SMF. Exemplarily, the information for distinguishing the first path is the identifier of the AMF, i.e., AMF1. The SMF sends the SUPI of the UE and AMF1 to the UDM. The UDM queries the subscription data or context information corresponding to the UE based on the SUPI, and sends the path identifier (i.e., path identifier 1) corresponding to the AMF1 to the SMF based on the association between the stored path identifier and the information for distinguishing the first path.

[0496] In another possible implementation, the subscription data includes a path identifier and information for distinguishing paths. Exemplarily, the information for distinguishing paths is an AMF identifier, that is, the path identifier and the information for distinguishing paths are path identifier 1 corresponding to AMF1, and path identifier 2 corresponding to AMF2. The SMF receives a session context request message from AMF1 in step 903, so that the SMF can subsequently determine to send data to AMF1 based on path identifier 1. In another example, the UDM queries the subscription data or context information corresponding to the UE based on the SUPI, and sends AMF1 and the corresponding path identifier (i.e., path identifier 1) to the SMF, and sends AMF2 and the corresponding path identifier (i.e., path identifier 2) based on the association between the stored path identifier and the information for distinguishing paths.

[0497] It should be noted that, when the above-mentioned session context request message includes the path identifier 1, the subscription data may also not include the path identifier and the information used to distinguish the path. For the relevant description of the subscription data, please refer to step 303 in Figure 3.

[0498] In one possible implementation, after receiving the path identifier, the SMF may store the path identifier in the context information of the UE. Exemplarily, the SMF may store the association relationship between the path identifier 1 and the information used to distinguish the first path and the association relationship between the path identifier 2 and the information used to distinguish the second path in the context information of the UE.

[0499] Step 905: Refer to the relevant description of steps 705-720 in Figure 7, which will not be repeated here.

[0500] Through the steps of method 900, when a UE accesses the network via two 3GPP access paths, the UDM assigns a path identifier, and the UE receives a first path identifier from the first path and a second path identifier from the second path. Thus, both the UE and the network can distinguish between the two different paths based on the path identifiers. Furthermore, the UE receives a diversion rule containing the path identifiers. The UE can then, based on the diversion rule corresponding to the service data, transmit the service data along the path corresponding to the path identifier, thereby improving transmission efficiency.

[0501] As shown in Figure 10, a method 1000 applicable to the present application is introduced. The method is applicable to a UE accessing a network through multiple paths of the same access type (e.g., two paths of the 3GPP access type). In method 1000, the AMF assigns a path identifier to the UE during the registration process. During the session establishment process, the SMF generates a diversion rule based on the path identifier, and the UE obtains the path identifier and the diversion rule. Through method 1000, the UE can determine the transmission path of the service data based on the path identifier. The method includes the following steps:

[0502] Step 1001: Refer to the relevant description of steps 601-608 in Figure 6, which will not be repeated here.

[0503] Step 1002: AMF1 sends a Registration Accept message to the UE through RAN1.

[0504] It should be noted that the registration acceptance message sent by AMF1 through RAN1 does not include path identifier 1.

[0505] Step 1003: Refer to the relevant description of steps 610-617 in Figure 6, which will not be repeated here.

[0506] Step 1004: AMF2 sends a Registration Accept message to the UE through RAN2.

[0507] It should be noted that the registration acceptance message sent by AMF2 through RAN2 does not include path identifier 2.

[0508] Step 1005: Refer to the relevant description of steps 619-620 in Figure 6, which will not be repeated here.

[0509] Step 1006: Refer to the relevant description of steps 701-711 in Figure 7, which will not be repeated here.

[0510] Step 1007: AMF1 sends the diversion rule and path identifier 1 to the UE through RAN1.

[0511] In one possible implementation, the diversion rule includes path identifier 1 and a service descriptor. The UE can determine the path through which service data should be transmitted based on the diversion rule. For example, in the default active standby mode, the UE identifies the path corresponding to path identifier 1 as the active path. When the first path corresponding to path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor along the first path.

[0512] In another possible implementation, the offload rule includes path identifier 1, an offload mode, and a service descriptor. The UE can determine the path through which service data should be transmitted based on the offload rule. For example, if the UE is in active standby mode based on the offload mode and the path corresponding to path identifier 1 is the active path, the UE transmits the service flow corresponding to the service descriptor over the first path when the first path corresponding to path identifier 1 is available.

[0513] The path identifier 1 is used by the UE to determine / identify / recognize / mark the first path.

[0514] In one possible implementation, the UE stores the path identifier 1. Exemplarily, the UE associates / maps the path identifier 1 with one or more of the access technology, access type, protocol stack, interface, or link corresponding to the current path. Specifically, the UE may associate / map the path identifier 1 with the currently connected RAN 1. For example, the UE may associate / map the path identifier 1 with the currently connected RAN 1 through circuit logic, line logic, protocol stack logic, or other means. Subsequently, the UE may determine the first path corresponding to RAN 1 based on the path identifier 1 and the association / mapping relationship.

[0515] Step 1008: Refer to the relevant description of steps 714-719 in Figure 7, which will not be repeated here.

[0516] Step 1009: AMF2 sends the diversion rule and path identifier 2 to the UE through RAN2.

[0517] In one possible implementation, the diversion rule includes path identifier 1, path identifier 2, and a service descriptor. Based on the diversion rule, the UE can determine which path the service data should be transmitted through. For example, in the default active standby mode, the UE identifies the path corresponding to path identifier 1 as the active path. When the first path corresponding to path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor along the first path. Alternatively, when the first path is unavailable and the second path identified by path identifier 2 is available, the UE uses the second path to transmit the service flow corresponding to the service descriptor.

[0518] In another possible implementation, the diversion rules include path identifier 1, path identifier 2, diversion mode, and service descriptor. The UE can determine which path the service data should be transmitted through based on the diversion rules. For example, if the UE is in active standby mode based on the diversion mode, the path corresponding to path identifier 1 is the active path, and the path corresponding to path identifier 2 is the standby path, the UE transmits the service flow corresponding to the service descriptor along the first path when the first path corresponding to path identifier 1 is available. Alternatively, when the first path is unavailable and the second path identified by path identifier 2 is available, the UE uses the second path to transmit the service flow corresponding to the service descriptor.

[0519] The path identifier 2 is used by the UE to determine / identify / recognize / mark the second path.

[0520] In one possible implementation, the UE stores path identifier 2. Exemplarily, the UE associates / maps path identifier 2 with one or more of the access technology type, access type, or protocol stack, interface, or link corresponding to the current path. That is, the UE may associate / map path identifier 2 with the currently connected RAN2. For example, the UE may associate / map path identifier 2 with the currently connected RAN2 through circuit logic, line logic, protocol stack logic, etc. Subsequently, the UE may determine the second path corresponding to RAN2 based on path identifier 2 and the association / mapping relationship.

[0521] Through the steps of method 1000, when the UE accesses the network through two 3GPP access type paths, the AMF allocates a path identifier, and the UE receives a diversion rule including the first path identifier from the first path, and receives a diversion rule including the second path identifier from the second path, so that both the UE and the network can distinguish the two different paths according to the path identifier, and then the UE can transmit the service data through the path corresponding to the path identifier according to the diversion rule corresponding to the service data, thereby improving transmission efficiency.

[0522] As shown in FIG11 , a method 1100 applicable to the present application is described. This method is applicable to a UE accessing a network via multiple paths of the same access type (e.g., two 3GPP access type paths). In method 1100, the UDM assigns a path identifier to the UE during the registration process. During the session establishment process, the UE obtains the path identifier and the diversion rules. Through method 1100, the UE can determine the transmission path of service data based on the path identifier. The method includes the following steps:

[0523] Step 1101: Refer to the relevant description of steps 801-807 in Figure 8 and will not be repeated here.

[0524] Step 1102: AMF1 sends a Registration Accept message to the UE through RAN1.

[0525] It should be noted that the registration acceptance message sent by AMF1 through RAN1 does not include path identifier 1.

[0526] Step 1103: Refer to the relevant description of steps 809-815 in Figure 8 and will not be repeated here.

[0527] Step 1104: AMF2 sends a Registration Accept message to the UE through RAN2.

[0528] It should be noted that the registration acceptance message sent by AMF2 through RAN2 does not include path identifier 2.

[0529] Step 1105: Refer to the relevant description of steps 817-818 in Figure 8, which will not be repeated here.

[0530] Step 1106: Refer to the relevant description of steps 701-711 in Figure 7, which will not be repeated here.

[0531] Step 1107: AMF1 sends the diversion rule and path identifier 1 to the UE through RAN1.

[0532] For related descriptions, please refer to the relevant instructions of step 1007, which will not be repeated here.

[0533] Step 1108: Refer to the relevant description of steps 714-719 in Figure 7, which will not be repeated here.

[0534] Step 1109: AMF2 sends the diversion rule and path identifier 2 to the UE through RAN2.

[0535] For related descriptions, please refer to the relevant instructions of step 1009 in Figure 10, which will not be repeated here.

[0536] Through the steps of method 1100, when the UE accesses the network through two 3GPP access type paths, the UDM allocates a path identifier, and the UE receives a diversion rule including the first path identifier from the first path, and receives a diversion rule including the second path identifier from the second path, so that both the UE and the network can distinguish the two different paths according to the path identifier, and then the UE can transmit the service data through the path corresponding to the path identifier according to the diversion rule corresponding to the service data, thereby improving transmission efficiency.

[0537] As shown in Figure 12, a method 1200 applicable to the present application is introduced. The method is applicable to a UE accessing a network through multiple paths of the same access type (e.g., two paths of the 3GPP access type). In method 1200, during the session establishment process, the AMF assigns a path identifier to the UE, the SMF generates a diversion rule based on the path identifier, and the UE obtains the path identifier and the diversion rule. Through method 1200, the UE can determine the transmission path of the service data based on the path identifier. The method includes the following steps:

[0538] Step 1201: The UE sends a session establishment request message to AMF1 through RAN1.

[0539] The session establishment request message includes capability information. For a description of the capability information, please refer to step 601 in FIG. 6 , which will not be repeated here.

[0540] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0541] This embodiment is described by taking the example of the UE selecting RAN1 as the first path to initiate the session establishment process and sending a session establishment request message to AMF1 via RAN1. Step 1202: AMF1 allocates a path identifier (eg, a path identifier).

[0542] For a description of the AMF1 allocation path, please refer to step 605 in FIG6 .

[0543] In this embodiment, description is made by taking AMF1 assigning path identifier 1 to the first path as an example.

[0544] In one possible implementation, AMF1 selects an SMF that supports dual connectivity based on capability information (e.g., whether the UE supports dual connectivity). For a related description, please refer to step 702 in Figure 7.

[0545] Step 1203: AMF1 sends path identifier 1 and information used to distinguish the first path to SMF.

[0546] The information used to distinguish the first path may be one or more of location information, access type, access technology, registration type, RAN identifier, and AMF identifier. The location information is, for example, ULI, which includes a cell identifier, and the cell identifier is the identifier of the cell that the UE accesses in RAN1. Since the cells accessed by the UE are different in different paths, different paths can be identified by ULI. Exemplarily, the information used to distinguish the first path is RAT type, for example, the RAT type corresponding to the first path connecting RAN1 and AMF1 is 6G, and the RAT type corresponding to the second path connecting RAN2 and AMF2 is 5G. Therefore, the SMF can subsequently determine to send data to AMF1 on the first path corresponding to 6G based on path identifier 1.

[0547] In one possible implementation, AMF1 sends the path identifier 1 and the information used to distinguish the first path to SMF through a PDU session create session management context request (Nsmf_PDUSession_CreateSMContext Request) message or a PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) message.

[0548] Step 1204: The SMF sends a policy request message to the PCF.

[0549] The policy request message includes a path identifier and information for distinguishing paths.

[0550] In one possible implementation, the SMF selects a PCF that supports multiple connections based on the path identifier and sends a policy request message to the PCF that supports multiple connections. A PCF that supports multiple connections can be understood as one that can recognize newly added parameters, such as path identifiers. The PCF supports the generation of policy rules (e.g., enhanced PCC rules) that include path identifiers. The policy rules are used to select the path transmission service corresponding to the path identifier among multiple paths under the same access type.

[0551] In a possible implementation, the policy request message is a policy association establishment request message (SM Policy Association Establishment Request) message, or a policy association modification request message (SM Policy Association Modification Request) message.

[0552] Step 1205: Refer to the relevant description of steps 708-711 in Figure 7, which will not be repeated here.

[0553] Step 1206: AMF1 sends the diversion rule and path identifier 1 to the UE through RAN1.

[0554] For related descriptions, please refer to the relevant instructions of step 1007 in Figure 10, which will not be repeated here.

[0555] Step 1207: The UE sends a session establishment request message to AMF2 through RAN 2.

[0556] The session establishment request message includes capability information. For a description of the capability information, please refer to step 601 in FIG. 6 , which will not be repeated here.

[0557] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0558] This embodiment is described by taking as an example that the UE selects RAN1 as the first path to initiate a session establishment process, and sends a session establishment request message to AMF1 through RAN1.

[0559] Step 1208: AMF2 allocates a path identifier (eg, a path identifier).

[0560] For a description of the AMF2 allocation path, please refer to step 614 in FIG. 6 .

[0561] In this embodiment, description is made by taking AMF2 assigning path identifier 2 to the second path as an example.

[0562] Step 1209: AMF2 sends path identifier 2 and information used to distinguish the second path to SMF.

[0563] The information used to distinguish the second path may be one or more of location information, access type, access technology, registration type, RAN identifier, and AMF identifier. The location information is, for example, ULI, which includes a cell identifier, and the cell identifier is the identifier of the cell in RAN1 that the UE accesses. Since the cells accessed by the UE are different in different paths, different paths can be identified by ULI. Exemplarily, the information used to distinguish the second path is RAT type, for example, the RAT type corresponding to the first path connecting RAN1 and AMF1 is 6G, and the RAT type corresponding to the second path connecting RAN2 and AMF2 is 5G. Therefore, the SMF can subsequently determine to send data to AMF2 on the second path corresponding to 5G based on path identifier 2.

[0564] Step 1210 (optional): The SMF sends the path identifier 2 and information for distinguishing the second path to the PCF.

[0565] In a possible implementation, the path identifier 2 and the information used to distinguish the second path are sent via a policy request message, such as a SM Policy Association Establishment Request message or a SM Policy Association Modification Request message.

[0566] Step 1211: Refer to the relevant description of steps 717-719 in Figure 7, which will not be repeated here.

[0567] Step 1212: AMF2 sends the diversion rule and path identifier 2 to the UE through RAN2.

[0568] For related descriptions, please refer to the relevant instructions of step 1009 in Figure 10, which will not be repeated here.

[0569] Through the steps of method 1200, when the UE accesses the network through two 3GPP access type paths, the AMF allocates a path identifier, and the UE receives a diversion rule including the first path identifier from the first path, and receives a diversion rule including the second path identifier from the second path, so that both the UE and the network can distinguish the two different paths according to the path identifier, and then the UE can transmit the service data through the path corresponding to the path identifier according to the diversion rule corresponding to the service data, thereby improving transmission efficiency.

[0570] As shown in FIG13 , a method 1300 applicable to the present application is introduced. The method is applicable to a UE accessing a network through multiple paths of the same access type (e.g., two paths of the 3GPP access type). In method 1300, during the session establishment process, the UDM assigns a path identifier to the UE, the SMF generates a diversion rule based on the path identifier, and the UE obtains the path identifier and the diversion rule. Through method 1300, the UE can determine the transmission path of the service data based on the path identifier. The method includes the following steps:

[0571] Step 1301: The UE sends a session establishment request message to AMF1 through RAN1.

[0572] The session establishment request message includes capability information. For a description of the capability information, please refer to step 601 in FIG. 6 , which will not be repeated here.

[0573] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0574] This embodiment is described by taking as an example that the UE selects RAN1 as the first path to initiate a session establishment process, and sends a session establishment request message to AMF1 through RAN1.

[0575] Step 1302: AMF1 sends information for distinguishing the first path to SMF.

[0576] The information used to distinguish the first path may be one or more of location information, access type, access technology type, registration type, RAN identifier, and AMF identifier. The location information is, for example, ULI, which includes a cell identifier, and the cell identifier is the identifier of the cell that the UE accesses in RAN1. Since the cells accessed by the UE are different in different paths, different paths can be identified by ULI. Exemplarily, the information used to distinguish the first path is RAT type, for example, the RAT type corresponding to the first path connecting RAN1 and AMF1 is 6G, and the RAT type corresponding to the second path connecting RAN2 and AMF2 is 5G. Therefore, the SMF can subsequently determine to send data to AMF1 on the first path corresponding to 6G based on path identifier 1.

[0577] In one possible implementation, the information used to distinguish the first path implicitly indicates that the UE supports multi-radio capabilities; or indicates that the UE supports multi-registration capabilities, or indicates that the UE accesses the network via multi-connectivity. It should be noted that the name of the multi-radio capability can also be replaced by any of the names of the extended dual connectivity or multi-connectivity in the dual connectivity architecture described above.

[0578] In another possible implementation, AMF1 sends path identifier allocation information to SMF, where the path identifier allocation information indicates that the UE supports multiple wireless capabilities; or indicates that the UE supports multiple registration capabilities, or indicates that the UE accesses the network through multiple connections.

[0579] In a possible implementation, AMF1 sends information for distinguishing the first path to SMF through a PDU session create session management context request (Nsmf_PDUSession_CreateSMContext Request) message or a PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) message.

[0580] Step 1303: The SMF sends information for distinguishing the first path to the UDM.

[0581] In a possible implementation, the information used to distinguish the first path implicitly indicates that the UE supports multi-radio capabilities, or indicates an allocation path identifier.

[0582] In another possible implementation, the SMF sends path identifier allocation information to the UDM, where the path identifier allocation information indicates the allocation of the path identifier.

[0583] Step 1304: The UDM allocates a path identifier (eg, a path identifier).

[0584] In a possible implementation, the UDM assigns a path identifier according to information used to distinguish the first path or path identifier assignment information.

[0585] Optionally, the UDM may query the UE's subscription data to determine whether the UE is allowed to access the network via dual connectivity. If the UE's subscription data indicates that the UE is allowed to access the network via dual connectivity, a path identifier is assigned. It is understood that if the UDM determines, based on the UE's subscription data, that the UE is not allowed to access the network using dual connectivity, the UDM will not assign a path identifier.

[0586] In a possible implementation, the UDM may store the information used to distinguish the first path and the path identifier 1, or the correspondence between the information used to distinguish the first path and the path identifier 1, in the subscription data or context information corresponding to the UE.

[0587] In this embodiment, description is made by taking the example of the UDM assigning the path identifier 1 to the first path where the AMF1 is located.

[0588] Step 1305: UDM sends path identifier 1 to SMF.

[0589] Optionally, the UDM also sends information for distinguishing the first path to the SMF.

[0590] Step 1306: The SMF sends a policy request message to the PCF.

[0591] The policy request message includes a path identifier and information for distinguishing paths. For related descriptions, refer to step 1204 in FIG12 , which will not be repeated here.

[0592] Step 1307: Refer to the relevant description of steps 708-711 in Figure 7, which will not be repeated here.

[0593] Step 1308: AMF1 sends the diversion rule and path identifier 1 to the UE through RAN1.

[0594] For related descriptions, please refer to the relevant instructions of step 1007 in Figure 10, which will not be repeated here.

[0595] Step 1309: The UE sends a session establishment request message to AMF2 through RAN 2.

[0596] The session establishment request message includes capability information. For a description of the capability information, please refer to step 601 in FIG. 6 , which will not be repeated here.

[0597] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0598] This embodiment is introduced by taking an example in which the UE selects RAN2 as the first path to initiate a session establishment process and sends a session establishment request message to AMF2 through RAN2.

[0599] Step 1310: AMF1 sends information for distinguishing the second path to SMF.

[0600] The information used to distinguish the second path may be one or more of location information, access type, access technology type, registration type, RAN identifier, and AMF identifier. The location information may be, for example, a ULI, which includes a cell identifier, which is the identifier of the cell accessed by the UE in RAN1. Because the UE accesses different cells along different paths, the ULI can be used to identify different paths.

[0601] In a possible implementation, the information used to distinguish the second path implicitly indicates that the UE supports multi-radio capabilities; or indicates that the UE supports multi-registration capabilities, or indicates that the UE accesses the network through multi-connection.

[0602] In another possible implementation, AMF1 sends path identifier allocation information to SMF, where the path identifier allocation information indicates that the UE supports multiple wireless capabilities; or indicates that the UE supports multiple registration capabilities, or indicates that the UE accesses the network through multiple connections.

[0603] In a possible implementation, AMF1 sends information for distinguishing the second path to SMF through a PDU session create session management context request (Nsmf_PDUSession_CreateSMContext Request) message or a PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) message.

[0604] Step 1311: The SMF sends information for distinguishing the second path to the UDM.

[0605] In a possible implementation, the information used to distinguish the second path implicitly indicates that the UE supports multi-radio capabilities, or indicates an allocation path identifier.

[0606] In another possible implementation, the SMF sends path identifier allocation information to the UDM, where the path identifier allocation information indicates the allocation of the path identifier.

[0607] Step 1312: The UDM allocates a path identifier (eg, a path identifier).

[0608] In one possible implementation, the UDM assigns a path identifier based on information used to distinguish the second path or path identifier allocation information. For example, the UDM assigns different path identifiers to different paths of the same UE (for example, the SUPI of the UE on different paths is the same). Or the UDM assigns a globally unique identifier to each path, that is, the UDM does not distinguish between different paths of the same or different UEs when assigning path identifiers. Optionally, the UDM can query the subscription data of the UE to determine whether the UE is allowed to access the network through dual connectivity. The path identifier is assigned when the UE's subscription data indicates that the UE is allowed to access the network through dual connectivity. It is understandable that when the UDM determines that the UE is not allowed to use dual connectivity to access the network based on the UE's subscription data, the UDM will not assign a path identifier.

[0609] In a possible implementation, the UDM may store the information for distinguishing the second path and the path identifier 2, or the correspondence between the information for distinguishing the second path and the path identifier 2, in the subscription data or context information corresponding to the UE.

[0610] In this embodiment, description is made by taking the example in which the UDM assigns the path identifier 2 to the second path where the AMF2 is located.

[0611] Step 1313: UDM sends path identifier 2 to SMF.

[0612] Optionally, the UDM also sends information for distinguishing the second path to the SMF.

[0613] Step 1314 (optional): The SMF sends the path identifier 2 and information for distinguishing the second path to the PCF.

[0614] In a possible implementation, the path identifier 2 and the information used to distinguish the second path are sent via a policy request message, such as a SM Policy Association Establishment Request message or a SM Policy Association Modification Request message.

[0615] Step 1315: Refer to the relevant description of steps 717-719 in Figure 7, which will not be repeated here.

[0616] Step 1316: AMF2 sends the diversion rule and path identifier 2 to the UE through RAN2.

[0617] For related descriptions, please refer to the relevant instructions of step 1009 in Figure 10, which will not be repeated here.

[0618] Through the steps of method 1300, when the UE accesses the network through two 3GPP access type paths, the UDM allocates a path identifier, and the UE receives a diversion rule including the first path identifier from the first path, and receives a diversion rule including the second path identifier from the second path, so that both the UE and the network can distinguish the two different paths based on the path identifier, and then the UE can transmit the service data through the path corresponding to the path identifier according to the diversion rule corresponding to the service data, thereby improving transmission efficiency.

[0619] As shown in FIG14 , a method 1400 applicable to the present application is introduced. The method is applicable to a UE accessing a network via multiple paths of the same access type (e.g., two 3GPP access type paths). In method 1400, during the session establishment process, the SMF assigns a path identifier to the UE, the SMF generates a diversion rule based on the path identifier, and the UE obtains the path identifier and the diversion rule. Through method 1400, the UE can determine the transmission path of the service data based on the path identifier. The method includes the following steps:

[0620] Step 1401: The UE sends a session establishment request message to AMF1 through RAN1.

[0621] The session establishment request message includes capability information. For a description of the capability information, please refer to step 601 in FIG. 6 , which will not be repeated here.

[0622] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0623] This embodiment is described by taking as an example that the UE selects RAN1 as the first path to initiate a session establishment process, and sends a session establishment request message to AMF1 through RAN1.

[0624] Step 1402: AMF1 sends information for distinguishing the first path to SMF.

[0625] The information used to distinguish the first path may be one or more of location information, access type, access technology type, registration type, RAN identifier, and AMF identifier. The location information is, for example, ULI, which includes a cell identifier, and the cell identifier is the identifier of the cell that the UE accesses in RAN1. Since the cells accessed by the UE are different in different paths, different paths can be identified by ULI. Exemplarily, the information used to distinguish the first path is RAT type, for example, the RAT type corresponding to the first path connecting RAN1 and AMF1 is 6G, and the RAT type corresponding to the second path connecting RAN2 and AMF2 is 5G. Therefore, the SMF can subsequently determine to send data to AMF1 on the first path corresponding to 6G based on path identifier 1.

[0626] In a possible implementation, the information used to distinguish the first path implicitly indicates that the UE supports multi-radio capabilities; or indicates that the UE supports multi-registration capabilities, or indicates that the UE accesses the network through multi-connection.

[0627] In another possible implementation, AMF1 sends path identifier allocation information to SMF, where the path identifier allocation information indicates that the UE supports multiple wireless capabilities; or indicates that the UE supports multiple registration capabilities, or indicates that the UE accesses the network through multiple connections.

[0628] In a possible implementation, AMF1 sends information for distinguishing the first path to SMF through a PDU session create session management context request (Nsmf_PDUSession_CreateSMContext Request) message or a PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) message.

[0629] Step 1403: The SMF allocates a path identifier (eg, a path identifier).

[0630] In a possible implementation, the SMF allocates a path identifier according to information used to distinguish the first path or path identifier allocation information.

[0631] In this embodiment, an example is given in which SMF assigns path identifier 1 to the first path where AMF1 is located.

[0632] In a possible implementation, the SMF may store the information used to distinguish the first path and the path identifier 1, or the correspondence between the information used to distinguish the first path and the path identifier 1, in the context information corresponding to the UE.

[0633] Step 1404: The SMF sends a policy request message to the PCF.

[0634] The policy request message includes a path identifier and information for distinguishing paths. For related descriptions, refer to step 1204 in FIG12 , which will not be repeated here.

[0635] Step 1405: Refer to the relevant description of steps 708-711 in Figure 7, which will not be repeated here.

[0636] Step 1406: AMF1 sends the diversion rule and path identifier 1 to the UE through RAN1.

[0637] For related descriptions, please refer to the relevant instructions of step 1007 in Figure 10, which will not be repeated here.

[0638] Step 1407: The UE sends a session establishment request message to AMF2 through RAN 2.

[0639] The session establishment request message includes capability information. For a description of the capability information, please refer to step 601 in FIG. 6 , which will not be repeated here.

[0640] In a possible implementation, the session establishment request message is a PDU Session Establishment Request message. For a description of the PDU Session Establishment Request message, reference may be made to step 301 in FIG. 3 .

[0641] This embodiment is introduced by taking an example in which the UE selects RAN2 as the first path to initiate a session establishment process and sends a session establishment request message to AMF2 through RAN2.

[0642] Step 1408: AMF1 sends information for distinguishing the second path to SMF.

[0643] The information used to distinguish the second path may be one or more of location information, access type, access technology type, registration type, RAN identifier, and AMF identifier. The location information may be, for example, a ULI, which includes a cell identifier, which is the identifier of the cell accessed by the UE in RAN1. Because the UE accesses different cells along different paths, the ULI can be used to identify different paths.

[0644] In a possible implementation, the information used to distinguish the second path implicitly indicates that the UE supports multi-radio capabilities; or indicates that the UE supports multi-registration capabilities, or indicates that the UE accesses the network through multi-connection.

[0645] In another possible implementation, AMF1 sends path identifier allocation information to SMF, where the path identifier allocation information indicates that the UE supports multiple wireless capabilities; or indicates that the UE supports multiple registration capabilities, or indicates that the UE accesses the network through multiple connections.

[0646] In a possible implementation, AMF1 sends information for distinguishing the second path to SMF through a PDU session create session management context request (Nsmf_PDUSession_CreateSMContext Request) message or a PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) message.

[0647] Step 1409: The SMF allocates a path identifier (eg, a path identifier).

[0648] In one possible implementation, the SMF assigns a path identifier based on the information used to distinguish the second path or the path identifier assignment information. For example, the SMF assigns different path identifiers to different paths of the same UE (e.g., the SUPI of the UE on different paths is the same). Alternatively, the SMF assigns a globally unique identifier to each path, i.e., the SMF does not distinguish between different paths of the same or different UEs when assigning path identifiers.

[0649] In this embodiment, an example is given in which SMF assigns path identifier 2 to the second path where AMF2 is located.

[0650] In a possible implementation, the SMF may store the information used to distinguish the second path and the path identifier 2, or the correspondence between the information used to distinguish the second path and the path identifier 2, in the context information corresponding to the UE.

[0651] Step 1410 (optional): The SMF sends the path identifier 2 and information for distinguishing the second path to the PCF.

[0652] In a possible implementation, the path identifier 2 and the information used to distinguish the second path are sent via a policy request message, such as a SM Policy Association Establishment Request message or a SM Policy Association Modification Request message.

[0653] Step 1411: Refer to the relevant description of steps 717-719 in Figure 7, which will not be repeated here.

[0654] Step 1412: AMF2 sends the diversion rule and path identifier 2 to the UE through RAN2.

[0655] For related descriptions, please refer to the relevant instructions of step 1009 in Figure 10, which will not be repeated here.

[0656] Through the steps of method 1400, when the UE accesses the network through two 3GPP access type paths, the SMF allocates a path identifier, the UE receives a diversion rule including the first path identifier from the first path, and receives a diversion rule including the second path identifier from the second path, so that both the UE and the network can distinguish the two different paths based on the path identifier, and then the UE can transmit the service data through the path corresponding to the path identifier according to the diversion rule corresponding to the service data, thereby improving transmission efficiency.

[0657] The following describes a method 1500 provided by an embodiment of the present application in conjunction with Figure 15. It should be noted that Figure 15 is used as an example for description herein, and this method is applicable to any of the processes in Figures 6 to 14 above. The communication device may be a terminal device (e.g., UE 110 in Figure 1), or a chip (system) that may be provided in the terminal device. In other words, method 1500 may be executed by the terminal device, or by a chip (system) in the terminal device.

[0658] The communication method flow diagram shown in FIG15 may include the following steps:

[0659] Step 1501: The first network element obtains capability information.

[0660] In a possible implementation manner, the communication device sends a capability message to the first network element.

[0661] In another possible implementation, the first network element obtains the capability information of the communication device from the subscription data. The first network element is an AMF. For instructions on obtaining the capability information from the subscription data, please refer to step 608 in Figure 6.

[0662] In one possible implementation, the first network element is AMF, and the relevant instructions for the communication device sending capability information to AMF can refer to steps 601 to 603 in Figure 6.

[0663] In one possible implementation, the AMF selects a session management network element that supports multiple connections based on the capability information; wherein the session management network element that supports multiple connections is a session management network element that supports generating a diversion rule including a first path identifier. The session management network element that supports multiple connections can be understood as a session management network element that can recognize newly added parameters, such as a path identifier, and supports generating a diversion rule including a path identifier.

[0664] In another possible implementation, the first network element is a UDM. For related descriptions of how the communication device sends capability information to the UDM, reference may be made to steps 801 to 805 in FIG. 8 .

[0665] In another possible implementation, the first network element is SMF, and the relevant instructions on how the communication device sends capability information to the SMF can be referred to steps 1401 to 1402 in Figure 14.

[0666] Step 1502: The first network element allocates a first path identifier.

[0667] In one possible implementation, the first network element is AMF, and the relevant instructions for allocating path identifiers can be referred to step 605 in Figure 6.

[0668] In one possible implementation, the AMF sends the first path identifier to the session management network element. For related descriptions, please refer to step 703 in Figure 7. The AMF receives the diversion rule including the first path identifier from the session management network element. For related descriptions, please refer to step 711 in Figure 7, and sends the diversion rule to the communication device. For related descriptions, please refer to steps 712-713 in Figure 7.

[0669] In another possible implementation, the first network element is a UDM, and the relevant description of allocating the path identifier can be referred to step 806 in FIG. 8 .

[0670] In one possible implementation, the UDM sends the first path identifier and information for distinguishing paths to the session management network element and / or the data storage network element. The information for distinguishing paths is used by the session management network element to distinguish different paths. For details on the UDM sending the first path identifier and information for distinguishing paths to the session management network element, see step 904 in Figure 9 . For details on the UDM sending the first path identifier and information for distinguishing paths to the data storage network element, see step 817 in Figure 8 . The data storage network element may then send this information to the policy control network element.

[0671] In another possible implementation, the first network element is an SMF, and the relevant instructions for allocating path identifiers can be referred to step 1403 in Figure 14.

[0672] In one possible implementation, the SMF generates a diversion rule including a first path identifier and sends the diversion rule to the communication device, where the diversion rule is used by the communication device to determine a transmission path for the service flow. For related descriptions, please refer to step 710 in FIG. 7 .

[0673] Step 1503: The first network element sends a first path identifier to the communication device.

[0674] In one possible implementation, the first network element is AMF, and the relevant instructions for sending the first path identifier to the communication device can refer to step 609 in Figure 6, or step 1007 in Figure 10, or step 1206 in Figure 12.

[0675] In another possible implementation, the first network element is a UDM, and related instructions for sending the first path identifier to the communication device can refer to steps 807-808 in Figure 8, or steps 1106-1107 in Figure 11, or steps 1307-1308 in Figure 13.

[0676] In another possible implementation, the first network element is an SMF, and for related instructions on sending the first path identifier to the communication device, reference may be made to steps 1405-1406 in FIG. 14 .

[0677] Assigning a path identifier through a session flow enables the use of the path identifier only when the UE needs to establish a multi-access session. In this case, the core network device that assigns the path identifier can be an AMF, UDM, SMF, or PCF. The present invention does not limit the first network element that assigns the path identifier. The path identifier can be at a path granularity or a session granularity. When the path identifier is at a session granularity, different sessions can be established through the same access network, and different path identifiers correspond to different sessions.

[0678] Step 1504: The communication device determines the transmission path of the service flow according to the diversion rule including the path identifier.

[0679] In one possible implementation, the communication device receives a diversion rule including a first path identifier. For related instructions, please refer to step 713 in Figure 7, or step 1007 in Figure 10, or step 1107 in Figure 11, or 1206 in Figure 12, or 1308 in Figure 13, or 1406 in Figure 14.

[0680] In one possible implementation, the diversion rule includes service flow information and a first path identifier. The communication device determines that the service flow corresponding to the uplink service flow information is transmitted on the first path based on the first path identifier. For related instructions, please refer to step 713 in Figure 7.

[0681] A communication device can first obtain a path identifier through a registration process, thereby identifying multiple different paths currently connected under the same access type. Furthermore, when a communication device establishes a session through multiple different paths under the same access type, it can use the diversion rules containing the path identifier to determine which transmission path the service data should use. This allows the service data to be transmitted along the path corresponding to the path identifier, thereby improving transmission efficiency.

[0682] The communication device can also obtain the path identifier when establishing a session through multiple different paths under the same access type. Then, the diversion rule containing the path identifier can be used to determine which transmission path the service data should be transmitted through, and the service data can be transmitted through the path corresponding to the path identifier, thereby improving transmission efficiency.

[0683] The following describes a method 1600 provided in an embodiment of the present application in conjunction with FIG16. It should be noted that FIG16 is used as an example for description herein, and this method is applicable to any of the processes in FIG6 to FIG15 above.

[0684] The communication method flow diagram shown in FIG16 may include the following steps:

[0685] Step 1601: A first network element obtains a first path identifier.

[0686] In one possible implementation, the first network element is SMF. For relevant instructions on how SMF obtains the first path identifier, please refer to step 703, step 704 or step 708 in Figure 7, or step 1203 in Figure 12, or step 1305 in Figure 13, or step 1403 in Figure 14.

[0687] Step 1602: The first network element generates a diversion rule.

[0688] In a possible implementation, the first network element is an SMF, and the SMF generates a diversion rule according to the first path identifier. For related instructions, please refer to step 710 in Figure 7.

[0689] Step 1603: The first network element sends the diversion rule to the second network element.

[0690] In a possible implementation, the second network element is a UPF, and the first network element may send diversion rules to the UPF for related instructions, which may refer to step 710 in FIG. 7 .

[0691] In one possible implementation, the UPF can learn through a diversion rule including a path identifier which transmission path the service data should take to transmit downlink service data, and transmit the service data through the path corresponding to the path identifier to improve transmission efficiency.

[0692] The above description of the communication method embodiment of the present application is described in detail in conjunction with Figures 6 to 16. The following description of the communication device embodiment of the present application is described in detail in conjunction with Figures 17 to 19. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.

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

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

[0695] In another possible design, the device 1000 can implement steps or processes corresponding to those performed by the communication device in the above method embodiment, wherein the transceiver unit 1010 is used to perform the transceiver-related operations of the communication device in the above method embodiment, and the processing unit 1020 is used to perform the processing-related operations of the communication device in the above method embodiment.

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

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

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

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

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

[0701] In a possible implementation, the device 2000 is used to implement various processes and steps corresponding to the first network element in the above method embodiment.

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

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

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

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

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

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

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

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

[0710] As a solution, the chip system 3000 is used to implement the operations performed by the first network element in the above method embodiments.

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

[0712] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods executed by the communication device, access and mobility management network element, and wireless access network equipment in the above-mentioned method embodiments.

[0713] An embodiment of the present application also provides a computer program product, comprising computer program code or instructions. When the computer program code or instructions are executed on a computer, the computer implements the methods performed by the communication device, access and mobility management network element, and wireless access network equipment in the above-mentioned method embodiments.

[0714] An embodiment of the present application also provides a communication system, including the aforementioned communication device and a first network element, and optionally, may also include a RAN, a UDR or a PCF.

[0715] The explanation and beneficial effects of the relevant contents of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, and will not be repeated here. In order to facilitate the understanding of the above-mentioned embodiments provided by this application, the following points are explained:

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

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

[0718] 3) Throughout this application, the terms "first," "second," and various numerical references (e.g., #1, #2, etc.) are used to distinguish between different messages for ease of description and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish between different messages, rather than to describe a specific order or precedence. It should be understood that such references are interchangeable, where appropriate, to allow for the description of scenarios beyond the embodiments of this application.

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

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

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

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

[0723] 6) In this application, "protocol" may refer to a standard protocol in the field of communications, such as 5G protocol, NR protocol, and related protocols used in future communication systems, which are not limited in this application. "Predefined" may include pre-definition. For example, protocol definition. "Preconfiguration" can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in the device. This application does not limit its specific implementation method.

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

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

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

[0727] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

[0730] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

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

Claims

1. A communication method, characterized in that, The method includes: A first network element obtains capability information, where the capability information indicates that a communication device supports multi-connection. The multi-connection includes at least two paths with the same access type, and the at least two paths include a first path connecting the communication device and a first radio access network device; The first network element allocates a first path identifier corresponding to the first path according to the capability information; The first network element sends the first path identifier to the communication device through the first path, and the first path identifier is used for the communication device to determine the first path among the at least two paths.

2. The method according to claim 1, wherein The first network element obtaining the capability information includes: The first network element receives the capability information from the first path; or, The first network element obtains the capability information from the subscription data of the communication device.

3. The method according to claim 1 or 2, characterized in that, The first network element is an access and mobility management network element, and the method further includes: The access and mobility management network element sends the first path identifier to a session management network element; Receives a traffic splitting rule including the first path identifier from the session management network element; and Sends the traffic splitting rule to the communication device, and the traffic splitting rule is used for the communication device to determine a transmission path of a service flow, and the transmission path is one or more paths among the at least two paths.

4. The method according to claim 3, wherein The method further includes: The access and mobility management network element selects a session management network element that supports multi-connection according to the capability information; where the session management network element that supports multi-connection is a session management network element that supports generating a traffic splitting rule including the first path identifier.

5. The method according to claim 1 or 2, characterized in that, The first network element is an access and mobility management network element, and the method further includes: The access and mobility management network element obtains information for differentiating paths, and the information for differentiating paths is different among the at least two paths.

6. The method according to claim 5, characterized in that, The access and mobility management network element obtaining the information for differentiating paths includes: The access and mobility management network element receives the information for differentiating paths from the first radio access network device; or, The access and mobility management network element determines the information for differentiating paths according to the first radio access network device.

7. The method according to claim 5 or 6, characterized in that, The method further includes: The access and mobility management network element stores the first path identifier and the information for differentiating paths.

8. The method according to any one of claims 5-7, characterized in that, The method further includes: The access and mobility management network element sends the first path identifier and the information for differentiating paths to a data management network element.

9. The method according to claim 8, wherein The method further includes: The access and mobility management network element selects a data management network element that supports multi-connection according to the capability information; where the data management network element that supports multi-connection is a data management network element that supports storing multiple contexts of the communication device.

10. The method according to any one of claims 5-9, characterized in that, The information for differentiating paths is one or more of the following: location information, access technology type, registration type, identifier of the first radio access network device; wherein, the location information indicates information of an access node to which the communication device accesses the network; the access technology type indicates an access technology type by which the communication device accesses the network through the first path; the registration type indicates a registration type by which the communication device registers to the network through the first path.

11. The method according to claim 1 or 2, characterized in that, The first network element is a data management network element. Before the first network element allocates a first path identifier corresponding to the first path according to the capability information, the method further includes: The data management network element queries subscription data of the communication device; When the subscription data of the communication device is authorized to allow access to the network through multi-connection, allocate the first path identifier.

12. The method according to claim 1 or 2, characterized in that, The first network element is a data management network element, and the method further includes: The data management network element receives information for differentiating paths from an access and mobility management network element, and the information for differentiating paths is different among the at least two paths.

13. The method according to claim 12, wherein The method further includes: The data management network element stores the first path identifier and the information for differentiating paths.

14. The method according to claim 12 or 13, characterized in that, The method further includes: The data management network element sends the first path identifier and the information for differentiating paths to a session management network element and / or a data storage network element.

15. The method according to claim 1 or 2, characterized in that, The first network element is a session management network element, and the method further includes: The session management network element receives information for differentiating paths from an access and mobility management network element, and the information for differentiating paths is different among the at least two paths.

16. The method according to claim 15, wherein The method further includes: The session management network element stores the first path identifier and the information for differentiating paths.

17. The method according to claim 15 or 16, characterized in that, The method further includes: The session management network element sends the first path identifier and the information for differentiating paths to the access and mobility management network element.

18. The method according to any one of claims 15-17, characterized in that, The method further includes: The session management network element generates a traffic splitting rule including the first path identifier; Send the traffic splitting rule to the communication device, and the traffic splitting rule is used for the communication device to determine a transmission path of a traffic flow.

19. The method according to claim 18, characterized in that, The traffic splitting rule includes a priority of the first path, and the information for differentiating paths is used to determine the priority of the first path.

20. The method according to any one of claims 15-19, characterized in that, The method further includes: The session management network element selects a user plane network element supporting multi-connection according to the capability information; wherein, the user plane network element supporting multi-connection is a user plane network element that supports data splitting according to a traffic splitting rule including the first path identifier.

21. A communication method, characterized in that, The method includes: A communication device receives a first path identifier through a first path connecting the communication device and a first radio access network device, and receives a second path identifier through a second path connecting the communication device and a second radio access network device; The communication device receives a traffic splitting rule, and the traffic splitting rule includes traffic flow information, and the first path identifier and / or the second path identifier; The communication device determines a transmission path of a service flow corresponding to the service flow information according to the first path identifier and / or the second path identifier.

22. The method according to claim 21, wherein Before the communication device receives the first path identifier and the second path identifier, the method further includes: The communication device sends capability information, where the capability information indicates that the communication device supports multi-connection, and the multi-connection includes at least two paths with the same access type, and the at least two paths include the first path and the second path.

23. The method according to claim 21 or 22, characterized in that, The traffic splitting rule includes the priority of the first path and / or the priority of the second path. Before the communication device determines a transmission path of the service flow according to the first path identifier and / or the second path identifier, the method further includes: The communication device determines a path identifier of a transmission path of the service flow according to the priority of the first path and / or the priority of the second path.

24. The method according to any one of claims 21-23, characterized in that, The communication device determines a transmission path of a service flow corresponding to the service flow information according to the first path identifier and / or the second path identifier, including: The communication device determines that a service flow corresponding to the service flow information is transmitted on the first path according to the first path identifier; and / or determines that a service flow corresponding to the service flow information is transmitted on the second path according to the second path identifier.

25. The method according to any one of claims 21-24, characterized in that, The method further includes: The communication device stores the first path identifier and the first path information, as well as the second path identifier and the second path information; where the first path information is used by the communication device to determine the first path, and the second path information is used by the communication device to determine the second path.

26. The method according to claim 25, wherein The first path information is one or more of the following information: an access technology type corresponding to the first path, a registration type of the first path, a protocol stack used by the first path, a port corresponding to the first path, an interface corresponding to the first path, a link corresponding to the first path, or an identifier of the first radio access network device; The second path information is one or more of the following information: an access technology type corresponding to the second path, a registration type of the second path, a protocol stack used by the second path, a port corresponding to the second path, an interface corresponding to the second path, a link corresponding to the second path, or an identifier of the second radio access network device.

27. The method according to any one of claims 1-26, characterized in that, The access type of the at least two paths with the same access type is a 3rd Generation Partnership Project (3GPP) access type or a non-3GPP access type.

28. A first network element, characterized in that The first network element includes a module for performing the communication method according to any one of claims 1-20 or 27.

29. A communication device, characterized in that, The communication device includes a module for performing the communication method according to any one of claims 21-27.

30. A computer-readable storage medium, characterized in that, Including: A computer program or instruction is stored on the computer-readable storage medium. When the computer program or instruction runs on a computer, the computer is caused to execute the method according to any one of claims 1 to 27.

Images