Communication method and communication device

Abstract

The invention provides a communication method and a communication device, which are used for solving the problem that the transmission efficiency is reduced when user equipment (UE) accesses a network through at least two paths with the same access type. The method comprises: a first network element receives capability information from a first path, the capability information indicating that UE supports multiple connections, and 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 UE through the first path, so that the UE can determine the first path in the at least two paths through the first path identifier.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communications, and more particularly, to a communication method and a communication device. Background Art

[0002] A user equipment (UE) and a user plane function (UPF) network element can transmit service flow data to be sent by establishing a multi-access session, simultaneously through a 3rd Generation Partnership Project (3GPP) access network and / or a non-3GPP access network, so as to improve the transmission efficiency.

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

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

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

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

[0007] To achieve the above object, the present application adopts the following technical solutions:

[0008] In a first aspect, a communication method is provided. This method can be executed by a first network element, or can also be executed by a chip or a circuit of the first network element. The present application does not limit this. For the sake of description, the following takes the execution by the first network element as an example for illustration.

[0009] The method includes: a first network element obtaining capability information, the capability information indicating that the communication device supports multi-connection, the multi-connection including at least two paths with the same access type, and the at least two paths including a first path connecting the communication device and a first radio access network device; the first network element allocating a first path identifier corresponding to the first path according to the capability information; and the first network element sending the first path identifier to the communication device through the first path, the first path identifier being used for the communication device to determine the first path among the at least two paths.

[0010] In the communication method provided in the first aspect, the first network element obtains the capability information that the communication device supports multi-connection, enabling the first network element to allocate a first path identifier, and then sending the first path identifier to the communication device through the first path, so that the communication device can determine the first path among the at least two paths through the first path identifier. Furthermore, the communication device and the network can distinguish two paths with the same access type through different path identifiers, and negotiate the paths corresponding to the path identifiers with the network and the communication device to transmit data, thereby improving the transmission efficiency.

[0011] In a possible implementation, the first network element receives the capability information from the first path. For example, the first network element receives the capability information sent by the communication device. Alternatively, the first network element obtains the capability information from the subscription data of the communication device. For example, the first network element receives the subscription data from a data management network element, and the subscription data includes the capability information of the communication device. Or when the first network element is a data management network element, it directly obtains the capability information of the communication device from the subscription data.

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

[0013] In a possible implementation, 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.

[0014] In a possible implementation, the first network element is an access and mobility management network element. 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. The traffic splitting rule is used for the communication device to determine the transmission path of the service flow, and the transmission path is one or more paths among the at least two paths. By the access and mobility management network element sending the first path identifier to the session management network element, the session management network element generates a traffic splitting rule including the first path identifier. Furthermore, the communication device can transmit the service data through the path corresponding to the path identifier according to the traffic splitting rule corresponding to the service data, thereby improving the transmission efficiency.

[0015] In a possible implementation, the access and mobility management function (AMF) selects a session management function (SMF) that supports multi-connection based on the capability information; wherein, the SMF that supports multi-connection is an SMF that supports generating a traffic splitting rule including a first path identifier. The SMF that supports multi-connection can be understood as that this SMF can identify new parameters, such as path identifiers, and support generating a traffic splitting rule including path identifiers.

[0016] In a possible implementation, the first network element is an access and mobility management function (AMF), and the AMF obtains information for differentiating paths, and the information for differentiating paths is different in at least two paths.

[0017] In a possible implementation, the AMF obtains information for differentiating paths, including: the AMF receives information for differentiating paths from a first radio access network device; or, the AMF determines information for differentiating paths according to the first radio access network device.

[0018] In a possible implementation, the AMF stores the first path identifier and the information for differentiating paths. Or the AMF stores the association relationship between the first path identifier and the information for differentiating paths. Thus, the corresponding information for differentiating paths can be determined according to the first path identifier, and then data can be sent to the corresponding path according to the information for differentiating paths.

[0019] In a possible implementation, the AMF selects a data management function (DMF) that supports multi-connection based on the capability information; wherein, the DMF that supports multi-connection is a DMF that supports storing multiple contexts of a communication device.

[0020] In a possible implementation, the information for differentiating paths is one or more of the following information: 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 where the communication device accesses the network; the access technology type indicates the access technology type by which the communication device accesses the network through the first path; the registration type indicates the registration type by which the communication device registers to the network through the first path. The information of the access node is, for example, a radio access network device identifier or a cell identifier.

[0021] In a possible implementation, the first network element is a data management network element. Before the data management 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 the subscription data of the communication device; when the subscription data of the communication device is authorized to access the network through multi-connection, allocate a first path identifier. By first querying the subscription data of the communication device by the data management network element, it is confirmed whether the communication device is authorized to access the network through multi-connection, thereby avoiding allocating a path identifier to a communication device that is not allowed to access the network through multi-connection.

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

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

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

[0025] In a possible implementation, 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 the access and mobility management network element, and the information for differentiating paths is different among at least two paths.

[0026] In a possible implementation, the session management network element stores the first path identifier and the information for differentiating paths.

[0027] In a possible implementation, the session management network element sends the first path identifier and the information for differentiating paths to the access and mobility management network element.

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

[0029] In a possible implementation, the traffic splitting rule includes the priority of the first path, and the information for differentiating paths is used to determine the priority of the first path.

[0030] In a possible implementation, the session management network element selects a user plane network element that supports multi-connection according to the capability information; wherein, the user plane network element that supports multi-connection is a user plane network element that supports data splitting according to the traffic splitting rule including the first path identifier.

[0031] In a possible implementation, the information for differentiating paths is one or more of the following information: location information, access technology type, registration type, identifier of the first radio access network device, identifier of the access and mobility management network element; where the location information indicates the information of the access node to which the communication device accesses the network; the access technology type indicates the access technology type by which the communication device accesses the network through the first path; the registration type indicates the registration type by which the communication device registers to the network through the first path.

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

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

[0034] In a possible implementation, the policy control network element stores the first path identifier and the information for differentiating paths.

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

[0036] In a possible implementation, the access types corresponding to at least two paths with the same access type are the 3rd Generation Partnership Project (3GPP) access type or a non-3GPP access type.

[0037] In a second aspect, a communication method is provided. This method can be executed by a communication device, or can also be executed by a chip or a circuit of the communication device. This application does not make any limitation in this regard. For the sake of convenience of description, the following takes the execution by the communication device as an example for illustration.

[0038] The method includes: the 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, the traffic splitting rule includes traffic flow information, and the first path identifier and / or the second path identifier; the communication device determines the transmission path of the traffic flow corresponding to the traffic flow information according to the first path identifier and / or the second path identifier.

[0039] In the communication method provided in the second aspect, the communication device receives a first path identifier through a first path and a second path identifier through a second path. Then, the communication device transmits the service flow data through the path corresponding to the path identifier according to the traffic splitting rule corresponding to the service flow and the first path identifier and / or the second path identifier in the traffic splitting rule, thereby improving the transmission efficiency.

[0040] In a possible implementation, before the communication device receives the first path identifier and the second path identifier, the communication device sends capability information indicating that the 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 the first path and the second path. By sending the capability information indicating support for multi-connection, the network respectively assigns different path identifiers to the communication device according to different paths through which the communication device accesses the network. For example, the network assigns a first path identifier to the first path and a second path identifier to the second path.

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

[0042] In a possible implementation, the traffic splitting rule includes 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 according to the first path identifier and / or the second path identifier, the method further includes: the communication device determines the path identifier of the transmission path of the service flow according to the priority of the first path and / or the priority of the second path.

[0043] In a possible implementation, the communication device determines the transmission path of the 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 the service flow corresponding to the service flow information is transmitted on the first path according to the first path identifier; and / or determines that the service flow corresponding to the service flow information is transmitted on the second path according to the second path identifier.

[0044] In a possible implementation, 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; 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.

[0045] In a 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 radio 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 radio access network device.

[0046] In a possible implementation, the access types corresponding to at least two paths with the same access type are the 3rd Generation Partnership Project (3GPP) access type or a non-3GPP access type.

[0047] In a third aspect, a communication device is provided, which includes: a module for executing any communication method executed by the first network element described in the above description, such as a transceiver module and a processing module. Among them, the transceiver module is used to perform corresponding message sending and receiving actions, and the processing module can be used to perform all actions except sending and receiving information.

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

[0049] In a fourth aspect, a communication device is provided, which includes: a module for executing any communication method executed by the communication device described in the above description, such as a transceiver module and a processing module. Among them, the transceiver module is used to perform corresponding message sending and receiving actions, and the processing module can be used to perform all actions except sending and receiving information.

[0050] Optionally, the communication device described in the fourth aspect may further include a storage module, and the storage module stores programs or instructions. When the processing module executes the programs or instructions, the communication device can execute any communication method executed by the communication device described in the above description.

[0051] In a fifth aspect, a communication system is provided, including: a first network element, and the first network element is used to execute the methods in the first aspect and any of its possible implementation manners described above.

[0052] Optionally, the communication system further includes a communication device, and the communication device is used to execute the methods in the second aspect and any of its possible implementation manners described above.

[0053] In a sixth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program or code, and when the computer program or code runs on a computer, the computer is caused to execute the method in any one of the first aspect to the second aspect and any of its possible implementation manners described above.

[0054] In a seventh aspect, a chip is provided, including at least one processor. The at least one processor is coupled to a memory, the memory is used to store a computer program, and the processor is 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 first aspect to the second aspect and any of its possible implementation manners described above.

[0055] Wherein, 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.

[0056] In an eighth aspect, a computer program product is provided. The computer program product includes: computer program code, and when the computer program code runs on the computer, the method in any one of the first aspect to the second aspect and any of its possible implementation manners described above is executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 FIG. is a schematic diagram of a communication system provided by an embodiment of the present application.

[0058] Figure 2 FIG. is a schematic diagram of a registration process under a 3GPP access technology provided by an embodiment of the present application.

[0059] Figure 3 FIG. is a schematic diagram of a multi-access session establishment process provided by an embodiment of the present application.

[0060] Figure 4 FIG. is a possible form for a UE to access a network and / or establish a multi-access session provided by an embodiment of the present application.

[0061] Figure 5 FIG. is another possible form for a UE to access a network and / or establish a multi-access session provided by an embodiment of the present application.

[0062] Figure 6 FIG. is a schematic diagram of the process of communication method 600 provided by an embodiment of the present application.

[0063] Figure 7 FIG. is a schematic diagram of the process of communication method 700 provided by an embodiment of the present application.

[0064] Figure 8 FIG. is a schematic diagram of the process of communication method 800 provided by an embodiment of the present application.

[0065] Figure 9 It is a schematic flowchart of the communication method 900 provided by an embodiment of the present application.

[0066] Figure 10 It is a schematic flowchart of the communication method 1000 provided by an embodiment of the present application.

[0067] Figure 11 It is a schematic flowchart of the communication method 1100 provided by an embodiment of the present application.

[0068] Figure 12 It is a schematic flowchart of the communication method 1200 provided by an embodiment of the present application.

[0069] Figure 13 It is a schematic flowchart of the communication method 1300 provided by an embodiment of the present application.

[0070] Figure 14 It is a schematic flowchart of the communication method 1400 provided by an embodiment of the present application.

[0071] Figure 15 It is a schematic flowchart of the communication method 1500 provided by an embodiment of the present application.

[0072] Figure 16 It is a schematic flowchart of the communication method 1600 provided by an embodiment of the present application.

[0073] Figure 17 It is a schematic structural diagram of the communication device 1000 provided by an embodiment of the present application.

[0074] Figure 18 It is a schematic structural diagram of the communication device 2000 provided by an embodiment of the present application.

[0075] Figure 19 It is a schematic structural diagram of the chip system 3000 provided by an embodiment of the present application. Detailed implementation manners

[0076] Next, the technical solutions in the present application will be described in conjunction with the accompanying drawings.

[0077] The technical solutions provided by 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 by 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.

[0078] In a communication system, the part operated by an operator can be called a Public Land Mobile Network (PLMN), or it can also be called an operator network, etc. A PLMN is a network established and operated by a government or an operator approved by it for the purpose of providing public land mobile communication services, mainly a public network where a Mobile Network Operator (MNO) provides mobile broadband access services for users. In the embodiments of this application, the PLMN described specifically can be a network that meets the requirements of the 3rd Generation Partnership Project (3GPP) standard, abbreviated as a 3GPP network. A 3GPP network generally includes but is not limited to 5th-generation (5G) mobile communication networks, 4th-generation (4G) mobile communication networks, and other future communication systems, such as 6th-generation (6G) mobile communication networks, etc.

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

[0080] Figure 1 is a schematic diagram of a network architecture. Taking the 5G network architecture based on the service-based architecture (SBA) in the non-roaming scenario defined in the 3GPP standardization process as an example. As Figure 1As shown in the figure, the network architecture may include a terminal device part, a data network (DN) part, and a public land mobile network (PLMN) part of the operator network. Among them, the PLMN part of the operator network may include, but is not limited to, a (radio) access network ((R)AN) 120 and a core network (CN) part.

[0081] The functions of the network elements of each part are briefly described below.

[0082] The terminal device part may include UE 110, which is a device that provides voice and / or data connectivity to users. This UE 110 may also be referred to as a user equipment UE. The UE 110 in this application is a device with wireless transceiver functions and can communicate with one or more CN devices via an access network device (or also referred to as an access device) in the (radio) access network (R) AN 120. UE 110 may also be referred to as an access terminal, terminal, user unit, user station, mobile station, mobile device, remote station, remote terminal, mobile device, user terminal, user agent, or user device, etc. UE 110 can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as a ship, etc.); it can also be deployed in the air (such as an airplane, balloon, satellite, etc.). UE 110 can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, smart phone, mobile phone, wireless local loop (WLL) station, personal digital assistant (PDA), etc. Or, UE 110 can also be a handheld device with wireless communication functions, a computing device, or other devices connected to a wireless modem, vehicle-mounted device, wearable device, drone device, or a terminal in the Internet of Things, vehicle-to-everything network, any form of terminal in a 5G network and future networks, a relay user equipment, or a terminal in a future evolved 6G network, etc. Among them, the relay user equipment can be, for example, a 5G residential gateway (RG). For example, UE 110 can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in remote healthcare, 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 subscribed 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, this terminal device can be called a Dual Steer device. In a possible implementation, the terminal device can access the network through different subscribed data to perform registration to establish multiple connections or paths. The embodiments of this application do not limit the type or category of the terminal device, etc. For ease of description, the following of this application uses UE to represent the terminal device as an example for illustration.

[0083] (R)AN 120 may include one or more access network elements or access network devices. The interface between the access network device and the terminal device may be the Uu interface (or also referred to as the 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 does not limit this. (R)AN 120 is a device that provides wireless communication functions for the terminal device 110, and can be a node or device that connects the terminal device to the wireless network, and can also be called a network device. (R)AN 120 can be regarded as a sub-network of the operator network and is an implementation system between the service node in the operator network and the terminal device 110. For example, the terminal device 110 can be connected to the service node of the operator network through (R)AN 120 to obtain 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 device, the mobile switching center, or the network device in the future network, etc.The access network device may also be a module or unit that completes the base station function, for example, including a central unit (CU) and a distributed unit (DU); in a possible network structure, the CU can be used to support communication under protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); the DU can be used to support communication under the radio link control (RLC) layer protocol, medium access control (MAC) layer protocol, and physical layer protocol. The specific technologies and device forms adopted by the access network device in the embodiments of the present application are not limited. In systems using different radio access technologies, the names of the devices with the functions of the access network device may be different. For the convenience of description, in all embodiments of the present application, the device that provides wireless communication functions for the terminal device 110 is collectively referred to as an access network device or simply RAN for short. It should be understood that the specific types of the access network device are not limited herein.

[0084] The CN part may include, but is not limited to, the following network functions (NFs): 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, session management function (SMF) 136.

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

[0086] The NF functions included in the CN are further briefly described below.

[0087] 1. The UPF 130 is a gateway provided by the operator and serves as the gateway for communication between the operator's network and the DN 140. The network functions of the UPF 130 include functions related to the user plane such as packet routing and transmission, packet detection, service usage reporting, quality of service (QoS) handling, lawful interception, uplink packet detection, and downlink packet preservation. In future communication systems, the user plane function network element can still be a UPF network element, or it can also have other names, which are not limited in this application.

[0088] 2. The PCF 131 is a control plane function provided by the operator, mainly supporting the provision of a unified policy framework to control network behavior, providing policy rules to control layer network functions, and at the same time being responsible for obtaining user subscription information related to policy decisions. Exemplarily, the PCF 131 can be divided into two PCFs with different functions. For example, the PCF is divided into UE-PCF and AMF-PCF. Among them, the UE-PCF can be used to generate the UE policy, that is, the policy sent to the UE 110, and the sending path is: UE-PCF--->AMF--->UE. At this time, the AMF does not parse the content of the UE policy, that is, the AMF transparently transmits the UE policy. The AM-PCF can be used to generate the AM policy, that is, the policy for access management sent to the AMF, and the sending path is: AMF-PCF--->AMF. Further, the AMF can also send some or all of the access management policies to the RAN 120. In another example, the PCF 131 can be divided into AM-PCF and SM-PCF, and the AM-PCF and SM-PCF can be located on the same PCF or different PCFs. Among them, the AM-PCF is mainly responsible for access mobility policy control. For example, it can generate a UE route selection policy (URSP). The SM-PCF is mainly responsible for session management policy control. For example, it can generate a 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 also have other names, which are not limited in this application.

[0089] 3. The UDM 132 is a control plane function provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI) of the subscribed users in the operator's network, the generic public subscription identifier (GPSI) of the subscribed users for public use, and the credential. Among them, the SUPI will be encrypted first during the transmission process, and the encrypted SUPI is called the subscription concealed identifier (SUCI). The information stored by the UDM network function 132 can be used for the authentication and authorization of the UE 110 to access the operator's network. Among them, the subscribed users of the above operator's network can specifically be the users who use the services provided by the operator's network, such as the users using the SIM cards of China Telecom, or the users using the SIM cards of China Mobile, etc. The credential of the above subscribed users can be the long-term key stored in the mobile phone chip card or the small file stored with the information related to the encryption of the mobile phone chip card, etc., for authentication and / or authorization. In the future communication system, the unified data management functional network element can still be the UDM network element, or there can be other names, which are not limited in this application. 4. The UDR 133 is a control plane function provided by the operator, providing the functions of storing and obtaining subscribed data for the UDM, storing and obtaining policy data for the PCF, storing and obtaining the NF group ID (group ID) information of the users, etc. In the future communication system, the unified data repository functional network element can still be the UDR network element, or there can be other names, which are not limited in this application.

[0090] 5. The AUSF 134 is a control plane function provided by the operator, usually used for primary authentication, that is, the authentication between the UE 110 (subscribed user) and the operator's network. After receiving the authentication request initiated by the subscribed user, the AUSF network function 134 can authenticate and / or authorize the subscribed user through the authentication information and / or authorization information stored in the UDM network function 134, or generate the authentication and / or authorization information of the subscribed user through the UDM network function 134. The AUSF network function 134 can feedback the authentication information and / or authorization information to the subscribed user. In the future communication system, the authentication server functional network element can still be the AUSF network element, or there can be other names, which are not limited in this application.

[0091] 6. The AMF 135 is a control plane network function provided by the operator network, responsible for access control and mobility management of the UE 110 accessing the operator network, such as functions including mobile status management, allocation of user temporary identity, authentication and authorization of users, etc. In future communication systems, the access management network element can still be the AMF network element, or, there can also be other names, which are not limited in this application.

[0092] 7. The SMF 136 is a control plane network function provided by the operator network, responsible for managing the protocol data unit (PDU) sessions of the UE 110 (including establishment, modification, and release of sessions), for selection and reselection of user plane function network elements, allocation of internet protocol (IP) addresses of terminal devices, quality of service (QoS) control, etc. Among them, a PDU session is a channel for transmitting PDUs, and the terminal device transmits PDUs to and from the DN 140 through the PDU session. The PDU session is responsible for establishment, maintenance, deletion, etc. by the SMF network function 136. The SMF network function 136 includes session management (such as session establishment, modification, and release, including tunnel maintenance between the user plane function UPF 130 and the (R)AN 120), selection and control of the UPF network function 130, service and session continuity (SSC) mode selection, roaming, and other session-related functions. In future communication systems, the session management function network element can still be the SMF network element, or, there can also be other names, which are not limited in this application.

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

[0094] Figure 1 Among them, Npcf, Nudm, Nudr, Nausf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. Exemplarily, the meanings of the above interface sequence numbers can be referred to the meanings defined in the 3GPP standard protocol, and this application does not limit the meanings of the above interface sequence numbers. It should be noted that Figure 1 The interface names between the various network functions herein are only examples. In specific implementations, the interface names of this system architecture may also be other names, which are not limited in this application. In addition, the names of the messages (or signaling) transmitted between the above network elements are also only examples and do not impose any limitations on the functions of the messages themselves.

[0095] It should be noted that in the Figure 1 architecture shown, 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 through the Xn interface, and gNBs are connected to the 5GC through the NG interface. Among them, the NG interface includes the NG-C interface and the NG-U interface. The NG-C interface is a control plane interface, connecting the gNB and the AMF, and transmitting control plane data; the NG-U interface is a user plane interface, connecting the gNB and the UPF, and transmitting 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.

[0096] It should be understood that the above network architecture 100 is only described from the perspective of the service-based architecture. In this service-based architecture, the PLMN can, according to specific scenario requirements, orderly combine some or all network functions as needed to achieve the customization of network capabilities and services, so as to deploy dedicated networks for different services, that is, to implement 5G network slicing. The network slicing technology enables operators to respond to customer needs more flexibly and quickly, and supports the flexible allocation of network resources.

[0097] For ease of description, in the embodiments of the present application, network functions (such as UPF 130…SMF136) are collectively / abbreviated as NF, that is, the NF described later in the embodiments of the present application can be replaced by any network function. In addition, in the embodiments of the present application, the UE 110 is referred to as the UE, that is, the UE described later in the embodiments of the present application can be replaced by a terminal device. Figure 1 Only some network functions are schematically described, and the NF described later is not limited to Figure 1 the network functions shown in

[0098] It should be understood that Figure 1 the AMF, SMF, UPF, AUSF, PCF, UDM, and UDR shown in

[0099] can be understood as network elements in the core network for implementing different functions. For example, they can be combined into network slices as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. The present application does not limit the specific form of the above network elements.

[0099] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to the present application. The present application does not exclude the possibility of using other names in 5G networks and future other networks. For example, in 6G networks, some or all of the above network elements may continue to use the terms in 5G, or other names may also be used.

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

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

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

[0103] The 3GPP access type includes, but is not limited to, the following access technologies: LTE access technology (corresponding to 4G cellular network), NR access technology (corresponding to 5G cellular network), satellite access technology defined by 3GPP, or subsequent evolved cellular access technology; among them, the satellite access technology defined by 3GPP can also be further divided into low-earth orbit satellites, medium-earth orbit satellites, and geostationary satellites. The 3GPP access network refers to an access network whose access type is 3GPP access type (the access type can also be referred to as an access mode).

[0104] The non-3GPP access type includes, but is not limited to, the following access technologies: untrusted non-3GPP access technology (such as accessing the core network through a wireless access node purchased personally), trusted non-3GPP access technology (such as accessing the core network through a wireless access node deployed by an operator), wireline access technology (such as Broadband Forum (BBF) access technology, Cable access technology, etc.), IEEE802.11 access technology, non-3GPP access technology connected through a standalone non-public network (SNPN). For example, the access modes adopting non-3GPP access technology can include wireline, Wireless Fidelity (WiFi), Bluetooth, ZigBee, etc. The non-3GPP access network refers to an access network whose access type is non-3GPP access type.

[0105] 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, registration process under wireline access technology.

[0106] As Figure 2 introduces a possible registration process of a UE under the 3GPP access type in the current technology.

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

[0108] Among them, the AN message includes AN parameters and a Registration Request message. The AN parameters contain parameter information for the RAN to select the AMF, and the parameter information may include one or more of the following: globally unique AMF identifier (GUAMI), public land mobile network (PLMN) identifier, network identification (NID), etc. The registration request message includes a registration type, 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.

[0109] Step 202: The RAN selects an AMF according to the AN parameters.

[0110] The AN parameters are the AN parameters in the AN message in Step 201.

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

[0112] Step 204: The UE, AMF, AUSF, UDM, etc. interact to perform an authentication and security procedure.

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

[0114] Then, the AMF indicates to the UE that the authentication is successful. For example, the AMF sends a NAS Security Mode Command to the UE to activate NAS security. This 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 is 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.

[0115] Step 205: The AMF interacts with the UDM to obtain the subscribed data of the UE.

[0116] The AMF can obtain relevant service information based on the subscribed data of the UE, such as at least one of the service level of the UE, service traffic limit, service fee, etc. These information can be used to control the service access and restrictions of the UE, as well as for charging and settlement, etc.

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

[0118] The NAS Registration Accept message can be included in the N2 message.

[0119] Step 207: The RAN forwards the NAS Registration Accept message sent by the AMF to the UE.

[0120] In a possible implementation, taking the dual-connection scenario as an example, both paths by which the UE connects to the network are of the 3GPP access type. The UE can perform 3GPP access type registration twice on the two paths respectively, so as to establish the connection of the two 3GPP access type paths.

[0121] 3) Determination process of access type and access technology type.

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

[0123] The access network device can 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. The W-AGF can also be referred to as the AGF.

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

[0125] In one example, the AMF determines the access type of the UE registration 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 a RAN), the AMF can determine that the access type of the UE registration 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 being sent by an N3IWF, a TNGF, a TWIF, a W-AGF, etc., the AMF can determine that the access type adopted by the UE is a non-3GPP access type.

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

[0127] In a multi-connection scenario, after the UE has registered multiple times, the access types registered by the UE can be one or more. For example, in a dual-connection scenario, the UE can register twice through the 3GPP access type. In this case, the access type registered by the UE is the 3GPP access type. For another example, the UE registers for the first time through the 3GPP access type and the second time through the non-3GPP access type. In this case, the access types registered by the UE are the 3GPP access type and the non-3GPP access type.

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

[0129] In a single access PDU session, the UE accesses the network only through the user plane channel of 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); the UPF can send downlink data to the UE through the RAN. Currently, the user plane channels of multi-access PDU sessions can include two access network devices (3GPP access network devices and non-3GPP access network devices), 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); the UPF sends downlink data to the UE through the RAN and / or the N3IWF.

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

[0131] 5) MA PDU Session Establishment Process:

[0132] As Figure 3 shown, 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.

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

[0134] The PUD session establishment request is an NAS message, including one or more of the following: request type, PDU Session ID, UE Requested DNN, slice information (S-NSSAI), etc. Among them, the request type is the multi-access session request (MA PDU Request), indicating that this session establishment request message is used to request the establishment of a multi-access PDU session.

[0135] Step 302: The AMF sends a PDU session create session context request (Nsmf_PDU Session_GreateSMContext Request) message to the SMF.

[0136] The PDU session create session context request includes one or more of the following: UE identifier (such as SUPI), UE Requested DNN, PDU Session ID, request type is 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 3GPP access type and non-3GPP access type. The radio access technology type can include radio access technology or can also include wired access technology. The access technologies corresponding to 3GPP access type and non-3GPP access type have been introduced above.

[0137] Step 303 (optional): The SMF interacts with the UDM to obtain session management subscription data, which can include information allowing the establishment of a multi-access PDU session or information not allowing the establishment of a multi-access PDU session. For example, the SMF can obtain the session management subscription data by means of subscription retrieval / subscription for updates.

[0138] Step 304: The SMF sends a PDU session create session context response (Nsmf_PDU Session_GreateSMContext Response) message to the AMF.

[0139] The PDU session create 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. For example, Unknown PDU Session Type means that the requested PDU session type is unknown or not supported.

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

[0141] Step 306: The SMF sends a Policy Association Establishment Request message to the PCF.

[0142] The Policy Association Establishment Request message includes one or more of the following: UE identifier (SUPI), DNN requested by the UE, PDU session identifier, request type as a multi-access session request, etc.

[0143] For example, if dynamic policy control and charging (PCC) rules are required, the SMF selects the PCF and sends the Policy Association Establishment Request message to the PCF to establish a session policy association with the PCF.

[0144] Step 307: The PCF sends a Policy Association Establishment Response message to the SMF.

[0145] 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 values, etc. The steering functionality can be a multi-path transmission control protocol (MPTCP) function, and the threshold values can be round trip time (RTT) threshold values and / or packet loss rate threshold values.

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

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

[0148] Among them, the UPF is the UPF selected by the SMF in Step 308.

[0149] The N4 session establishment request includes N4 rules, and the N4 rules include one or more of the following rules: Packet Detection Rule (PDR): contains information for classifying the data packets arriving at the UPF; Forwarding Action Rule (FAR): contains information on whether to forward, discard, or cache the traffic flow identified by the PDR; Multi-Access Rule (MAR): contains information on how to handle splitting, handover, or splitting in the MA PDU session; Usage Reporting Rule (URR): contains information for defining how to count the traffic flow identified by the PDR and how to report the measurement; QoS Enforcement Rule (QER), contains information related to performing QoS for the traffic flow identified by the PDR; Session Reporting Rule (SRR), contains information on the events for requesting the user plane function to detect and report, and the events are not related to a specific PDR in the PDU session nor related to usage measurement. Among them, the MAR rule includes one or more of the following: splitting mode, splitting function, and other information.

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

[0151] The N4 session establishment response includes tunnel information, such as CN tunnels info.

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

[0153] Step 310: The SMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF.

[0154] The Namf_Communication_N1N2MessageTransfer 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.

[0155] 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), core network side tunnel information (CN Tunnel Info) (one of the CN Tunnel Infos from step 309b), etc. The SMF sends the core network side tunnel information to the RAN through the AMF for the RAN to determine the destination address of the uplink data.

[0156] The N1 interface session management container includes, but is not limited to, one or more of the following: PDU session establishment accept (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, handover, access traffic steering switchingsplitting (ATSSS) rules, etc. information related to the session. Among them, the ATSSS rules include, but are not limited to, one or more of the following: splitting mode, splitting function, threshold value and other information. Subsequently, the information in the N1 interface session management container is sent by the SMF to the UE through the AMF. For example, the AMF sends it to the UE through NAS messages.

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

[0158] The AMF device can also send a response to the SMF device indicating that it has received the information from the SMF device.

[0159] Step 311: The AMF sends an N2 PDU session request message to the RAN.

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

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

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

[0163] The RAN sends this NAS message to the UE. The NAS message includes one or more of the following, including but not limited to: PDU Session ID, PDU Session Establishment Accept message, ATSSS rule. The ATSSS rule includes information such as, for example, traffic splitting mode, traffic splitting function, threshold value, etc.

[0164] Step 313: The RAN sends an N2 PDU session response message to the AMF.

[0165] The N2 PDU session response message includes the access network tunnel information (AN tunnels info) on the RAN side. This access network side tunnel information on the RAN 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 3GPP transmission path). The AN tunnels info on the RAN side will subsequently pass through the AMF and the SMF to the UPF. Steps 313, 314, and 315 can be referred to.

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

[0167] The PDU session update session context request message includes the access network tunnel information (AN tunnels info) on the RAN side (from Step 313).

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

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

[0170] The PDU session update session context response message includes an indication of success or failure of the update. If it fails, the SMF can also send a failure cause value to the AMF.

[0171] Step 317: The SMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF.

[0172] The Namf_Communication_N1N2MessageTransfer message includes one or more of the following: N2 Session Management information (N2 SMinformation), N1 Session Management Container (N1 SM Container), access type and other information.

[0173] The N2 Session Management information includes, but is not limited to, one or more of the following: PDU Session ID (from the UE reported in Step 301), Core Network side Tunnel Endpoint Information (CN Tunnel Info). The SMF sends the core network side tunnel information to the N3IWF through the AMF for the N3IWF to determine the destination address of the uplink data.

[0174] The AMF may also send a response to the SMF to indicate that it has received the information from the SMF.

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

[0176] 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 according to the access type indicated by the SMF. For example, when the access type in Step 317 is a non-3GPP access type, this information is sent to a non-3GPP access gateway device (such as the N3IWF).

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

[0178] In this process, the N3IWF assigns an IP address (such as UP_IP_ADDRESS) for this IPSec Child SA to the UE. That is, when the UE sends uplink data, the destination IP address should be set to this UP_IP_ADDRESS, and the source IP address is the assigned internal IP address, which is used to identify the UE's identity in the network. The number of IPSec Child SAs established between the UE and the N3IWF, and which Quality of Service Flow (QoS Flow) data each IPSec Child SA transmits are determined based on the N3IWF's policies and configurations.

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

[0180] The N2 PDU session response message includes access network tunnel information (AN tunnels info) on the N3IWF side, which 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 via the AMF and the SMF. Refer to Step 320, Step 321, and Step 322.

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

[0182] The PDU session update session context request includes the access network tunnel information on the N3IWF side (from Step 320).

[0183] Step 322: The SMF sends the AN tunnel information on the N3IWF side to the UPF through the N4 session modification process.

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

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

[0186] The response message includes an indication of success or failure of the update. If it fails, the SMF can also send a failure cause value to the AMF.

[0187] Figure 3 It is introduced that the session establishment process is first executed on the 3GPP access side (for example, refer to Steps 310 to 316 in Figure 3 ), and then the session establishment process is executed on the non-3GPP access side (for example, refer to Steps 317 to 323 in Figure 3 ). In another example, the session establishment process can also be first executed on the non-3GPP access side and then on the 3GPP access side. This process is similar to the above schematic diagram and will not be elaborated in detail.

[0188] Figure 3The example describes that the UE sends a session establishment request message once. In another example, the UE may send session establishment request messages on the 3GPP side and the non-3GPP side respectively. For example, between step 316 and step 317, a process similar to steps 301 and 302 may be further executed, which will not be elaborated here.

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

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

[0191] The split mode includes but is not limited to: Active Standby mode, SmallestDelay mode, Load-Balancing mode, Priority-based mode. The mechanism of each split mode will be elaborated below:

[0192] Active Standby: When there are 2 transmission paths, one of the transmission paths is specified as Active (3GPP access or Non-3GPP access), and the other transmission path is Standby. When the Active transmission path is available, all data of the service flow is transmitted to the peer through the Active transmission path. When the Active path is unavailable, all data of the service flow is switched to the Standby transmission path for transmission.

[0193] Smallest Delay: Select the transmission path with the shortest delay to transmit the data of the traffic flow. In this mode, the UE or UPF needs to monitor the transmission delay of the path in real time. The implementation can be completed 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) in the UPF.

[0194] Load-Balancing: The data of the traffic flow will be distributed proportionally to different transmission paths for transmission, and the distribution ratio is determined according to the load conditions of multiple (two or more) transmission paths in the network (for example, the path with a heavier load has a smaller distribution ratio, and the path with a lighter load has a larger distribution ratio).

[0195] Priority-based: Designate one of the transmission paths as the high-priority transmission path, and the other transmission paths as the second-high-priority (or medium-priority, low-priority, etc.) transmission paths. When there is no congestion on the high-priority transmission path, all the data of the traffic flow is transmitted through the high-priority transmission path. When congestion occurs on the high-priority transmission path, some of the data of the traffic flow will be transmitted through the second-high-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 the data of this traffic flow will be transmitted through the second-high-priority (or medium-priority, low-priority, etc.) transmission path, or any one or more of the remaining paths.

[0196] The traffic splitting function can be understood as which function is used for multi-path traffic splitting, such as the MPTCP function defined by 3GPP.

[0197] For the case where the traffic splitting mode is load-balancing, the traffic splitting mode indicator can be autonomous load-balance or UE-assistance. Autonomous load-balance means that the UE or UPF can independently determine the splitting ratio. UE-assistance means that the UE can independently determine the splitting ratio, and in addition, the splitting ratio can be sent to the UPF so that the UPF can send downlink data according to this splitting ratio.

[0198] Threshold values, including but not limited to RTT threshold values and / or packet loss rate threshold values, can be used in combination with load - balancing or priority - based traffic splitting modes to assist in making decisions on how to split traffic.

[0199] Billing information: In a mobile communication network, communication service providers need to bill users for their communication behaviors. The billing information in the MAPDU can record users' communication behaviors, such as call duration, number of text messages, data traffic, etc., for the communication service providers to perform billing. The communication service provider can bill for the path of service flow transmission.

[0200] Usage Monitoring information: Resources in a mobile communication network are limited, and communication service providers need to allocate and manage resources reasonably. The usage monitoring information in the MAPDU can record users' communication behaviors, such as data traffic, bandwidth usage, etc., for the communication service providers to perform resource management and optimization. It depends on which access type path the service flow is transmitted on.

[0201] In addition, the MAPDU session control information can also include Application descriptors, which are used to identify the service flow, so as to determine which traffic splitting function and traffic splitting mode should be adopted for this service flow.

[0202] 7) ATSSS Rules

[0203] The SMF generates ATSSS rules according to PCC rules and sends the ATSSS rules to the UE through the AMF. The ATSSS rules can include one or more of the following:

[0204] Rule identifier, which is used to uniquely identify the ATSSS rule.

[0205] Rule Precedence, which is used to determine the order of the ATSSS rules.

[0206] Traffic Descriptor, which is used to define traffic flows and may include one or more of the following information: Application descriptor, IP descriptor, Non-IP descriptor; among them, the Application descriptor includes one or more application identifiers for identifying the application that generates the traffic flow; the IP descriptor includes one or more five-tuples for identifying the destination of the IP traffic flow; the Non-IP descriptor includes one or more descriptors for identifying the destination of non-IP traffic flows such as Ethernet packets.

[0207] Access Selection Descriptor, which is used to define the part of access selection. It may include the following information: splitting mode, splitting mode indication, threshold value, splitting function. The above information can refer to the relevant descriptions in the PCC rules.

[0208] 8) System architecture of multi-access PDU session:

[0209] Currently, multi-access PDU session supports transmission through two paths, namely the 3GPP path and the non-3GPP path.

[0210] However, in the future, multi-access PDU session will support transmission through multiple paths with the access type of 3GPP and / or multiple paths with the access type of non-3GPP. In this case, it is no longer possible to accurately identify different paths only by the access type (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 only on the parameter of the access type (e.g., 3GPP access type).

[0211] Figure 4A possible form of the UE accessing the network and / or establishing a multi-access session is introduced: The UE accesses the PLMN through the 3GPP transmission path 1 (such as the 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 the 3GPP transmission path 2 (such as the 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 these two paths, then this 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).

[0212] Figure 5 Another possible form of the UE accessing the network and / or establishing a multi-access session is introduced: The UE accesses the core network through the 3GPP transmission path 1 (such as a satellite base station) via the gNB, and the UE accesses the core network through the 3GPP transmission path 2 (such as a terrestrial cellular network (gNB)). From the perspective of the core network, the UE accesses the PLMN through two 3GPP transmission paths. If the core network (such as the AMF) can distinguish between satellite access technology and terrestrial cellular access technology, then the AMF can distinguish the two paths by the access technology. However, from the perspective of current registration management, mobility management, and session management, both belong to the 3GPP access type.

[0213] According to the above possible new forms of the UE accessing the network and / or establishing a multi-access session, that is, each path of the UE accessing the network and / or establishing a multi-access session can be multiple belonging to the same access type (such as multiple 3GPP access types or multiple non-3GPP access types), or a multi-access session with a path number greater than two paths.

[0214] 9) Dual-connection scenario:

[0215] Take Figure 4 as an example to introduce the dual-connection scenario used in the embodiments of the present application. For example, the dual-connection can be called Dualsteer. 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 the RAN. For example, the UE can use a SIM card and simultaneously access the same PLMN through two different RANs. Exemplarily, the two connections of the 3GPP access type correspond to two paths. As Figure 4As shown, 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.

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

[0217] It should be noted that in this application, the names of dual connection or multiple connections can be further extended as follows:

[0218] 1: Dual / multiple radio capability, which indicates the UE's ability to support accessing the network through dual / multiple radio access.

[0219] 2: Dual / multiple 3GPP RAT, which indicates the UE's access to the network through dual / multiple 3GPP radio access technologies.

[0220] 3: Dual / multiple steer, which indicates the UE's access to the network through dual / multiple split paths.

[0221] 4: Dual / multiple 3GPP access, which indicates the UE's access to the network through dual / multiple 3GPP paths.

[0222] 5: Dual / multiple 3GPP access type, which indicates the UE's access to the network through dual / multiple 3GPP access types.

[0223] 6: Dual / multiple connectivity, which indicates the UE's access to the network through dual / multiple different paths.

[0224] 7: Dual / multiple registration, which indicates the UE's registration to the network through dual / multiple different paths.

[0225] 8: Same access type, which indicates the UE's access to the network through dual / multiple paths of the same access type.

[0226] 9: Same Radio Access Technology (RAT), where the same RAT indicates that the UE accesses the network through two / multiple paths of the same RAT.

[0227] 10: Same access network, where the same access network indicates that the UE accesses the same network through two / multiple paths.

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

[0229] 12: Dual / multiple air interface capability, where dual / multiple air interface capability indicates that the UE supports the ability to access the network through dual / multiple air interfaces.

[0230] In this embodiment, the case where the UE supports dual Radio Capability is taken as an example for introduction. It should be noted that the other names of the above extensions are also applicable. In other words, the names of the above extensions can be replaced with each other.

[0231] However, in this dual-connection scenario, when the UE accesses the network through two 3GPP access types, since the access network devices in both paths are access network devices of the 3GPP access type, the UE cannot distinguish on which path the data is transmitted through the same access type. As a result, the UE will randomly select at least one path out of the two paths to transmit data according to the 3GPP access type, leading to a reduction in transmission efficiency.

[0232] To solve the above problems, the present application proposes the following method, enabling the UE and the network to accurately identify different transmission paths with the same access type to achieve multi-connection management or multi-path management.

[0233] As Figure 6 shown, a method 600 applicable to the present application is introduced. This method is applicable to the case where the UE accesses the network through multiple paths of the same access type (for example, two paths of the 3GPP access type). In method 600, the AMF assigns a path identifier to the UE during the registration process and sends it to the UE. Through method 600, the UE can determine the transmission path according to the path identifier. This method includes the following steps:

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

[0235] In one possible implementation, the AN message includes capability information, which indicates the connection capabilities supported by the UE, such as supporting multi-connection or dual-connection. The dual-connection / multi-connection capability indicates that the UE can establish connections or transmit data with two / multiple RANs simultaneously. Alternatively, the dual-connection / multi-connection capability indicates that the UE has two / multiple user plane protocol stacks and can perform dual transmit and receive / multi-transmit and multi-receive of data simultaneously. The data transmitted and received simultaneously 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, converge it, and send the converged data to the data network (or server), such as Figure 1 send to the DN 140 in. In one possible implementation, the capability information indicates that the UE supports establishing connections or transmitting data with two / multiple RANs simultaneously. Alternatively, the capability information indicates that the UE supports two / multiple user plane protocol stacks and can perform dual transmit and receive / multi-transmit and multi-receive of data simultaneously. The name of this capability information is not limited in this application. It can be supporting dual-connection or supporting multi-connection, or an extension of the above names of dual-connection or multi-connection. In this embodiment, the UE capability information is taken as an example where the UE supports dual-connection for illustration.

[0236] In one possible implementation, the capability information is in a field that can be parsed by the AMF in the AN message, so that the AMF can obtain the capability information and allocate a path identifier according to the capability information. For example, the registration request message in the AN message includes the capability information. For another example, the capability information can coexist with AN parameters and the registration request message in the AN message.

[0237] Optionally, the capability information is in a field that can be parsed by the RAN in the AN message, so that the RAN can obtain the capability information and select the AMF according to the capability information. For example, the AN parameters in the AN message include the capability information. For another example, the capability information can coexist with AN parameters and the registration request message in the AN message.

[0238] In one possible implementation, when the UE determines that it has dual-connection capabilities, or the UE hopes to access the network through two different paths of the 3GPP access type simultaneously, the AN message sent in step 601 includes the capability information.

[0239] In one possible implementation, the UE determines that it can access the network through two paths according to the dual-connection information (such as the information of DualSteer), or determines that it hopes to access the network through two different paths simultaneously. Exemplarily, the dual-connection information can be obtained by the UE according to the service. For example, one path cannot meet the rate requirement of a certain service (such as a video service). Therefore, the UE can determine to use two paths to access the network according to this service, and thus execute step 601.

[0240] In a possible implementation, the UE may obtain dual-connection information (such as DualSteer information) based on a user's operation instruction. For example, the user may turn on the DualSteer switch on the UE. Further, the UE may enter the DualSteer state according to the user's operation instruction, and thus execute step 601.

[0241] In another possible implementation, the UE may obtain dual-connection support information (such as DualSteer information) based on pre-configured information. For example, the UE is pre-configured with DualSteer support information in the factory configuration, such as the UE supports accessing the network through two different paths simultaneously, and thus execute step 601.

[0242] This embodiment takes the UE selecting RAN1 as the first path to initiate the registration process and sending an AN message to RAN1 as an example for introduction. In another possible implementation, for the related description of the AN message, refer to Figure 2 step 201 in, that is, the AN message may not include the above-mentioned capability information.

[0243] Step 602: RAN1 selects an AMF.

[0244] In a possible implementation, the capability information is in a field that can be parsed by the RAN in the AN message. RAN1 selects an AMF that supports dual connection according to the capability information. In other words, it selects an AMF that supports managing a "UE that supports dual connection". It can be understood that this AMF can reserve two path connections for the same UE, or it can be understood that the AMF can maintain the connection with the UE through two paths simultaneously, or it can be understood that this AMF can identify new parameters, such as the UE's capability information. Among them, a "UE that supports dual connection" can be understood as a UE 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, this AMF can simultaneously maintain the connection status / context information of the UE corresponding to the two 3GPP paths, or it can be understood that this AMF supports dual registration, and the support for multi-registration in this embodiment also applies. It should be noted that the names for supporting dual registration or multi-registration can be further extended as follows:

[0245] 1: Support dual / multi-registration management, and support for dual / multi-registration management indicates that the AMF supports managing the UE's dual / multi-registration to the network.

[0246] 2: Support dual / multi-registration under the same access type, and support for dual / multi-registration under the same access type indicates that the AMF supports managing UEs that are registered to the network through dual / multiple paths of the same access type.

[0247] 3: Support dual / multi-registration under the same access technology. The support for dual / multi-registration under the same access technology indicates that the AMF supports managing UEs that are registered to the network through dual / multiple paths of the same access technology.

[0248] 4: Support dual / multi-connection management. The support for dual / multi-connection management indicates that the AMF supports managing UEs that are connected to the network through dual / multiple paths.

[0249] 5: Support dual / multi-connection under the same access type. The support for dual / multi-connection under the same access type indicates that the AMF supports managing UEs that are connected to the network through dual / multiple paths of the same access type.

[0250] 6: Support dual / multi-connection under the same access technology. The support for dual / multi-connection under the same access technology indicates that the AMF supports managing UEs that are connected to the network through dual / multiple paths of the same access technology.

[0251] In this embodiment, RAN1 selects AMF1 as an example for illustration.

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

[0253] The registration request message includes capability information, which is used by AMF1 to allocate path identifiers.

[0254] Optionally, RAN1 sends information for differentiating paths to AMF1. In one possible implementation, the information for differentiating 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), and the ULI includes a cell identifier, which is the identifier of the cell where the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, different paths can be identified through the ULI.

[0255] In one possible implementation, RAN1 sends a next generation application protocol (NGAP) message to AMF1, which can also be referred to as an N2 message. Among them, the N2 message includes a registration request message and information for differentiating paths. It can be understood that in this N2 message, the registration request message and the information for differentiating paths exist side by side.

[0256] In another possible implementation, RAN1 can send a registration request message and information for differentiating paths to AMF1 through two N2 messages respectively.

[0257] In another possible implementation, RAN1 may send a registration request message to AMF 1 via an N2 message, where the registration request message includes the UE's capability information and information for differentiating paths.

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

[0259] For relevant descriptions, refer to Figure 2 the relevant explanations in step 204 therein, which will not be elaborated here.

[0260] Step 605: AMF1 allocates a path identifier (such as a path identifier).

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

[0262] In one possible implementation, when the AMFs on different paths are different, to ensure that the path identifiers allocated by different AMFs for the same UE are different, the AMF may allocate path identifiers in the following two ways:

[0263] Method a: The path identifier includes the identifier of the AMF. Exemplarily, the identifier of this AMF is AMF1. If AMF1 allocates path identifier 1 for the first path, then the path identifier of the first path may include AMF1 and 1. The identifier of another AMF is AMF2. If AMF2 allocates path identifier 1 for the second path, then the path identifier of the second path may include AMF2 and 1. Thus, it is ensured that the path identifiers allocated by AMF1 and AMF2 are different.

[0264] Method b: Select a path identifier from an identifier set. The network allocates different identifier sets to different AMFs. Exemplarily, the set allocated by the network for AMF1 is 1 - 32. Then AMF1 selects the path identifier for the first path from the set 1 - 32, for example, selects path identifier 1. The set allocated by the network for AMF2 is 33 - 64. Then AMF2 selects the path identifier for the second path from the set 33 - 64, for example, selects path identifier 33. Thus, it is ensured that the path identifiers allocated by AMF1 and AMF2 are different.

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

[0266] In this embodiment, it is described by taking AMF1 allocating path identifier 1 for the first path as an example.

[0267] In a possible implementation, AMF1 obtains information for differentiating paths, such as location information, access type, access technology type, registration type, RAN identifier, etc. Among them, AMF1 can determine the access type, access technology type, and RAN identifier according to the access network device information, and AMF1 can obtain the location information and registration type according to the message sent by RAN1. 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 the registration type. It should be noted that the information for differentiating paths is the information for differentiating the first path or the information for identifying the first path.

[0268] In a possible implementation, AMF1 stores the path identifier in the UE context, or AMF1 stores the path identifier 1 and the information for differentiating the first path (such as one or more of location information, access type, access technology type, registration type, RAN identifier) in the UE context, or AMF1 stores the association relationship between the path identifier 1 and the information for differentiating the first path in the UE context. In this way, after AMF1 receives the downlink data subsequently, it can determine the first path according to the path identifier 1 and send the data to the UE through the first path.

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

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

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

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

[0273] In a possible implementation, AMF 1 can select a UDM that supports dual registration according to the capability information or the registration type. For example, the registration type is a newly added registration type, and this registration type is used to indicate that the UE registers two paths. Exemplarily, the name of the newly added registration type can be DualSteer Registration, and the name is not limited here. It can be understood that the UDM selected by AMF is a UDM that supports storing multiple contexts of the same UE.

[0274] Step 607: The UDM queries the subscribed data.

[0275] Optionally, the UDM may query the subscribed data of the UE according to the identifier of the UE. The subscribed data of the UE includes the UE's capability information, so as to determine whether the UE is allowed to access the network through dual connectivity. When the subscribed 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. When the subscribed 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.

[0276] In a possible implementation, the UDM may store the information for distinguishing the first path and the path identifier 1, or the corresponding relationship between the information for distinguishing the first path and the path identifier 1, in the subscribed data or context information corresponding to the UE.

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

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

[0279] In a possible implementation, the UDM sends the UE's capability information indicating that the UE supports dual connectivity to AMF1. AMF1 allocates a path identifier according to the UE's capability information. That is, step 605 may be executed after step 608.

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

[0281] The Registration Accept message includes the path identifier 1, which is used by the UE to determine / identify / mark the first path.

[0282] In a 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 the 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 RAN1. For example, the UE may associate / map the path identifier 1 with the currently connected RAN1 through circuit logic, line logic, protocol stack logic, etc. Subsequently, the UE may determine the first path corresponding to RAN1 according to the path identifier 1 and the association / mapping relationship.

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

[0284] The AN message includes capability information. For the relevant description of the capability information, refer to Figure 6 Step 601 in it, which will not be elaborated here.

[0285] It should be noted that when the UE determines that it hopes to access the network through two different paths simultaneously, step 610 is executed. Exemplarily, before the UE sends the AN message to RAN2, the UE determines that it can access the network through two paths, and the UE determines that it has already accessed the network through the first path. Exemplarily, the UE can determine that it can access the network through two paths according to the dual-connection information. For the relevant description of the dual connection, refer to Figure 6 Step 601 in it.

[0286] This embodiment takes the UE selecting RAN2 as the second path to initiate the registration process and sending the AN message to RAN2 as an example for introduction.

[0287] Step 611: RAN2 selects an AMF.

[0288] For the relevant description of selecting the AMF, refer to step 602, which will not be elaborated here.

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

[0290] This embodiment takes RAN2 selecting AMF2 as an example for illustration.

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

[0292] For the relevant description, refer to step 603, which will not be elaborated here.

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

[0294] For the relevant description, refer to Figure 2 The relevant description in step 204 in it, which will not be elaborated here.

[0295] Step 614: AMF2 allocates a path identifier (such as a path identifier).

[0296] For the relevant description, refer to the relevant description in step 605, which will not be elaborated here.

[0297] This embodiment takes AMF2 allocating the path identifier 2 for the second path as an example for illustration.

[0298] Step 615: AMF2 sends a registration request to the UDM.

[0299] For the relevant description, refer to the relevant instructions in step 606, which will not be elaborated here.

[0300] Step 616: The UDM queries the subscribed data.

[0301] For the relevant description, refer to the relevant instructions in step 607, which will not be elaborated here.

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

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

[0304] The Registration Accept message includes a path identifier 2, which is used for the UE to determine / identify / recognize / mark the second path.

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

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

[0307] Exemplarily, the UDM sends the path identifier and the information for differentiating paths to the UDR through a data management create / update request message (such as Nudr_DM_Create / Updaterequest).

[0308] In a possible implementation, the UDM can send one or more path identifiers and the information for differentiating paths to the UDR. For example, the information for differentiating paths is the identifier of the AMF. That is, the information for differentiating the first path is the identifier of AMF1, and the information for differentiating the second path is the identifier of AMF2. The UDM sends the identifier of AMF1 and the path identifier 1, and / or, the identifier of AMF2 and the path identifier 2 to the UDR. In the subsequent session establishment process, the PCF can obtain the path identifier and the corresponding information for differentiating paths through the UDR.

[0309] In another possible implementation, the UDM may send the identification information of the UE, as well as the path identifier corresponding to the UE and the information for differentiating paths, to the UDR.

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

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

[0312] In one possible implementation, the PCF generates a routing rule (such as URSP) based on the path identifier and the information for differentiating paths. The routing rule includes the path identifier. The information for differentiating paths can be used to determine the path priority. Subsequently, the routing rule is sent to the UE, and the UE can select the path corresponding to the path identifier from multiple paths under the same access type to transmit services through this routing rule. When the routing rule is URSP, it can be understood that the generated here is an enhanced URSP.

[0313] In another possible implementation, the PCF receives the path identifier 1 and the information for differentiating the first path from AMF1, and receives the path identifier 2 and the information for differentiating the second path from AMF2. It should be noted that when the AMFs in the first path and the second path are the same, such as both being AMF1, the PCF may receive the path identifier 1 and the information for differentiating the first path, as well as the path identifier 2 and the information for differentiating the second path, from AMF1.

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

[0315] Through the steps of method 600, when the UE accesses the network through two paths of 3GPP access types, the AMF allocates path identifiers. The UE receives the first path identifier from the first path and the second path identifier from the second path. Thus, both the UE and the network can differentiate the two different paths according to the path identifiers.

[0316] As Figure 7 shown, in combination with the above Figure 6, a method 700 applicable to this application is introduced. This method is applicable to a 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 traffic splitting rule based on the path identifier, and the UE obtains the traffic splitting rule. In one possible implementation, the UE executes the steps in method 700 after the registration process is completed for both paths. In another possible implementation, the UE executes steps 701 - 713 of method 700 after the registration of the first path is completed, and the UE executes steps 714 - 720 of method 700 after the registration of the second path is completed. Through method 700, the UE can determine the transmission path of service data according to the path identifier. The method includes the following steps:

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

[0318] In one possible implementation, the session establishment request message is a PDU session establishment request (PDU Session Establishment Request) message. The relevant description of the PDU session establishment request message can be referred to Figure 3 in step 301.

[0319] In this embodiment, taking the UE selecting RAN1 as the first path to initiate the session establishment process and sending a session establishment request message to AMF1 through RAN1 as an example for introduction.

[0320] Step 702: The AMF selects an SMF.

[0321] In one possible implementation, AMF1 selects an SMF that supports dual connectivity according to the capability information (such as the UE supports dual connectivity). The SMF that supports dual connectivity can be understood as that this SMF can recognize the newly added parameters in the message, such as the path identifier, the information for differentiating paths, etc. This SMF supports generating a traffic splitting rule including the path identifier (for example, an enhanced traffic splitting rule). Through the traffic splitting rule including the path identifier, the path corresponding to the path identifier can be selected for transmitting services among multiple paths under the same access type. The relevant description of the capability information refers to Figure 6 in step 601.

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

[0323] The session context request message includes path identifier 1 and / or the information for differentiating the first path. Among them, path identifier 1 is the one that AMF1 is in Figure 6The information allocated in step 605 for distinguishing the first path may be one or more of location information, access type, access technology type, registration type, RAN identifier, AMF identifier. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell to which the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, different paths can be identified by the ULI.

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

[0325] In another possible implementation, the session context request message includes path identifier 1 and the information for distinguishing the first path. The information for distinguishing the first path is, for example, 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 according to path identifier 1.

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

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

[0328] Step 704: The SMF obtains the subscribed data from the UDM.

[0329] The subscribed data (such as session management subscribed data) may include a path identifier, or a path identifier and the information for distinguishing paths. Among them, the path identifier and the information for distinguishing paths may be path identifier 1 and the information for distinguishing the first path, and path identifier 2 and the information for distinguishing the second path. Path identifier 1 and the information for distinguishing the first path are stored by the UDM in Figure 6 in step 607, and path identifier 2 and the information for distinguishing the second path are stored by the UDM in Figure 6Stored in step 616. Exemplarily, the UDM may store the above path identifier and the information for differentiating paths in the subscribed data or context information corresponding to the UE.

[0330] In a possible implementation manner, the subscribed data includes a path identifier. Exemplarily, the SMF sends the information for differentiating the first path to the UDM, and this information is obtained by the SMF from AMF1 in step 703. The UDM determines the corresponding path identifier, that is, path identifier 1, according to the information for differentiating the first path, and sends this path identifier to the SMF. Exemplarily, the information for differentiating the first path is the identifier of the AMF, that is, AMF1. The SMF sends the SUPI of the UE and AMF1 to the UDM. The UDM queries the subscribed data or context information corresponding to the UE according to the SUPI, and sends the path identifier corresponding to AMF1 (that is, path identifier 1) to the SMF according to the association relationship between the stored path identifier and the information for differentiating the first path.

[0331] In another possible implementation manner, the subscribed data includes a path identifier and the information for differentiating paths. Exemplarily, the information for differentiating paths is the AMF identifier, that is, the above information is that path identifier 1 corresponds to AMF1, and path identifier 2 corresponds to AMF2. The SMF receives a session context request message from AMF1 in step 703, so that the SMF can subsequently determine to send data to AMF1 according to path identifier 1.

[0332] It should be noted that in the case where the above session context request message includes path identifier 1, the subscribed data may not include the path identifier and the information for differentiating paths either. For the relevant description of the subscribed data, reference can be made to Figure 3 step 303 in

[0333] In a possible implementation manner, 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 for differentiating the first path in the context information of the UE.

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

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

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

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

[0338] In a possible implementation, when the policy request message includes a path identifier, or a path identifier and information for differentiating paths, the PCF can obtain the path identifier, such as path identifier 1.

[0339] In another possible implementation, when the policy request message includes information for differentiating paths, the PCF can obtain the path identifier from the UDR.

[0340] In a possible implementation, the SMF selects a multi-connection supported PCF based on the path identifier and sends a policy request message to the multi-connection supported PCF. The multi-connection supported PCF can be understood as a PCF that can recognize new parameters, such as a path identifier. This PCF supports generating policy rules including the path identifier (such as enhanced PCC rules), and the policy rules are used to select the path corresponding to the path identifier for traffic transmission among multiple paths under the same access type.

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

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

[0343] It should be noted that the UDR can obtain the association relationship between the path identifier and the information for differentiating paths through step 619 in method 600.

[0344] In a possible implementation, the PCF sends the information for differentiating paths to the UDR. The UDR determines the path identifier according to the above association relationship and sends the path identifier to the PCF. For example, the information for differentiating paths such as 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 according to the association relationship between 5G and path identifier 1, and then the UDR sends path identifier 1 to the PCF, or the UDR sends path identifier 1 and 6G to the PCF.

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

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

[0347] The policy response message includes policy rules.

[0348] In a possible implementation, the policy rules (such as PCC rules) in the policy response message may include path identifiers. Exemplarily, when the policy rule is a PCC rule, it can be understood that an enhanced PCC rule is generated here. Through this policy information, the UE or the UPF can select the path corresponding to the path identifier for traffic transmission among multiple paths under the same access type.

[0349] In a possible implementation, the PCF can generate policy rules based on the path identifier and the information for differentiating paths. Among them, the information for differentiating paths can be used to determine the path priority. For example, generate the Mobility and Anchor PDU Session Control (MA PDU Session Control) information in the policy rule. This MA PDU session control information allows the PCF to control one or more of the following: splitting mode, splitting function, splitting mode indication, threshold value, charging information, usage monitoring information. Exemplarily, taking the information for differentiating the first path corresponding to path identifier 1 as 6G and the splitting mode as the Active standby mode as an example, assuming that 6G is higher than 5G and 4G, the PCF can determine that this path is the Active path according to the higher priority of 6G. The policy rule generated by the PCF based on path identifier 1 and including path identifier 1 can be represented by Table 1:

[0350] Table 1 Policy Rule (Including Path Identifier 1)

[0351]

[0352] Among them, the service descriptor is used to define the traffic flow. This rule represents that for the traffic flow corresponding to this service descriptor, the Active standby splitting 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 traffic flow.

[0353] It should be noted that when the policy rules generated by the PCF do not include path identifiers, the relevant descriptions of the policy rules can refer to the PCC rules. In this embodiment, the split mode in the policy rules is used as active standby for illustration. The policy rules generated by the PCF without path identifiers can be represented by Table 2:

[0354] Table 2 Policy Rules (Without Path Identifiers)

[0355]

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

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

[0358] Step 709: The SMF selects a UPF.

[0359] In a possible implementation, the UPF selected by the SMF supports storing multiple contexts of the same UE. It can be understood that the UPF supports data (or service) splitting for multiple paths through which the UE is connected to the network. For example, the UPF supports data splitting for paths through which the UE is connected to the network via dual 3GPP access types. Or the UPF supports splitting rules including path identifiers (such as enhanced N4 rules). The splitting rules including path identifiers can be used by the UPF to select the path corresponding to the path identifier for transmitting services among multiple paths under the same access type.

[0360] Step 710: The SMF sends a splitting rule to the UPF.

[0361] The SMF can generate a splitting rule (such as an N4 rule) for the UPF to use according to the policy rules. The splitting rule includes a path identifier. Exemplarily, the multi-access rule (MAR) includes a path identifier. When the splitting rule is an N4 rule, it can be understood that an enhanced N4 rule is generated here. The splitting rule is used by the UPF to select the path corresponding to the path identifier for transmitting downlink service data among multiple paths under the same access type.

[0362] In one possible implementation, the policy information does not include a path identifier. The SMF can generate a traffic splitting rule based on the path identifier and the information used to distinguish paths. Exemplarily, taking the information used to distinguish the first path corresponding to path identifier 1 as 6G and the traffic splitting mode as the Active standby mode as an example, the SMF can determine that this path is the Active path based on the higher priority of 6G. The traffic splitting rule generated by the SMF based on path identifier 1 and including path identifier 1 can be represented using Table 3:

[0363] Table 3 Traffic Splitting Rule

[0364]

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

[0366] In one possible implementation, the SMF sends an N4 session establishment request (N4 Session Establishment Request) message to the UPF, and the above traffic splitting rule is included in this message.

[0367] Step 711: The SMF sends a Namf_Communication_N1N2MessageTransfer message to AMF1.

[0368] The SMF can generate a traffic splitting rule (such as an ATSSS rule) used by the UE according to the policy rule. The traffic splitting rule includes a path identifier. When the traffic splitting rule is an ATSSS rule, it can be understood that the generated here is an enhanced ATSSS rule (enhanced ATSSS rule). The traffic splitting rule is used for the UE to select the path corresponding to the path identifier for traffic transmission among multiple paths under the same access type. Exemplarily, the traffic splitting rule can be represented using the above Table 3. It should be noted that the traffic splitting rule used by the UPF is for downlink data transmission, and the traffic splitting rule used by the UE is for uplink data transmission. The IP addresses in the service descriptors of the traffic splitting rules used by the UE and the UPF are different, and this IP address is used to identify the destination of the IP traffic flow. The Namf_Communication_N1N2MessageTransfer message includes path identifier 1 and the traffic splitting rule. This path identifier 1 is used for AMF 1 to determine the RAN corresponding to this path identifier 1. For example, the UE is connected to AMF1 through RAN1 and RAN2, that is, the AMFs on the first path and the second path are the same, that is, AMF1. AMF 1 can determine the first path where RAN 1 is located according to path identifier 1.

[0369] In a possible implementation, the N1 interface session management container (N1 SMContainer) in the N1N2 message transfer message includes a traffic splitting rule and a Session Establishment Accept message (which can be regarded as a response to the session establishment request in step 701).

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

[0371] The N2 session request message includes a traffic splitting rule.

[0372] In a possible implementation, AMF1 can determine which access network device (such as RAN) the above information is sent to according to the path identifier sent by the SMF. For example, AMF1 determines to send an N2 session request message to RAN1 in the first path according to path identifier 1.

[0373] 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 traffic splitting rule.

[0374] Step 713: RAN1 sends a traffic splitting rule to the UE.

[0375] In a possible implementation, the traffic splitting rule includes path identifier 1 and a service descriptor. The UE can determine through which path the service data should be transmitted according to the traffic splitting rule. For example, by default in the Active standby mode, the path corresponding to path identifier 1 for the UE is 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 on the first path.

[0376] In another possible implementation, the traffic splitting rule includes path identifier 1, a traffic splitting mode, and a service descriptor. The UE can determine through which path the service data should be transmitted according to the traffic splitting rule. For example, when the traffic splitting mode for the UE is the Activestandby mode and the path corresponding to path identifier 1 is 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 on the first path.

[0377] Exemplarily, the UE determines the corresponding first path according to path identifier 1. The relevant description of the association / mapping between the path identifier and the path can refer to step 609.

[0378] In a possible implementation, RAN1 sends a traffic splitting rule to the UE during the process of establishing radio interface resources between RAN1 and the UE.

[0379] It should be noted that for the subsequent steps of the UE to establish the user plane channel of the first path through RAN1 and AMF1, please refer to Figure 3 Steps 313 to 318 in it will not be elaborated here.

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

[0381] In a possible implementation, the session establishment request message is a PDU session establishment request (PDU Session Establishment Request) message. The relevant description of the PDU session establishment request message can be referred to Figure 3 Step 301 in it.

[0382] In this embodiment, an example is given where the UE selects RAN2 as the second path to initiate the session establishment process and sends a session establishment request message to AMF2 through RAN2.

[0383] Step 715: AMF2 sends the path identifier 2 and / or the information for differentiating the second path to the SMF.

[0384] The path identifier 2 is allocated by AMF2 in Figure 6 Step 614 in it. The information for differentiating the second path can be one or more of location information, access type, access technology, registration type, RAN identifier, and AMF identifier. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell where the UE accesses RAN1. Since the cells accessed by the UE in different paths are different, the ULI can be used to identify different paths.

[0385] In a possible implementation, AMF2 sends the path identifier 2 to the SMF. The SMF can obtain the path identifier 2 through AMF2, so that the SMF can determine to send data to AMF2 according to the path identifier 2 subsequently.

[0386] In another possible implementation, AMF2 sends the path identifier 2 and the information for differentiating the second path to the SMF. The information for differentiating the second path is, for example, 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 determine to send data to AMF2 on the second path corresponding to 5G according to the path identifier 2 subsequently.

[0387] In still another possible implementation, AMF2 sends the information for differentiating the second path to the SMF. Thus, the SMF can obtain the path identifier 2 corresponding to the second path from the UDM or PCF according to the information for differentiating the second path.

[0388] In a possible implementation, the path identifier 2 and / or the information used to distinguish the second path are sent via a session context request or update message. For example, 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.

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

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

[0391] In another possible implementation, when the SMF sends the information used to distinguish the second path to the PCF, the PCF can obtain the path identifier 2 from the UDR.

[0392] In a possible implementation, the path identifier 2 and / or the information used to distinguish the second path are sent via a policy request message. For example, a policy association establishment request message (SM Policy Association EstablishmentRequest) message, or a policy association modification request message (SM Policy Association ModificationRequest) message.

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

[0394] In a possible implementation, the policy update message includes updated policy rules, and the policy rules (such as PCC rules) include the path identifier 2.

[0395] In a possible implementation, the PCF can generate policy rules based on the path identifier and the information used to distinguish paths. Among them, the information used to distinguish paths can be used to determine the path priority. Exemplarily, here, taking the information used to distinguish the first path corresponding to the path identifier 1 as 6G, the information used to distinguish the second path corresponding to the path identifier 2 as 5G, and the traffic splitting mode as the Active standby mode as an example, the PCF can determine that the first path is the Active path and the second path is the Standby path according to the fact that the priority of 6G is higher than that of 5G. The policy rules generated by the PCF based on the path identifier and including the path identifier 1 and the path identifier 2 can be represented by Table 4:

[0396] Table 4 Policy Rules (including Path Identifiers 1 and 2)

[0397]

[0398] Among them, the service descriptor is used to define the service flow. This rule represents that for the service flow corresponding to this service descriptor, an active standby traffic splitting mode is adopted. 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.

[0399] Step 718: The SMF sends the traffic splitting rule to the UPF.

[0400] The SMF can generate a traffic splitting rule (such as an N4 rule) for the UPF to use, and this traffic splitting rule includes Path Identifier 2.

[0401] In a possible implementation, when Step 717 is not executed, the SMF can generate a traffic splitting rule according to the path identifier and the information for differentiating paths. Exemplarily, here, taking the information for differentiating the first path corresponding to Path Identifier 1 as 6G, the information for differentiating the second path corresponding to Path Identifier 2 as 5G, and the traffic splitting mode as 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 according to the higher priority of 6G compared to 5G. The traffic splitting rule generated by the SMF according to the path identifier and including Path Identifier 1 and Path Identifier 2 can be represented by the above Table 4, which will not be elaborated here.

[0402] In another possible implementation, when Step 717 is executed, the SMF can obtain the updated policy rule sent by the PCF, and thus generate a traffic splitting rule including Path Identifiers 1 and 2 according to the updated policy rule. The traffic splitting rule can be represented by the above Table 4, which will not be elaborated here.

[0403] In a possible implementation, the SMF sends an N4 session establishment request (N4 Session Establishment Request) message to the UPF, and this message includes the above traffic splitting rule.

[0404] Step 719: The SMF sends Path Identifier 2 and the traffic splitting rule to the AMF2.

[0405] The SMF can generate the traffic splitting rules (such as ATSSS rules) used by the UE. The traffic splitting rules include the path identifier 2. Exemplarily, the traffic splitting rules can be characterized by Table 4 above. It should be noted that the traffic splitting rules used by the UPF are for downlink data transmission, and the traffic splitting rules used by the UE are for uplink data transmission. The IP addresses in the service descriptors of the traffic splitting rules used by the UE and the UPF are different, and this IP address is used to identify the destination of the IP traffic flow.

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

[0407] In a possible implementation, the path identifier 2 and the traffic splitting rules are sent through the N1N2 message transmission message (Namf_Communication_N1N2MessageTransfer).

[0408] Step 720: The AMF2 sends the traffic splitting rules to the UE through the RAN2.

[0409] In a possible implementation, the AMF2 can determine which access network device (such as RAN) the above information is sent to according to the path identifier sent by the SMF. For example, the AMF2 determines to send the traffic splitting rules to the RAN2 in the second path according to the path identifier 2.

[0410] In a possible implementation, the traffic splitting rules include the path identifier 1, the path identifier 2, and the service descriptor. The UE can determine which path the service data should be transmitted through according to the traffic splitting rules. For example, by default, it is in the Active standby mode. The path corresponding to the path identifier 1 for the UE is the Active path. When the first path corresponding to the path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor on the first path. Or, when the first path is unavailable and the second path identified by the path identifier 2 is available, the second path is used to transmit the service flow corresponding to the service descriptor.

[0411] In another possible implementation, the traffic splitting rule includes path identifier 1, path identifier 2, a traffic splitting mode, and a service descriptor. Based on the traffic splitting rule, the UE can determine which path the service data should be transmitted through. For example, if the traffic splitting mode of the UE is the Active standby mode, the path corresponding to path identifier 1 is the Active path, and the path corresponding to path identifier 2 is the Standby path. When the first path corresponding to path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor on the first path. Alternatively, when the first path is unavailable and the second path identified by path identifier 2 is available, the second path is used to transmit the service flow corresponding to the service descriptor.

[0412] Exemplarily, the UE determines the corresponding first path based on path identifier 1. For relevant descriptions, refer to step 609. The UE determines the corresponding second path based on path identifier 2. For relevant descriptions, refer to step 618.

[0413] It should be noted that for the subsequent steps of the UE to establish the user plane channel of the second path through RAN2 and AMF2, refer to Figure 3 steps 313 - 318 therein, which will not be elaborated here.

[0414] Through the steps of method 700, when the UE accesses the network through two paths of 3GPP access types, the UE first obtains the path identifiers corresponding to different paths under the same access type through the registration process. When the UE establishes sessions through multiple different paths under the same access type, it can learn which path the service data should be transmitted through by receiving the traffic splitting rule containing the path identifier, thus enabling better execution of service transmission.

[0415] Through the steps of method 700, when the UE accesses the network through two paths of 3GPP access types, the AMF allocates path identifiers. The UE receives the first path identifier from the first path and the second path identifier from the second path. Thus, both the UE and the network can distinguish the two different paths based on the path identifiers. In addition, the UE receives the traffic splitting rule containing the path identifier, and then the UE can transmit the service data through the path corresponding to the path identifier according to the traffic splitting rule corresponding to the service data, thereby improving the transmission efficiency.

[0416] As Figure 8 shown, a method 800 applicable to this application is introduced. This method is applicable to the UE accessing the network through multiple paths of the same access type (such as two paths of 3GPP access types). In method 800, the UDM allocates path identifiers for the UE during the registration process and sends them to the UE. Through method 800, the UE can determine the transmission path based on the path identifier. This method includes the following steps: Step 801: The UE sends an AN message to RAN1.

[0417] In a possible implementation, the AN message includes capability information. For the relevant description of the capability information, refer to Figure 6 step 601 in it, which will not be elaborated here.

[0418] In a possible implementation, when the UE determines that it has dual-connectivity capability, or the UE hopes to access the network simultaneously through two different paths of 3GPP access types, the AN message sent in step 801 includes capability information. For the relevant description, refer to Figure 6 step 601 in it, which will not be elaborated here.

[0419] In this embodiment, an example is given where the UE selects RAN1 as the first path to initiate the registration process and sends an AN message to RAN1.

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

[0421] Step 802: RAN1 selects an AMF.

[0422] In a possible implementation, the capability information is in a field that can be parsed by the RAN in the AN message. RAN1 selects an AMF that supports dual connectivity according to the capability information. For the relevant description of the AMF that supports dual connectivity, refer to Figure 6 step 602 in it, which will not be elaborated here.

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

[0424] The registration request message includes capability information.

[0425] Optionally, RAN1 sends information for differentiating paths to AMF1. In a possible implementation, the information for differentiating paths is one or more of location information, access type, access technology type, registration type, RAN identifier. The location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell where the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, the ULI can be used to identify different paths.

[0426] In a possible implementation, RAN1 sends an NGAP message to AMF1, which can also be called an N2 message. Among them, the N2 message includes a registration request message and information for differentiating paths. It can be understood that in this N2 message, the registration request message and the information for differentiating paths exist side by side.

[0427] In another possible implementation, RAN1 can send a registration request message and information for differentiating paths to AMF1 through two N2 messages respectively.

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

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

[0430] For relevant descriptions, refer to Figure 2 the relevant descriptions in step 204 therein, which will not be elaborated here.

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

[0432] The registration request is for AMF1 to register with the UDM as the AMF serving the UE. Exemplarily, the registration request is a Nudm_UECM_Registration request.

[0433] 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 a multi-connection method. It should be noted that the indication information may be the same as or different from the capability information reported by the UE in step 801. Exemplarily, when they are different, it can be understood that AMF1 processes the information reported by the UE. For example, if the capability information reported by the UE indicates that the UE supports dual connectivity, the indication information sent by AMF1 to the UDM indicates that the UE accesses the network through a multi-connection method. It should be noted that the name of the multi-radio capabilities can also be replaced with any one of the extended dual connectivity or multi-connection names in the above dual connectivity architecture.

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

[0435] In a possible implementation, the AMF 1 may select a UDM that supports dual registration based on the capability information or the registration type. For example, the registration type is a newly added registration type, which is used to indicate that the UE registers two paths. Exemplarily, the name of the newly added registration type may be DualSteer Registration, but the name is not limited here.

[0436] Step 806: The UDM allocates a path identifier (such as a path identifier).

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

[0438] Optionally, the UDM may query the subscription data of the UE based on the identifier of the UE. The subscription data of the UE includes the capability information of the UE, so as to determine whether the UE is allowed to access the network through dual connectivity. When the subscription data of the UE allows the UE to access the network through dual connectivity, a path identifier is allocated. It can be understood that when the UDM determines that the UE is not allowed to use dual connectivity to access the network based on the subscription data of the UE, the UDM does not allocate a path identifier.

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

[0440] In this embodiment, an example is given in which the UDM allocates the path identifier 1 for the first path where the AMF1 is located.

[0441] Step 807: The UDM sends a registration response to the AMF 1.

[0442] The registration response message includes the path identifier 1.

[0443] Optionally, the registration response message further includes the information for distinguishing the first path, such as the RAN identifier, so that the AMF can determine the corresponding path according to the information for distinguishing the paths.

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

[0445] Step 808: The AMF1 sends a registration accept (such as Registration Accept) message to the UE through the RAN1.

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

[0447] In a possible implementation, after the AMF 1 receives the path identifier, the AMF 1 may store the information for differentiating the first path and the path identifier 1, or the corresponding relationship between the information for differentiating the first path and the path identifier 1, in the UE's context information.

[0448] In a 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 corresponding to the current path, the RAN identifier, the access type, or the protocol stack, interface, or link used. That is, the UE may associate / map the path identifier 1 with the currently connected RAN1. For example, the UE may associate / map the path identifier 1 with the currently connected RAN1 through circuit logic, line logic, protocol stack logic, etc. Subsequently, the UE may determine the first path corresponding to RAN1 based on the path identifier 1 and the association / mapping relationship.

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

[0450] The AN message includes capability information. For the relevant description of the capability information, refer to Figure 6 Step 601 in, which will not be elaborated here.

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

[0452] In this embodiment, an example is given where the UE selects RAN2 as the second path to initiate the registration process and sends an AN message to RAN2.

[0453] Step 810: RAN2 selects an AMF.

[0454] For the relevant description of selecting the AMF, refer to step 602, which will not be elaborated here.

[0455] It should be noted that the AMF selected by RAN2 may be AMF1 or an AMF2 different from AMF1.

[0456] In this embodiment, an example is given where RAN2 selects AMF2.

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

[0458] The registration request message includes capability information. For relevant descriptions, refer to step 803, which will not be elaborated here.

[0459] Step 812: AMF2 triggers an authentication and security procedure between the UE, AUSF, and UDM.

[0460] For relevant descriptions, refer to Figure 2 the relevant explanations in step 204 therein, which will not be elaborated here.

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

[0462] The registration request includes indication information. For relevant descriptions, refer to the relevant explanations in step 805, which will not be elaborated here.

[0463] Step 814: The UDM allocates a path identifier (such as a path identifier).

[0464] In a possible implementation, the UDM allocates a path identifier according to the indication information. For example, for different paths of the same UE (such as the SUPI of the UE on different paths being the same), the UDM allocates different path identifiers respectively. Or the UDM allocates a globally unique identifier for each path, that is, the UDM does not distinguish between the same or different paths of different UEs when allocating paths.

[0465] Optionally, the UDM can query the subscribed data of the UE based on the identifier of the UE to determine whether the UE is allowed to access the network through dual connectivity. When the subscribed data of the UE allows the UE to access the network through dual connectivity, a path identifier is allocated. It can be understood that when the UDM determines based on the subscribed data of the UE that the UE is not allowed to access the network using dual connectivity, the UDM will not allocate a path identifier.

[0466] In a possible implementation, the UDM can store the information for distinguishing the second path and the path identifier 2, or the corresponding relationship between the information for distinguishing the second path and the path identifier 2, in the subscribed data or context information corresponding to the UE.

[0467] In this embodiment, an example is given where the UDM allocates the path identifier 2 for the second path where AMF2 is located.

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

[0469] The registration response message includes the path identifier 2.

[0470] Optionally, the registration response message further includes information for differentiating the second path, such as the RAN identifier, so that the AMF can determine the corresponding second path according to the information for differentiating the second path.

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

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

[0473] The Registration Accept message includes a path identifier 2, which is used by the UE to determine / identify / mark the second path.

[0474] In a possible implementation, after receiving the path identifier, AMF2 may store the information for differentiating the second path and the path identifier 2, or the corresponding relationship between the information for differentiating the second path and the path identifier 2, in the UE's context information.

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

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

[0477] Exemplarily, the UDM sends the path identifier and the information for differentiating paths to the UDR through a data management create / update request message (such as Nudr_DM_Create / Update request).

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

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

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

[0481] In one possible implementation, the PCF generates a routing rule (such as URSP) according to the path identifier and the information for differentiating paths. The routing rule includes the path identifier. Among them, the information for differentiating paths can be used to determine the path priority. Subsequently, this routing rule is sent to the UE, and the UE can select the path corresponding to the path identifier from multiple paths under the same access type through this routing rule. When the routing rule is URSP, it can be understood that the enhanced URSP is generated here.

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

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

[0484] Through the steps of method 800, when the UE accesses the network through two paths of 3GPP access types, the UDM allocates path identifiers, and the UE receives the first path identifier from the first path and the second path identifier from the second path. Thus, both the UE and the network can differentiate the two different paths according to the path identifiers.

[0485] As Figure 9 shown, combining the above Figure 8, a method 900 applicable to this application is introduced. This method is applicable to the 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 traffic splitting rule based on the path identifier, and the UE obtains the traffic splitting rule. In one possible implementation, the UE executes the steps in method 900 after the registration process is completed for both paths. In another possible implementation, the UE executes the session establishment process for the first path of method 900 after the first path is registered, and the UE executes the session establishment process for the second path of method 900 after the second path is registered. Through method 900, the UE can determine the transmission path of service data according to the path identifier. This method includes the following steps:

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

[0487] In one possible implementation, the session establishment request message is a PDU session establishment request (PDU SessionEstablishment Request) message. The relevant description of the PDU session establishment request message can refer to Figure 3 Step 301 in.

[0488] In this embodiment, an example is introduced where the UE selects RAN1 as the first path to initiate the session establishment process and sends a session establishment request message to AMF1 through RAN1.

[0489] Step 902: The AMF selects an SMF.

[0490] In one possible implementation, AMF1 selects an SMF that supports dual connectivity according to the capability information (such as the UE supports dual connectivity). The SMF that supports dual connectivity can be understood as that this SMF can identify the newly added parameters in the message, such as the path identifier, the information for distinguishing paths, etc. This SMF supports generating a traffic splitting rule including the path identifier (for example, an enhanced traffic splitting rule). Through the traffic splitting rule including the path identifier, the path corresponding to the path identifier can be selected for transmitting services among multiple paths under the same access type. The relevant description of the capability information refers to Figure 6 Step 601 in.

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

[0492] Optionally, the session context request message includes path identifier 1 and / or the information for distinguishing the first path. Among them, path identifier 1 is the one allocated by the UDM in Figure 8The information allocated in step 806 for differentiating the first path may be one or more of location information, access type, access technology, registration type, RAN identifier, and AMF identifier. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell where the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, the ULI can be used to identify different paths. For the relevant description, refer to step 703, which will not be elaborated here.

[0493] It should be noted that the session context request message may not include the path identifier 1 and / or the information for differentiating the first path, and subsequently the SMF obtains the path identifier and the information for differentiating paths from the UDM.

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

[0495] Step 904: The SMF obtains the subscribed data from the UDM.

[0496] The subscribed data (such as session management subscribed data) may include the path identifier and / or the information for differentiating paths. Among them, the path identifier and the information for differentiating paths may be the path identifier 1 and the information for differentiating the first path, and the path identifier 2 and the information for differentiating the second path. The path identifier 1 and the information for differentiating the first path are stored by the UDM in Figure 8 step 806, and the path identifier 2 and the information for differentiating the second path are stored by the UDM in Figure 8 step 814.

[0497] In a possible implementation, the subscribed data includes the path identifier. Exemplarily, the SMF sends the information for differentiating the first path to the UDM, and this information is obtained by the SMF from AMF1 in step 903. The UDM determines the corresponding path identifier, that is, the path identifier 1, according to the information for differentiating the first path, and sends the path identifier to the SMF. Exemplarily, the information for differentiating the first path is the identifier of the AMF, that is, AMF1. The SMF sends the SUPI of the UE and AMF1 to the UDM. The UDM queries the subscribed data or context information corresponding to the UE according to the SUPI, and sends the path identifier corresponding to AMF1 (that is, the path identifier 1) to the SMF according to the stored association relationship between the path identifier and the information for differentiating the first path.

[0498] In another possible implementation, the subscription data includes a path identifier and information for differentiating paths. Exemplarily, the information for differentiating paths is an AMF identifier, that is, the path identifier and the information for differentiating paths are such that path identifier 1 corresponds to AMF1 and path identifier 2 corresponds 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 according to path identifier 1. In another example, the UDM queries the subscription data or context information corresponding to the UE according to the SUPI, and sends AMF1 and the corresponding path identifier (i.e., path identifier 1), and sends AMF2 and the corresponding path identifier (i.e., path identifier 2) to the SMF according to the stored association relationship between the path identifier and the information for differentiating paths.

[0499] It should be noted that in the case where the above session context request message includes path identifier 1, the subscription data may not include the path identifier and the information for differentiating paths either. For the relevant description of the subscription data, reference can be made to Figure 3 step 303 in

[0500] In a possible implementation, after receiving the path identifier, the SMF can store the path identifier in the context information of the UE. Exemplarily, the SMF can store the association relationship between path identifier 1 and the information for differentiating the first path and the association relationship between path identifier 2 and the information for differentiating the second path in the context information of the UE.

[0501] Step 905: Refer to Figure 7 the relevant descriptions in steps 705-720 in

[0502] Through the steps of method 900, when the UE accesses the network through two 3GPP access type paths, the UDM allocates path identifiers, the UE receives the first path identifier from the first path, and receives the second path identifier from the second path. Thus, both the UE and the network can differentiate the two different paths according to the path identifiers. In addition, the UE receives a traffic splitting rule including the path identifier, and further the UE can transmit the service data through the path corresponding to the path identifier according to the traffic splitting rule corresponding to the service data, thereby improving the transmission efficiency.

[0503] Such as Figure 10As shown, a method 1000 applicable to this application is introduced. This method is applicable to a UE accessing the network through multiple paths of the same access type (for example, two paths of 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 traffic splitting rule based on the path identifier, and the UE obtains the path identifier and the traffic splitting rule. Through method 1000, the UE can determine the transmission path of service data according to the path identifier. This method includes the following steps:

[0504] Step 1001: Refer to Figure 6 the relevant descriptions of steps 601 - 608 therein, which will not be elaborated here.

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

[0506] It should be noted that the Registration Accept message sent by AMF1 through RAN1 does not include path identifier 1.

[0507] Step 1003: Refer to Figure 6 the relevant descriptions of steps 610 - 617 therein, which will not be elaborated here.

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

[0509] It should be noted that the Registration Accept message sent by AMF2 through RAN2 does not include path identifier 2.

[0510] Step 1005: Refer to Figure 6 the relevant descriptions of steps 619 - 620 therein, which will not be elaborated here.

[0511] Step 1006: Refer to Figure 7 the relevant descriptions of steps 701 - 711 therein, which will not be elaborated here.

[0512] Step 1007: AMF1 sends the traffic splitting rule and path identifier 1 to the UE through RAN1.

[0513] In a possible implementation, the traffic splitting rule includes path identifier 1 and a service descriptor. The UE can determine through which path the service data should be transmitted according to the traffic splitting rule. For example, by default, it is in the Active standby mode. The path corresponding to path identifier 1 for the UE is 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 on the first path.

[0514] In another possible implementation, the traffic splitting rule includes a path identifier 1, a traffic splitting mode, and a service descriptor. Based on the traffic splitting rule, the UE can determine through which path the service data should be transmitted. For example, if the traffic splitting mode of the UE is the Active standby mode and the path corresponding to the path identifier 1 is the Active path, when the first path corresponding to the path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor over the first path.

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

[0516] 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, or the protocol stack, interface, or link corresponding to the current path. That is, the UE can associate / map the path identifier 1 with the RAN1 corresponding to the current connection. For example, the UE can associate / map the path identifier 1 with the RAN1 corresponding to the current connection through circuit logic, line logic, protocol stack logic, etc. Subsequently, the UE can determine the first path corresponding to the RAN1 based on the path identifier 1 and the association / mapping relationship.

[0517] Step 1008: Refer to Figure 7 the relevant descriptions in steps 714 - 719 in , which will not be elaborated here.

[0518] Step 1009: AMF2 sends the traffic splitting rule and the path identifier 2 to the UE through RAN2.

[0519] In one possible implementation, the traffic splitting rule includes a path identifier 1, a path identifier 2, and a service descriptor. Based on the traffic splitting rule, the UE can determine through which path the service data should be transmitted. For example, by default, it is the Active standby mode. If the path corresponding to the path identifier 1 is the Active path, when the first path corresponding to the path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor over the first path. Or, when the first path is unavailable and the second path identified by the path identifier 2 is available, the second path is used to transmit the service flow corresponding to the service descriptor.

[0520] In another possible implementation, the traffic splitting rule includes a path identifier 1, a path identifier 2, a traffic splitting mode, and a service descriptor. Based on the traffic splitting rule, the UE can determine which path the service data should be transmitted through. For example, if the traffic splitting mode of the UE is the Active standby mode, the path corresponding to the path identifier 1 is the Active path, and the path corresponding to the path identifier 2 is the Standby path. When the first path corresponding to the path identifier 1 is available, the UE transmits the service flow corresponding to the service descriptor through the first path. Or, when the first path is unavailable and the second path identified by the path identifier 2 is available, the second path is used to transmit the service flow corresponding to the service descriptor.

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

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

[0523] Through the steps of method 1000, when the UE accesses the network through two paths of 3GPP access types, the AMF allocates path identifiers. The UE receives the traffic splitting rule containing the first path identifier from the first path and the traffic splitting rule containing the second path identifier from the second path. Thus, both the UE and the network can distinguish the two different paths based on the path identifiers. Furthermore, the UE can transmit the service data through the path corresponding to the path identifier according to the traffic splitting rule corresponding to the service data, thereby improving the transmission efficiency.

[0524] As Figure 11 shown, a method 1100 applicable to this application is introduced. This method is applicable to the UE accessing the network through multiple paths of the same access type (for example, two paths of 3GPP access types). In method 1100, the UDM allocates path identifiers for the UE during the registration process. During the session establishment process, the UE obtains the path identifiers and the traffic splitting rules. Through method 1100, the UE can determine the transmission path of the service data according to the path identifiers. The method includes the following steps:

[0525] Step 1101: Refer to Figure 8 the relevant descriptions of steps 801 - 807 in

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

[0527] It should be noted that the Registration Accept message sent by AMF1 via RAN1 does not include Path Identifier 1.

[0528] Step 1103: Refer to Figure 8 the relevant descriptions in Steps 809 - 815 therein, which will not be elaborated here.

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

[0530] It should be noted that the Registration Accept message sent by AMF2 via RAN2 does not include Path Identifier 2.

[0531] Step 1105: Refer to Figure 8 the relevant descriptions in Steps 817 - 818 therein, which will not be elaborated here.

[0532] Step 1106: Refer to Figure 7 the relevant descriptions in Steps 701 - 711 therein, which will not be elaborated here.

[0533] Step 1107: AMF1 sends the traffic splitting rules and Path Identifier 1 to the UE via RAN1.

[0534] For relevant descriptions, refer to the relevant explanations in Step 1007, which will not be elaborated here.

[0535] Step 1108: Refer to Figure 7 the relevant descriptions in Steps 714 - 719 therein, which will not be elaborated here.

[0536] Step 1109: AMF2 sends the traffic splitting rules and Path Identifier 2 to the UE via RAN2.

[0537] For relevant descriptions, refer to Figure 10 the relevant explanations in Step 1009 therein, which will not be elaborated here.

[0538] Through the steps of Method 1100, when the UE accesses the network through two paths of 3GPP access types, the UDM allocates path identifiers, the UE receives the traffic splitting rules containing the first path identifier from the first path, and receives the traffic splitting rules containing the second path identifier from the second path. Thus, both the UE and the network can distinguish the two different paths according to the path identifiers. Furthermore, the UE can transmit the service data through the path corresponding to the path identifier according to the traffic splitting rules corresponding to the service data, thereby improving the transmission efficiency.

[0539] As Figure 12As shown in the figure, a method 1200 applicable to this application is introduced. This method is applicable to the case where a UE accesses the network through multiple paths of the same access type (for example, two paths of 3GPP access type). In method 1200, during the session establishment process, the AMF allocates a path identifier for the UE, the SMF generates a traffic splitting rule based on the path identifier, and the UE obtains the path identifier and the traffic splitting rule. Through method 1200, the UE can determine the transmission path of service data according to the path identifier. This method includes the following steps:

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

[0541] The session establishment request message includes capability information. For the relevant description of the capability information, please refer to Figure 6 step 601 in, which will not be elaborated here.

[0542] In a possible implementation, the session establishment request message is a PDU session establishment request (PDU Session Establishment Request) message. For the relevant description of the PDU session establishment request message, please refer to Figure 3 step 301 in.

[0543] In this embodiment, it is introduced by taking the UE selecting RAN1 as the first path to initiate the session establishment process and sending a session establishment request message to AMF1 through RAN1 as an example. Step 1202: AMF1 allocates a path identifier (for example, path identifier).

[0544] For the relevant description of AMF1 allocating a path, please refer to Figure 6 step 605 in.

[0545] In this embodiment, it is illustrated by taking AMF1 allocating path identifier 1 for the first path as an example.

[0546] In a possible implementation, AMF1 selects an SMF that supports dual connectivity according to the capability information (such as the UE supports dual connectivity). For the relevant description, please refer to Figure 7 step 702 in.

[0547] Step 1203: AMF1 sends path identifier 1 and information for distinguishing the first path to the SMF.

[0548] The information used to distinguish the first path can be one or more of location information, access type, access technology, registration type, RAN identifier, and AMF identifier. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell to which the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, the ULI can be used to identify different paths. 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. Thus, the SMF can subsequently determine to send data to AMF1 on the first path corresponding to 6G according to path identifier 1.

[0549] In a possible implementation, AMF1 sends path identifier 1 and the information used to distinguish the first path to the 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.

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

[0551] The policy request message includes the path identifier and the information used to distinguish the paths.

[0552] In a possible implementation, the SMF selects a PCF that supports multi-connection according to the path identifier, and sends a policy request message to the PCF that supports multi-connection. The PCF that supports multi-connection can be understood as the PCF that can recognize new parameters, such as the path identifier. This PCF supports generating a policy rule including the path identifier (such as an enhanced PCC rule), and the policy rule is used to select the path corresponding to the path identifier for traffic transmission among multiple paths under the same access type.

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

[0554] Step 1205: Refer to Figure 7 the relevant descriptions in steps 708-711 in , which will not be elaborated here.

[0555] Step 1206: AMF1 sends the traffic splitting rule and path identifier 1 to the UE via RAN1.

[0556] For related descriptions, refer to Figure 10 the relevant description in step 1007 therein, which will not be elaborated here.

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

[0558] The session establishment request message includes capability information. For the relevant description of the capability information, refer to Figure 6 step 601 therein, which will not be elaborated here.

[0559] In a possible implementation, the session establishment request message is a PDU session establishment request (PDU Session Establishment Request) message. For the relevant description of the PDU session establishment request message, refer to Figure 3 step 301 therein.

[0560] In this embodiment, the case where the UE selects RAN1 as the first path to initiate the session establishment process and sends a session establishment request message to AMF1 via RAN1 is taken as an example for introduction.

[0561] Step 1208: AMF2 allocates a path identifier (such as path identifier).

[0562] For the relevant description of AMF2 allocating the path, refer to Figure 6 step 614 therein.

[0563] In this embodiment, the case where AMF2 allocates path identifier 2 for the second path is taken as an example for illustration.

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

[0565] The information used to distinguish the second path can be one or more of location information, access type, access technology, registration type, RAN identifier, and AMF identifier. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell where the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, the ULI can be used to identify different paths. 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. Thus, the SMF can subsequently determine to send data to AMF2 on the second path corresponding to 5G according to path identifier 2.

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

[0567] In a possible implementation, the path identifier 2 and the information for differentiating the second path are sent through a policy request message. For example, 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.

[0568] Step 1211: Refer to Figure 7 the relevant descriptions in steps 717 - 719 in , which will not be elaborated here.

[0569] Step 1212: AMF2 sends the traffic splitting rule and the path identifier 2 to the UE through RAN2.

[0570] For relevant descriptions, refer to Figure 10 the relevant descriptions in step 1009 in , which will not be elaborated here.

[0571] Through the steps of method 1200, when the UE accesses the network through two paths of 3GPP access types, the AMF allocates path identifiers, the UE receives the traffic splitting rule containing the first path identifier from the first path, and receives the traffic splitting rule containing the second path identifier from the second path. Thus, both the UE and the network can distinguish the two different paths according to the path identifiers. Furthermore, the UE can transmit the service data through the path corresponding to the path identifier according to the traffic splitting rule corresponding to the service data, thereby improving the transmission efficiency.

[0572] As Figure 13 shown, a method 1300 applicable to this application is introduced. This method is applicable to the UE accessing the network through multiple paths of the same access type (for example, two paths of 3GPP access types). In method 1300, in the session establishment process, the UDM allocates path identifiers for the UE, the SMF generates traffic splitting rules according to the path identifiers, and the UE obtains the path identifiers and the traffic splitting rules. Through method 1300, the UE can determine the transmission path of the service data according to the path identifiers. This method includes the following steps:

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

[0574] The session establishment request message includes capability information. For relevant descriptions of the capability information, refer to Figure 6 step 601 in , which will not be elaborated here.

[0575] In a possible implementation, the session establishment request message is a PDU session establishment request (PDU Session Establishment Request) message. For the relevant description of the PDU session establishment request message, reference can be made to Figure 3 step 301 in

[0576] In this embodiment, it is introduced by taking the example that the UE selects RAN1 as the first path to initiate the session establishment process and sends a session establishment request message to AMF1 through RAN1.

[0577] Step 1302: AMF1 sends information for differentiating the first path to the SMF.

[0578] The information for differentiating the first path can be one or more of location information, access type, access technology type, registration type, RAN identifier, and AMF identifier. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell in which the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, different paths can be identified by the ULI. Exemplarily, the information for differentiating 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. Thus, the SMF can subsequently determine to send data to AMF1 on the first path corresponding to 6G according to the path identifier 1.

[0579] In a possible implementation, the information for differentiating the first path implicitly indicates that the UE supports multi-radio capabilities; or, it indicates that the UE supports multi-registration capabilities, or it indicates that the UE accesses the network through a multi-connection method. It should be noted that the name of the multi-radio capabilities can also be replaced by any one of the names of the extended dual connection or multi-connection in the above dual connection architecture.

[0580] In another possible implementation, AMF1 sends path identifier allocation information to the SMF, and the path identifier allocation information indicates that the UE supports multi-radio capabilities; or, it indicates that the UE supports multi-registration capabilities, or it indicates that the UE accesses the network through a multi-connection method.

[0581] In a possible implementation, AMF1 sends the information for differentiating the first path to the 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.

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

[0583] In a possible implementation, the information for differentiating the first path implicitly indicates that the UE supports multi-radio capabilities or indicates the allocation of a path identifier.

[0584] In another possible implementation, the SMF sends path identifier allocation information to the UDM, and the path identifier allocation information indicates the allocation of a path identifier.

[0585] Step 1304: The UDM allocates a path identifier (e.g., path identifier).

[0586] In a possible implementation, the UDM allocates a path identifier according to the information for differentiating the first path or the path identifier allocation information.

[0587] 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. When the subscription data of the UE indicates that the UE is allowed to access the network through dual connectivity, a path identifier is allocated. It can be understood that when the UDM determines according to the subscription data of the UE that the UE is not allowed to use dual connectivity to access the network, the UDM will not allocate a path identifier.

[0588] In a possible implementation, the UDM can store the information for differentiating the first path and path identifier 1, or the corresponding relationship between the information for differentiating the first path and path identifier 1, in the subscription data or context information corresponding to the UE.

[0589] In this embodiment, an example is given in which the UDM allocates path identifier 1 for the first path where the AMF1 is located.

[0590] Step 1305: The UDM sends path identifier 1 to the SMF.

[0591] Optionally, the UDM also sends the information for differentiating the first path to the SMF.

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

[0593] The policy request message includes a path identifier and information for differentiating paths. For relevant descriptions, refer to Figure 12 Step 1204 in, which will not be elaborated here.

[0594] Step 1307: Refer to Figure 7 The relevant descriptions in steps 708 - 711 in, which will not be elaborated here.

[0595] Step 1308: The AMF1 sends a traffic splitting rule and path identifier 1 to the UE through RAN1.

[0596] For related descriptions, refer to Figure 10 the relevant description of step 1007 in [reference], which will not be elaborated here.

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

[0598] The session establishment request message includes capability information. For the related description of the capability information, refer to Figure 6 step 601 in [reference], which will not be elaborated here.

[0599] In a possible implementation, the session establishment request message is a PDU session establishment request (PDU Session Establishment Request) message. For the related description of the PDU session establishment request message, refer to Figure 3 step 301 in [reference].

[0600] In this embodiment, the example of the UE selecting RAN2 as the first path to initiate the session establishment process and sending a session establishment request message to AMF2 via RAN2 is introduced.

[0601] Step 1310: AMF1 sends information for differentiating the second path to SMF.

[0602] The information for differentiating the second path can be one or more of location information, access type, access technology type, registration type, RAN identifier, AMF identifier. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell where the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, the ULI can be used to identify different paths.

[0603] In a possible implementation, the information for differentiating 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.

[0604] In another possible implementation, AMF1 sends path identifier allocation information to SMF, and the path identifier allocation 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.

[0605] In a possible implementation, AMF1 sends information for differentiating the second path to the 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.

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

[0607] In a possible implementation, the information for differentiating the second path implicitly indicates that the UE supports multi-radio capabilities or indicates the allocation of a path identifier.

[0608] In another possible implementation, the SMF sends path identifier allocation information to the UDM, and the path identifier allocation information indicates the allocation of a path identifier.

[0609] Step 1312: The UDM allocates a path identifier (such as a path identifier).

[0610] In a possible implementation, the UDM allocates a path identifier according to the information for differentiating the second path or the path identifier allocation information. For example, the UDM allocates different path identifiers for different paths of the same UE (for example, the SUPI of the UE on different paths is the same). Or the UDM allocates a globally unique identifier for each path, that is, the UDM does not distinguish between different paths of the same or different UEs when allocating 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. When the subscription data of the UE indicates that the UE is allowed to access the network through dual connectivity, a path identifier is allocated. It can be understood that when the UDM determines according to the subscription data of the UE that the UE is not allowed to use dual connectivity to access the network, the UDM will not allocate a path identifier.

[0611] In a possible implementation, the UDM can store the information for differentiating the second path and path identifier 2, or the corresponding relationship between the information for differentiating the second path and path identifier 2, in the subscription data or context information corresponding to the UE.

[0612] In this embodiment, an example is given in which the UDM allocates path identifier 2 for the second path where AMF2 is located.

[0613] Step 1313: The UDM sends path identifier 2 to the SMF.

[0614] Optionally, the UDM also sends the information for differentiating the second path to the SMF.

[0615] Step 1314 (optional): The SMF sends Path ID 2 and information for differentiating the second path to the PCF.

[0616] In a possible implementation, Path ID 2 and the information for differentiating the second path are sent through a policy request message. For example, 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.

[0617] Step 1315: Refer to Figure 7 the relevant descriptions in steps 717 - 719 in , which will not be elaborated here.

[0618] Step 1316: The AMF2 sends the traffic splitting rules and Path ID 2 to the UE through RAN2.

[0619] For relevant descriptions, refer to Figure 10 the relevant descriptions in step 1009 in , which will not be elaborated here.

[0620] Through the steps of method 1300, when the UE accesses the network through two paths of 3GPP access types, the UDM allocates path identifiers, the UE receives the traffic splitting rules containing the first path identifier from the first path, and the traffic splitting rules containing the second path identifier from the second path. Thus, both the UE and the network can differentiate the two different paths according to the path identifiers. Furthermore, the UE can transmit the service data through the path corresponding to the path identifier according to the traffic splitting rules corresponding to the service data, thereby improving the transmission efficiency.

[0621] As Figure 14 shown, a method 1400 applicable to this application is introduced. This method is applicable to the UE accessing the network through multiple paths of the same access type (for example, two paths of 3GPP access types). In method 1400, during the session establishment process, the SMF allocates path identifiers for the UE, the SMF generates traffic splitting rules according to the path identifiers, and the UE obtains the path identifiers and the traffic splitting rules. Through method 1400, the UE can determine the transmission path of the service data according to the path identifiers. This method includes the following steps:

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

[0623] The session establishment request message includes capability information. For relevant descriptions of the capability information, refer to Figure 6 step 601 in , which will not be elaborated here.

[0624] In a possible implementation, the session establishment request message is a PDU session establishment request (PDU Session Establishment Request) message. For the relevant description of the PDU session establishment request message, reference can be made to Figure 3 Step 301 in

[0625] In this embodiment, the UE selects RAN1 as the first path to initiate the session establishment process, and takes the example of sending a session establishment request message to AMF1 through RAN1 for introduction.

[0626] Step 1402: AMF1 sends information for differentiating the first path to the SMF.

[0627] The information for differentiating the first path can be one or more of location information, access type, access technology type, registration type, RAN identifier, and AMF identifier. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell where the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, the ULI can be used to identify different paths. Exemplarily, the information for differentiating 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. Thus, the SMF can subsequently determine to send data to AMF1 on the first path corresponding to 6G according to the path identifier 1.

[0628] In a possible implementation, the information for differentiating 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 a multi-connection method.

[0629] In another possible implementation, AMF1 sends path identifier allocation information to the SMF, and the path identifier allocation 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 a multi-connection method.

[0630] In a possible implementation, AMF1 sends the information for differentiating the first path to the 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.

[0631] Step 1403: The SMF allocates a path identifier (such as path identifier).

[0632] In a possible implementation, the SMF allocates a path identifier according to the information for differentiating the first path or the path identifier allocation information.

[0633] In this embodiment, an example is given where the SMF allocates the path identifier 1 for the first path where the AMF1 is located.

[0634] In a possible implementation, the SMF may store the information for differentiating the first path and the path identifier 1, or the corresponding relationship between the information for differentiating the first path and the path identifier 1, in the context information corresponding to the UE.

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

[0636] The policy request message includes the path identifier and the information for differentiating paths. For relevant descriptions, refer to Figure 12 Step 1204 in, which will not be elaborated here.

[0637] Step 1405: Refer to Figure 7 The relevant descriptions in steps 708 - 711 in, which will not be elaborated here.

[0638] Step 1406: The AMF1 sends the traffic splitting rule and the path identifier 1 to the UE through RAN1.

[0639] For relevant descriptions, refer to Figure 10 The relevant descriptions in step 1007 in, which will not be elaborated here.

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

[0641] The session establishment request message includes capability information. For relevant descriptions of the capability information, refer to Figure 6 Step 601 in, which will not be elaborated here.

[0642] In a possible implementation, the session establishment request message is a PDU session establishment request (PDU Session Establishment Request) message. For relevant descriptions of the PDU session establishment request message, reference can be made to Figure 3 Step 301 in.

[0643] In this embodiment, an example is given where the UE selects RAN2 as the first path to initiate the session establishment process and sends a session establishment request message to the AMF2 through RAN2.

[0644] Step 1408: The AMF1 sends the information for differentiating the second path to the SMF.

[0645] 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. Among them, the location information is, for example, ULI, and the ULI includes a cell identifier, and the cell identifier is the identifier of the cell to which the UE accesses RAN1. Since the cells accessed by the UE on different paths are different, the ULI can be used to identify different paths.

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

[0647] In another possible implementation, AMF1 sends path identifier allocation information to SMF, and the path identifier allocation 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.

[0648] In a possible implementation, AMF1 sends the information used to distinguish 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.

[0649] Step 1409: SMF allocates a path identifier (such as a path identifier).

[0650] In a possible implementation, SMF allocates a path identifier according to the information used to distinguish the second path or the path identifier allocation information. For example, SMF allocates different path identifiers for different paths of the same UE (for example, the SUPI of the UE on different paths is the same). Or SMF allocates a globally unique identifier for each path, that is, when SMF allocates a path identifier, it does not distinguish between different paths of the same or different UEs.

[0651] In this embodiment, an example is given in which SMF allocates path identifier 2 for the second path where AMF2 is located.

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

[0653] Step 1410 (optional): SMF sends path identifier 2 and the information used to distinguish the second path to PCF.

[0654] In a possible implementation, the path identifier 2 and the information for differentiating the second path are sent through a policy request message. For example, 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.

[0655] Step 1411: Refer to Figure 7 the relevant descriptions in steps 717 - 719 in , which will not be elaborated here.

[0656] Step 1412: AMF2 sends the traffic splitting rules and the path identifier 2 to the UE through RAN2.

[0657] For relevant descriptions, refer to Figure 10 the relevant descriptions in step 1009 in , which will not be elaborated here.

[0658] Through the steps of method 1400, when the UE accesses the network through two paths of 3GPP access types, the SMF allocates path identifiers. The UE receives the traffic splitting rules containing the first path identifier from the first path and the traffic splitting rules containing the second path identifier from the second path. Thus, both the UE and the network can distinguish the two different paths according to the path identifiers. Furthermore, the UE can transmit the service data through the path corresponding to the path identifier according to the traffic splitting rules corresponding to the service data, thereby improving the transmission efficiency.

[0659] Next, in combination with the attached Figure 15 , a method 1500 provided by an embodiment of the present application will be introduced. It should be noted that, taking Figure 15 as an example for introduction, this method is applicable to any one of the processes in the above Figures 6 - 14 . The communication device can be a terminal device (such as the UE 110 in Figure 1 ), or a chip (system) that can be disposed in the terminal device. That is to say, method 1500 can be executed by the terminal device or by the chip (system) in the terminal device.

[0660] As Figure 15 shown in the schematic diagram of the communication method process, the following steps can be included:

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

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

[0663] 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 the AMF. For the relevant description of obtaining the capability information from the subscription data, reference can be made to Figure 6 Step 608 in

[0664] In a possible implementation, the first network element is the AMF. For the relevant description of the communication device sending the capability information to the AMF, reference can be made to Figure 6 Steps 601 - Step 603 in

[0665] In a possible implementation, the AMF selects a session management network element that supports multi-connection according to the capability information; among them, the session management network element that supports multi-connection is a session management network element that supports generating a traffic splitting rule including a first path identifier. The session management network element that supports multi-connection can be understood as that this session management network element can identify new parameters, such as path identifiers, and support generating traffic splitting rules including path identifiers.

[0666] In another possible implementation, the first network element is the UDM. For the relevant description of the communication device sending the capability information to the UDM, reference can be made to Figure 8 Steps 801 - Step 805 in

[0667] In still another possible implementation, the first network element is the SMF. For the relevant description of the communication device sending the capability information to the SMF, reference can be made to Figure 14 Steps 1401 - Step 1402 in

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

[0669] In a possible implementation, the first network element is the AMF. For the relevant description of allocating the path identifier, reference can be made to Figure 6 Step 605 in

[0670] In a possible implementation, the AMF sends the first path identifier to the session management network element. For the relevant description, reference can be made to Figure 7 Step 703 in . For the relevant description of receiving the traffic splitting rule including the first path identifier from the session management network element, reference can be made to Figure 7 Step 711 in , and for the relevant description of sending the traffic splitting rule to the communication device, reference can be made to Figure 7 Steps 712 - 713 in

[0671] In another possible implementation, the first network element is the UDM. For the relevant description of allocating the path identifier, reference can be made to Figure 8 Step 806 in

[0672] In a possible implementation, the UDM sends a first path identifier and information for differentiating paths to a session management network element and / or a data storage network element. The information for differentiating paths is used by the session management network element to distinguish different paths. The relevant description of the UDM sending the first path identifier and the information for differentiating paths can be referred to Figure 9 in step 904 of Figure 8 The relevant description of the UDM sending the first path identifier and the information for differentiating paths to the data storage network element can be referred to

[0673] in step 817 of Figure 14

[0674] Figure 7 In a possible implementation, the SMF generates a traffic splitting rule including the first path identifier; and sends the traffic splitting rule to a communication device, where the traffic splitting rule is used by the communication device to determine a transmission path of a service flow. The relevant description can be referred to Figure 7 in step 710 of

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

[0676] In a possible implementation, the first network element is the AMF. The relevant description of the AMF sending the first path identifier to the communication device can be referred to Figure 6 in step 609 of Figure 10 or Figure 12 in step 1007 of

[0677] In another possible implementation, the first network element is the UDM. The relevant description of the UDM sending the first path identifier to the communication device can be referred to Figure 8 in steps 807 - 808 of Figure 11 or Figure 13 in steps 1106 - 1107 of

[0678] In yet another possible implementation, the first network element is the SMF. The relevant description of the SMF sending the first path identifier to the communication device can be referred to Figure 14 in steps 1405 - 1406 of

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

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

[0681] In a possible implementation, the communication device receives a traffic splitting rule including a first path identifier. For relevant descriptions, reference can be made to Figure 7 step 713 in Figure 10 step 1007 in Figure 11 step 1107 in Figure 12 1206 in Figure 13 1308 in Figure 14 1406 in

[0682] In a possible implementation, the traffic splitting 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 according to the first path identifier. For relevant descriptions, reference can be made to Figure 7 step 713 in

[0683] The communication device can first obtain the path identifier through the registration process, so as to be able to identify multiple different paths under the same access type of the current access. In addition, when the communication device establishes sessions through multiple different paths under the same access type, it can know through the traffic splitting rule including the path identifier which transmission path the service data should be transmitted through, and transmit the service data through the path corresponding to the path identifier, thereby improving the transmission efficiency.

[0684] The communication device can also obtain the path identifier when establishing sessions through multiple different paths under the same access type. Furthermore, it can know through the traffic splitting rule including the path identifier which transmission path the service data should be transmitted through, and transmit the service data through the path corresponding to the path identifier, thereby improving the transmission efficiency.

[0685] Next, in combination with the attached Figure 16 , a method 1600 provided by an embodiment of the present application is introduced. It should be noted that here Figure 16 is taken as an example for introduction, and this method is applicable to any one of the above Figures 6 - 15 processes.

[0686] As Figure 16The schematic flow diagram of the communication method described above may include the following steps:

[0687] Step 1601: The first network element obtains a first path identifier.

[0688] In a possible implementation, the first network element is an SMF. For the relevant description of the SMF obtaining the first path identifier, reference can be made to Figure 7 Step 703, Step 704 or Step 708 in Figure 12 Step 1203 in Figure 13 Step 1305 in Figure 14 Step 1403 in

[0689] Step 1602: The first network element generates a traffic splitting rule.

[0690] In a possible implementation, the first network element is an SMF. For the relevant description of the SMF generating a traffic splitting rule according to the first path identifier, reference can be made to Figure 7 Step 710 in

[0691] Step 1603: The first network element sends the traffic splitting rule to the second network element.

[0692] In a possible implementation, the second network element is a UPF. For the relevant description of the first network element sending the traffic splitting rule to the UPF, reference can be made to Figure 7 Step 710 in

[0693] In a possible implementation, the UPF can know through the traffic splitting rule containing the path identifier which transmission path the service data should pass through to transmit the downlink service data, and transmit the service data through the path corresponding to the path identifier, thereby improving the transmission efficiency.

[0694] As described above in conjunction with Figures 6 to 16 , the method-side embodiments of the communication method of the present application have been described in detail. Next, the apparatus-side embodiments of the present application will be described in conjunction with Figures 17 to 19 . It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, the parts not described in detail can be referred to the previous method embodiments.

[0695] Figure 17 is a schematic structural diagram of a communication apparatus 1000 provided by an embodiment of the present application. As Figure 17 shown, the apparatus 1000 may include a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 can communicate with the outside, and the processing unit 1020 is used for data processing. The transceiver unit 1010 may also be referred to as a communication interface or a transceiver unit.

[0696] In a possible design, the apparatus 1000 may implement the steps or processes corresponding to those performed by the first network element in the above method embodiments. Among them, the processing unit 1020 is configured to perform operations related to the processing of the first network element in the above method embodiments, and the transceiver unit 1010 is configured to perform operations related to the transceiver of the first network element in the above method embodiments.

[0697] In another possible design, the apparatus 1000 may implement the steps or processes corresponding to those performed by the communication device in the above method embodiments. Among them, the transceiver unit 1010 is configured to perform operations related to the transceiver of the communication device in the above method embodiments, and the processing unit 1020 is configured to perform operations related to the processing of the communication device in the above method embodiments.

[0698] It should be understood that the apparatus 1000 here is embodied in the form of functional units. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group of processors, etc.) for executing one or more software or firmware programs, and a memory, a combined logic circuit and / or other suitable components that support the described functions. In an alternative example, those skilled in the art can understand that the apparatus 1000 may specifically be the sending end in the above embodiments, and may be used to execute each process and / or step corresponding to the sending end in the above method embodiments. Or, the apparatus 2000 may specifically be the receiving end in the above embodiments, and may be used to execute each process and / or step corresponding to the receiving end in the above method embodiments. To avoid repetition, it will not be elaborated here.

[0699] The apparatus 1000 in the above various solutions has the function of implementing the corresponding steps performed by the sending end in the above method, or the apparatus 1000 in the above various solutions has the function of implementing the corresponding steps performed by the receiving end in the above method. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending 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, etc., can be replaced by a processor to respectively execute the transceiver operations and related processing operations in each method embodiment.

[0700] In addition, the above transceiver unit may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit. In an embodiment of the present application, the device 1000 may be the receiving end or the transmitting end in the foregoing embodiments, or may be a chip or a chip system, for example: a system on chip (SoC). Among them, the transceiver unit may be an input / output circuit or a communication interface. The processing unit is a processor, a microprocessor, or an integrated circuit integrated on the chip. This is not limited herein.

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

[0702] Optionally, the device 2000 may further include a memory 2030, and the memory 2030 communicates with the processor 2010 and the transceiver 2020 through 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.

[0703] In a possible implementation, the device 2000 is used to implement each process and step corresponding to the first network element in the foregoing method embodiments.

[0704] In another possible implementation, the device 2000 is used to implement each process and step corresponding to the communication device in the foregoing method embodiments.

[0705] It should be understood that the device 2000 may specifically be the transmitting end or the receiving end in the foregoing embodiments, or may be a chip or a chip system. Correspondingly, the transceiver 2020 may be the transceiver circuit of the chip, which is not limited herein. Specifically, the device 2000 may be used to execute each step and / or process corresponding to the transmitting end or the receiving end in the foregoing method embodiments.

[0706] Optionally, the memory 2030 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A part of the memory may further include a non-volatile random access memory. For example, the memory may also store information about the device type. The processor 2010 may be used to execute the instructions stored in the memory, and when the processor 2010 executes the instructions stored in the memory, the processor 2010 is used to execute each step and / or process of the foregoing method embodiments corresponding to the transmitting end or the receiving end.

[0707] In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor or the instructions in the form of software. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by the hardware processor, or executed and completed by the combination of the hardware and software modules in the processor. The software module can be located in the random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register and other mature storage media in the art. This storage media is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

[0708] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with the ability to process signals. In the implementation process, each step of the above method embodiments can be completed by the integrated logic circuit of the hardware in the processor or the instructions in the form of software. 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 devices, discrete gate or transistor logic devices, discrete hardware components. The processor in the embodiments of the present application can implement or execute each method, step and logic block diagram disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module can be located in the random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register and other mature storage media in the art. This storage media is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0709] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can 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 can 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 link 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 not be limited to these and any other suitable types of memory.

[0710] Figure 19 is a schematic structural diagram of a chip system 3000 provided by an embodiment of the present application. As Figure 19 shown, the chip system 3000 (or can also be referred to as a processing system) includes a logic circuit 3010 and an input / output interface 3020.

[0711] Among them, the logic circuit 3010 can be a processing circuit in the chip system 3000. The logic circuit 3010 can 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 embodiments of the present application. The input / output interface 3020 can be an input / output circuit in the chip system 3000, output the information processed by the chip system 3000, or input the data or signaling information to be processed into the chip system 3000 for processing.

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

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

[0714] The embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the methods performed by the communication device, the access and mobility management network element, and the radio access network device in the above method embodiments are stored.

[0715] An embodiment of the present application further provides a computer program product, including computer program code or instructions. When the computer program code or instructions run on a computer, the computer implements the methods executed by the communication device, the access and mobility management network element, and the radio access network device in the above method embodiments.

[0716] An embodiment of the present application further provides a communication system, including the aforementioned communication device and the first network element. Optionally, it may further include a RAN, a UDR, or a PCF.

[0717] For the explanations and beneficial effects of the relevant content in any of the above-provided devices, reference can be made to the corresponding method embodiments provided above, which will not be elaborated here. To facilitate the understanding of the above embodiments provided by the present application, the following points are explained:

[0718] 1) In the present application, without special instructions and logical conflicts, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0719] 2) In the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. In the text description of the present application, the character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (item) or multiple items (items). For example, at least one (item) of a, b, and c can represent: 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.

[0720] 3) In the present application, "first", "second", and various numerical numbers (for example, #1, #2, etc.) are used for distinction for convenience of description, and do not limit the scope of the embodiments of the present application. For example, to distinguish different messages, etc., rather than for describing a specific order or sequence. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe the solutions other than the embodiments of the present application.

[0721] 4) In this application, descriptions such as "when...", "in the case of...", and "if" all refer to the device making corresponding processing under certain objective circumstances, which do not limit time, and do not require the device to have a judgment action during implementation, nor does it mean there are other limitations.

[0722] 5) In this application, "for indicating" may include for direct indication and for indirect indication. When it is described that a certain indication information is for indicating A, it may include that the indication information directly indicates A or indirectly indicates A, rather than meaning that A must be carried in the indication information.

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

[0724] The "indication information" in the embodiments of this application can be explicit indication, that is, directly indicated by signaling, or obtained by combining other rules or other parameters or by derivation according to the parameters indicated by the signaling. It can also be implicit indication, that is, obtained according to rules or relationships, or according to other parameters, or by derivation. This application does not make specific limitations on this.

[0725] 6) In this application, "protocol" can refer to standard protocols in the communication field. For example, it can include 5G protocols, NR protocols, and related protocols applied to future communication systems. This application does not make limitations on this. "Predefined" can include predefined. For example, protocol definition. "Preconfigured" can be implemented by pre-saving corresponding codes, tables, or other ways that can be used to indicate relevant information in the device. This application does not limit its specific implementation method.

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

[0727] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed in this article can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0728] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0729] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. 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 displayed or discussed coupling, direct coupling, or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in an electrical, mechanical, or other form.

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

[0731] In addition, in each embodiment of the present application, the functional units can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0732] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or a part of this 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 to enable a computer device to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: USB flash drives, mobile hard disks, read-only memories, random access memories, magnetic disks, or optical discs and other various media that can store program codes.

[0733] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application and should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope 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, and 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, characterized in that, 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 traffic flow, and the transmission path is one or more paths among the at least two paths.

4. The method according to claim 3, characterized in that, 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; wherein, 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, wherein 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 to 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; wherein, 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 the access node to which the communication device accesses the network; the access technology type indicates the access technology type by which the communication device accesses the network through the first path; the registration type indicates the registration type by which the communication device registers to the network through the first path.

11. The method according to claim 1 or 2, wherein 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 the 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 the transmission path of the service flow.

19. The method according to claim 18, wherein The traffic splitting rule includes the 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 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: The 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 service 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 the service flow corresponding to the service flow information is transmitted on the first path according to the first path identifier; and / or determines that the 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, and 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: 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 radio 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 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 the 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 executing 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 executing 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