Communication method, and device

Abstract

The present application relates to a communication method, device, a computer-readable storage medium, a computer program product, and a computer program. The method comprises: a terminal sending a first request to a first core network device, wherein the first request is used for establishing or modifying a first session corresponding to a first user equipment (UE), the first request carries an identifier of a second session corresponding to a second UE, the identifier of the second session is used by the first core network device to select a second core network device corresponding to the second session, and the terminal comprises the first UE and the second UE.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method, device, computer-readable storage medium, computer program product, and computer program. Background Art

[0002] Related technologies stipulate that a terminal can have two UEs (User Equipment), both belonging to the same HPLMN (Home Public Land Mobile Network) and the same user. The Release 19 Multi-Access Steering, Switching, and Splitting (MASSS) project proposes that a terminal can use two UEs to access the same or different PLMNs. However, in this scenario, ensuring that the network controls data for multiple sessions of multiple UEs belonging to the same terminal and implementing MASSS becomes a challenge.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a communication method, device, computer-readable storage medium, computer program product, and computer program.

[0005] This embodiment of the present application provides a communication method, including:

[0006] The terminal sends a first request to the first core network device, wherein the first request is used to establish or modify a first session corresponding to the first user equipment UE, the first request carries an identifier of a second session corresponding to the second UE, and the identifier of the second session is used by the first core network device to select the second core network device corresponding to the second session. The terminal includes the first UE and the second UE.

[0007] An embodiment of the present application provides a communication method, including:

[0008] A first core network device receives a first request sent by a terminal, wherein the first request is used to establish or modify a first session corresponding to a first user equipment UE, the first request carries an identifier of a second session corresponding to a second UE, the identifier of the second session is used to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

[0009] An embodiment of the present application provides a terminal, including:

[0010] A first communication unit is used to send a first request to a first core network device, wherein the first request is used to establish or modify a first session corresponding to a first user equipment UE, the first request carries an identifier of a second session corresponding to a second UE, the identifier of the second session is used by the first core network device to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

[0011] An embodiment of the present application provides a first core network device, including:

[0012] A second communication unit is used to receive a first request sent by a terminal, wherein the first request is used to establish or modify a first session corresponding to a first user equipment UE, the first request carries an identifier of a second session corresponding to a second UE, the identifier of the second session is used to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

[0013] An embodiment of the present application provides a terminal, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and run the computer program stored in the memory, so that the terminal executes the above method.

[0014] An embodiment of the present application provides a first core network device, comprising: a transceiver, a processor, and a memory. The memory is configured to store a computer program, the transceiver is configured to communicate with other devices, and the processor is configured to call and execute the computer program stored in the memory, so that the first core network device executes the above method.

[0015] The embodiment of the present application provides a chip for implementing the above method. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above method.

[0016] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above method when the computer program is executed by the device.

[0017] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method.

[0018] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method.

[0019] By adopting the solution provided by this embodiment, when there is a second UE in the terminal that has completed the establishment of a second session, when the terminal requests the first core network device to establish or modify the first session corresponding to the first UE, by carrying the identifier of the established second session in the corresponding request, the first core network device can select the second core network device corresponding to the second session, and then the network side can associate the multiple sessions established by the multiple UEs of the terminal with the same second core network device, thereby ensuring that the business data of the multiple sessions can be aggregated to the same core network device side, so as to ensure that the network side can realize MASSS of multiple sessions of the multiple UEs of the control terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0021] Figure 2 is a schematic diagram of the 5G network system architecture.

[0022] FIG3 is a schematic diagram of a scenario of a multi-access (MA)-PDU.

[0023] FIG4 and FIG5 are schematic diagrams of two scenarios of accessing networks through two 3GPPs in this application.

[0024] FIG6 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0025] FIG7 is a schematic flowchart of a communication method according to another embodiment of the present application.

[0026] FIG8 and FIG9 are two exemplary flow charts of a communication method according to an embodiment of the present application.

[0027] FIG10 is a schematic block diagram of a terminal according to an embodiment of the present application.

[0028] FIG11 is a schematic block diagram of a first core network device according to an embodiment of the present application.

[0029] FIG12 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0030] FIG13 is a schematic block diagram of a chip according to an embodiment of the present application.

[0031] FIG14 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0033] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), Fifth Generation (5G) system or other communication systems.

[0034] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, and the embodiments of the present application may also be applied to these communication systems. In one possible implementation, the communication system in the embodiment of the present application may be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario. In one possible implementation, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to an authorized spectrum, where the authorized spectrum may also be considered a non-shared spectrum.

[0035] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, where the terminal device may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next-generation communication system such as a NR network, or a terminal device in a future-evolved Public Land Mobile Network (PLMN) network, etc. In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (such as an airplane, a balloon, and a satellite, etc.). In an embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc. As an example and not a limitation, in an embodiment of the present application, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by applying wearable technology to intelligently design everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into clothing or accessories. Wearable devices are more than just hardware devices; they also enable powerful functionality through software support, data interaction, and cloud-based interaction.In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0036] In an embodiment of the present application, a network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, a base station (BTS) in a GSM or CDMA, a base station (NodeB, NB) in a WCDMA, an evolved base station (eNB or eNodeB) in an LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network. As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water. In an embodiment of the present application, the network device may provide services for a cell, and the terminal device may communicate with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0037] Figure 1 exemplarily shows a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In a possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application. In a possible implementation, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application. Among them, the network device may include an access network device and a core network network element. That is, the wireless communication system also includes multiple core networks for communicating with the access network device. The access network equipment may be an evolutionary base station (evolutional node B, which may be referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system. It should be understood that the equipment with communication functions in the network / system in the embodiment of the present application may be referred to as communication equipment. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiment of the present application, which will not be repeated here; the communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited in the embodiment of the present application.

[0038] To facilitate understanding of the embodiments of the present application, the following briefly describes the basic processes and basic concepts involved in the embodiments of the present application. It should be understood that the basic processes and basic concepts introduced below do not limit the embodiments of the present application.

[0039] The 5G network system architecture is shown in Figure 2, which includes: NSSF (Network Slice Selection Function) is mainly used to manage network slice related information, such as selecting network slices for terminal devices; AUSF (Authentication Server Function) is used to complete the identity authentication function of user access; UDM (Unified Data Management) is used to manage and store contract data and authentication data; AMF (Access and Mobility Management Function) is used to complete mobility management, security anchor and secure UE policy management, etc. In addition to managing the mobility of UE, AMF is also responsible for forwarding session management related messages between UE and SMF; SMF (Session Management Function) is used to complete session management, UE IP address allocation and management, etc.; PCF (Policy Control Function) is responsible for formulating policies related to UE mobility management, session management, billing, etc.; AF (Application Function) is used for external application servers; UPF (User Plane Function) is used to manage and store user data and authentication data; The 5GC (5G Core Network) is used for complex user plane processing, such as forwarding traffic between the radio access network and the internet, reporting traffic usage, and implementing QoS (Quality of Service) policies. The DN (Data Network) is the external data network of the 5GC (such as the internet). Data is transmitted between the various nodes of the 5GC (5G Core Network), between the user equipment (UE) and 5GC nodes, between the UE and the Radio Access Network ((R)AN, Radio Access Network), and between the RAN and 5GC nodes through corresponding interfaces. For example, as shown in Figure 2: Data is transmitted between the AMF and NSSF in the 5GC via interface N22; the AMF transmits data with the SMF via interface N11; the AMF transmits data with the AUSF via N12; and the AMF transmits data with the UDM via interface N8. Data is transmitted between the SMF and the UPF via interface N4. The UPF transmits data with the external data network via interface N6 and with the AN via interface N3. The UE establishes an access layer connection with the (R)AN through the Uu interface, exchanges access layer messages and wireless data transmission, and establishes a non-access layer (NAS) connection with the AMF through the N1 interface, exchanges NAS messages.Data is transmitted between the RAN and AMF via the N2 interface, and between the RAN and UPF via the N3 interface. It should be understood that the above description only describes the interfaces between some nodes, and the other interfaces between other 5GC nodes in Figure 2 are not detailed one by one. In Figure 2, except for the UE, (R)AN, and DN, all other nodes are core network nodes; core network nodes can be further divided into user plane nodes (i.e., UPF in Figure 2) and control plane nodes (i.e., other core network nodes in the core network except UPF).

[0040] The current 3GPP (3rd Generation Partnership Project) system supports a multiple access (MA)-PDU ​​scenario (or session mode) that combines 3GPP access and non-3GPP access. In the multiple access (MA)-PDU ​​scenario shown in Figure 3, the UE can access the core network (which can be the core network of one or two PLMNs) simultaneously through 3GPP access and non-3GPP access, and realize the transmission of different data packets through 3GPP access or non-3GPP access. Specifically, the multi-access (MA) PDU scenario shown in Figure 3 includes: the UE connects to the UPF through the N3 interface through 3GPP access, the UPF connects to the UPF (PSA (Protocol Data Unit Session Anchor)) through the N9 interface, and finally the UPF (PSA) is connected to the server host through the N6 interface, so that the UE can transmit the PDU session through a 3GPP connection; the UE connects to the N3IWF (Non-3GPP Inter Working Function) through non-3GPP access, the N3IWF connects to the UPF through the N3 interface, the UPF connects to the UPF (PSA) through the N9 interface, and finally the UPF (PSA) is connected to the server host through the N6 interface, so that the UE can transmit the PDU (linked) session through a non-3GPP connection.

[0041] In the research content of 3GPP Release 19, a UE can connect to the same or different PLMNs using two 3GPP access technologies. For example: NR+PLMN 1–LTE+PLMN 2, NR+PLMN 1–Satellite+PLMN 2.

[0042] In some actual use cases, since there are many 3GPP access types, in some cases it is necessary to consider two UEs in the same device (or the same terminal) accessing the network through different 3GPP types for data transmission. Here, the same UE accessing the network through multiple different 3GPP types for data transmission can be divided into multiple granularities and combined to realize multiple 3GPP access scenarios, for example, it can include: a single PLMN (Public Land Mobile Network), multiple PLMNs; PLMN+SNPN (Stand-alone Non-Public Network); NR access+satellite access; satellite high orbit access+satellite medium orbit access+satellite low orbit access, etc. It should be understood that the above is only an exemplary description of multiple granularities and the combination of various granularities. The actual processing may include but is not limited to the multiple granularities exemplified above, and include but is not limited to the combination of different granularities exemplified above.

[0043] Furthermore, for the above different granularities and their combinations, two examples of multi-3GPP access scenarios are given:

[0044] Scenario 1, single PLMN, terrestrial + satellite access. This scenario is shown in Figure 4. NTN (Non-Terrestrial Networks) (i.e., low-orbit satellites and synchronous satellites shown in Figure 4) are used to expand the capacity / throughput of TN (Terrestrial Networks) (i.e., 5G Terrestrial Access shown in Figure 4), and vice versa. In this scenario, the terminal can be temporarily covered by dual radio access technologies (RATs). For example, the terminal is in the same carrier (train / cruise ship / airplane), and the carrier makes stopovers at positions 1 and 2 to 5 shown in Figure 4. Then, in at least one of positions 1 to 5, the terminal may be in dual RAT coverage, and the multi-3GPP access scenario provided by scenario 1 can be used for communication.

[0045] Scenario 2, dual PLMN or PLMN+SNPN. Figure 5 illustrates an exemplary scenario of local dual 3GPP connection. For example, UE-A and UE-B in Figure 5 are in a stadium, and UE-B shown in Figure 5 is only connected to PLMN-B CN (anchor point) through 3GPP access 1 (PLMN-B RAN); UE-A shown in Figure 5 can use local SNPN (i.e., 3GPP access 2 (via SNPN RAN) shown in Figure 5), and PLMN-B RAT (i.e., 3GPP access 1 (PLMN-B RAN) shown in Figure 5) to obtain additional PLMN-B capacity, and vice versa; in this way, UE-A can access PLMN-B CN (anchor point) through 3GPP access 1 (PLMN-B RAN) and 3GPP access 2 (via SNPN RAN), and after PLMN-B CN (anchor point), the data of UE-A's two 3GPP accesses can be aggregated to obtain UE-A aggregated data (Aggregated Data). Figure 5 is only an example. UE-A can establish two 3GPP connections temporarily or on demand. The scenario shown in Figure 5 can also be replaced with other similar scenarios, such as campuses, enterprises, factories, etc., which are not exhaustive or limited here.

[0046] The above two scenarios are only exemplary. In addition to the above two scenarios, NR+LTE scenarios, dual-satellite access scenarios, etc. can also be possible multi-3GPP access scenarios, which are not exhaustive here.

[0047] From the above description, it can be seen that research has begun on a terminal accessing the network through multiple 3GPP access types. Furthermore, it is stipulated in the relevant technology that a terminal has two UEs, and the two UEs belong to the same HPLMN and belong to the same user. In addition, the data transmission of a service can only use one access at a time point, and two accesses transmit data of different services at the same time. In the R19 Multi Access Steering, Switching, Splitting (MASSS) topic, a research direction is proposed in which a terminal uses two UEs to access the same or different PLMNs. However, in such a processing scenario, the service data of multiple PDU sessions of multiple UEs of a terminal may not be able to be aggregated in the 3GPP network, and then the network may not be able to control the data of multiple PDU sessions of multiple UEs of a terminal to implement MASSS.

[0048] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated before and after are in an "or" relationship. It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. In the description of the embodiments of this application, the term "corresponding" can mean that there is a direct or indirect correspondence between the two, or it can mean that there is an association relationship between the two, or it can mean a relationship between indication and indication, configuration and configuration, etc.

[0049] Figure 6 is a schematic flow chart of a communication method according to an embodiment of the present application. The method includes at least part of the following contents.

[0050] S610. The terminal sends a first request to the first core network device, wherein the first request is used to establish or modify a first session corresponding to the first user equipment UE, the first request carries an identifier of a second session corresponding to the second UE, the identifier of the second session is used by the first core network device to select the second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

[0051] Figure 7 is a schematic flow chart of a communication method according to another embodiment of the present application. The method includes at least part of the following contents.

[0052] S710. The first core network device receives a first request sent by a terminal, wherein the first request is used to establish or modify a first session corresponding to a first user equipment UE, the first request carries an identifier of a second session corresponding to a second UE, the identifier of the second session is used to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

[0053] Here, the terminal may include at least two UEs.

[0054] Different UEs in the at least two UEs of the terminal correspond to different identifiers, and the identifier of each UE may include at least one of a globally unique temporary UE identifier (GUTI) of the UE and a subscription permanent identifier (SUPI) of the UE. The identifier of each UE may also be represented as an ID of each UE.

[0055] In one example, a terminal may be provided with or include at least two communication modules, that is, the at least two UEs included in the terminal refer to at least two communication modules in the terminal or terminal device, that is, different communication modules in the at least two communication modules provided with or included in a terminal are different UEs, and different UEs correspond to different SUPIs. In another example, a terminal may be provided with or include at least two communication modules, and different communication modules in the at least two communication modules may be provided with or configured with or installed with different SIM (Subscriber Identity Module) cards, and different UEs in the at least two UEs included in the terminal are different communication modules in which different SIM cards are provided in the terminal or terminal device; in other words, different SIM cards in the terminal belong to different communication modules, and different communication modules are different UEs, that is, different SIM cards correspond to or belong to different UEs, and different SIM cards correspond to different SUPIs, that is, different UEs correspond to different SUPIs.

[0056] It should be noted that the UE in a terminal involved in the embodiments of the present application can be replaced or described as a communication module or a SIM card. For example, the first UE involved in the embodiments of the present application can be replaced with a first communication module, and the second UE involved in the embodiments of the present application can be replaced with a second communication module; or the first UE involved in the embodiments of the present application can be replaced with a first SIM card, and the second UE involved in the embodiments of the present application can be replaced with a second SIM card.

[0057] In an embodiment of the present application, the second UE may refer to a UE in the terminal that has completed the establishment or modification of its corresponding session before the terminal sends the first request to the first core network device; accordingly, the second session refers to a session that the second UE in the terminal has completed the establishment or modification of. The first UE refers to a UE in the terminal that has not established or modified its corresponding session and currently requests to establish or modify its corresponding session by sending a first request; the first session refers to the session that the first UE in the terminal currently requests to establish or modify. The second session is completed earlier than the first session.

[0058] It should be noted that the sessions involved in the embodiments of the present application all refer to PDU sessions (Packet Data Unit Session, PDU Session), which will not be explained again below.

[0059] In one example, there are two UEs in a terminal. Before the terminal sends a first request to the first core network device, only one UE has completed establishing or modifying a session. In this case, this UE is the second UE, and the session corresponding to the second UE is the second session. The other UE in the terminal other than the second UE is the first UE, and the session requested to be established or modified by the first UE is the first session. In this example, the terminal may include only the first UE and the second UE.

[0060] In one example, there are three or more UEs in the terminal.

[0061] In this example, the second UE may refer to: the UE that completes the establishment or modification of its corresponding session earliest among three or more UEs before the terminal sends the first request to the first core network device; or, the second UE may refer to: any one of the three or more UEs that completes the establishment or modification of its corresponding session before the terminal sends the first request to the first core network device. The session corresponding to the second UE is the second session. The first UE refers to: a UE in the terminal that has not established or modified its corresponding session and currently requests to establish or modify its corresponding session by sending the first request. The session requested to be established or modified by the first UE is the first session.

[0062] In this example, the terminal may include a first UE, a second UE, and may also include more other UEs. There is no limitation on the number of other UEs or whether the other UEs have completed the establishment or modification of the corresponding session.

[0063] It should be noted that the relevant meanings of the first UE and the second UE, the first session and the second session in the embodiments of the present application are the same as those in the above examples, so they will not be explained again.

[0064] The first core network device may be a first AMF. The first AMF is the AMF corresponding to the first UE of the terminal. It should be noted that the AMFs corresponding to the first UE and the second UE, respectively, may be the same or different; the AMFs corresponding to the first UE and the second UE, respectively, may be determined during the registration process of the first UE and the second UE, respectively, or in other processes. This embodiment does not limit the method for determining the AMF corresponding to the first UE and the AMF corresponding to the second UE.

[0065] In some possible implementations, the terminal sending the first request to the first core network device may be: a first UE of the terminal sending the first request to the first core network device.

[0066] The first request may be carried by a first UL (Uplink) NAS (Non-access stratum) message. Exemplarily, the first uplink NAS message may be encapsulated in a first UL NAS Transfer message or signaling and transmitted.

[0067] The first request may carry one of the following: a first PDU session establishment request (PDU Session Establish Request) or a first PDU session modification request (PDU Session Modification Request). Wherein, if the first request includes a first PDU session establishment request, the first request is used to establish the first session corresponding to the first UE; if the first request includes a first PDU session modification request, the first request is used to modify the first session corresponding to the first UE.

[0068] The first request carries an identifier of a second session corresponding to the second UE. The manner in which the first UE of the terminal obtains the identifier of the second session may include: when the first UE of the terminal is triggered to establish or modify a first session that can be used for multi-access steering, switching, and splitting (MASSS), the first UE of the terminal obtains the identifier of the second session corresponding to the second UE from the second UE of the terminal.

[0069] Here, the method of triggering the first UE of the terminal to establish a session for MASSS can be any one of the following: the first UE of the terminal is triggered by the application layer to establish or modify the first session for MASSS; the terminal itself triggers the first UE to establish or modify the first session for MASSS; the second UE of the terminal triggers the first UE to establish or modify the first session for MASSS, and so on.

[0070] The relevant descriptions about the second UE and its corresponding second session are the same as those in the above embodiment and will not be repeated here.

[0071] Optionally, the first request further carries a first indication, where the first indication is used to indicate that the first session is used for MASSS.

[0072] The first indication may be referred to as a first MASSS indication. The first session being used for MASSS may mean that the first session may be used to perform at least one processing such as redirection, switching, or splitting between one or more sessions established with one or more other UEs of the terminal. In other words, through the first indication, the first core network device may determine that the first session currently requested to be established or modified by the first UE of the terminal can be used to perform at least one processing such as redirection, switching, or splitting between sessions established with other UEs of the terminal that are also used for MASSS.

[0073] Optionally, the first request may also carry an identifier of the second UE. The previous embodiment has explained that the identifier of any UE may include the GUTI of the UE and / or the SUPI of the UE. Specifically, the first request also carries at least one of the following: the GUTI of the second UE, the SUPI of the second UE.

[0074] The manner in which the first UE of the terminal obtains the identifier of the second UE may include: when the first UE of the terminal is triggered to establish or modify a first session that can be used for MASSS, the first UE of the terminal obtains the identifier of the second UE from the second UE of the terminal.

[0075] It should be noted that, when the terminal includes two UEs, the first request may not carry the identifier of the second UE (that is, the first request does not carry the SUPI of the second UE and the GUPI of the second UE), or the first request may carry the identifier of the second UE. When the terminal includes three or more UEs, the first request carries the identifier of the second UE, that is, the first request carries at least one of the GUTI of the second UE and the SUPI of the second UE.

[0076] Optionally, the first request also carries at least one of the following: an identifier of the first session; a data network name (DNN) corresponding to the first session; and single-network slice selection assistance information (S-NSSAI) corresponding to the first session.

[0077] The present embodiment does not limit the manner in which the DNN corresponding to the first session and the S-NSSAI corresponding to the first session are determined or generated. Whether the DNN corresponding to the first session is the same as or different from the DNN corresponding to the second session, and whether the S-NSSAI corresponding to the first session is the same as or different from the S-NSSAI corresponding to the second session, are all within the scope of protection of this embodiment.

[0078] The identifier of the first session and the identifier of the second session may be the same or different.

[0079] In one case, the identifier of the first session is the same as the identifier of the second session. In this case, the first UE of the terminal may directly use the identifier of the second session as the identifier of the first session after obtaining the identifier of the second session. In this case, the first request may or may not carry the identifier of the first session.

[0080] In another case, the identifier of the first session is different from the identifier of the second session. In the case where the first request carries the identifier of the first session, the identifier of the first session may be generated by the first UE of the terminal.

[0081] That is, the first request sent by the first UE of the terminal must include the identifier of the second session corresponding to the second UE; it may also include any one of a first PDU session establishment request and a first PDU session modification request. Optionally, the first request may also include at least one of the following: a first indication, the GUTI of the second UE, the SUPI of the second UE, the identifier of the first session, the DNN corresponding to the first session, and the S-NSSAI corresponding to the first session.

[0082] In some possible implementations, the first core network device receiving the first request sent by the terminal may be: the first core network device receiving the first request sent by the first UE of the terminal. After the first core network device receives the first request sent by the terminal, the first core network device further includes: the first core network device obtaining the identifier of the second core network device based on the identifier of the second session.

[0083] In some embodiments, the first core network device obtains the identifier of the second core network device based on the identifier of the second session, including: when the first core network device determines that the session context of the second session is locally stored based on the identifier of the second session and the SUPI of the second UE, the first core network device obtains the identifier of the second core network device from the session context of the second session.

[0084] The first core network device is the first AMF; in this embodiment, the first UE and the second UE of the terminal correspond to the same AMF, that is, the first UE and the second UE both correspond to the first core network device, namely the first AMF.

[0085] When the first core network device determines that the session context of the second session is stored locally based on the identifier of the second session and the SUPI of the second UE, the first core network device obtains the identifier of the second core network device from the session context of the second session. Specifically, it may include: the first core network device extracts the identifier of the second session from the first request; the first core network device obtains the SUPI of the second UE; the first core network device searches locally for whether the session context of the second session is stored based on the identifier of the second session and the SUPI of the second UE; if the first core network device determines that the session context of the second session is stored locally, the identifier of the second core network device is obtained from the session context of the second session.

[0086] Among them, the second core network device can be SMF; the identification of the second core network device can include at least one of the following: SMF ID, SMF address; the address of the SMF can include at least one of the SMF network address, SMF operator internal address, among which the SMF network address can include at least one of the following: SMF IP (Internet Protocol) address, SMF MAC (Media Access Control) address.

[0087] In one embodiment, the first request further carries at least one of the following: the GUTI of the second UE, the SUPI of the second UE.

[0088] This embodiment may not limit the number of UEs included in the terminal. The number of UEs included in the terminal is greater than or equal to 2 and is within the protection scope of this embodiment. That is to say, this embodiment is applicable to scenarios where the terminal may include only the first UE and the second UE, and is also applicable to scenarios where the terminal includes the first UE, the second UE, and more UEs in addition to the first UE and the second UE.

[0089] In one example, the first request may carry the SUPI of the second UE. In this example, the first request may or may not carry the GUTI of the second UE, which is not limited in this example. Accordingly, when the first request carries the SUPI of the second UE, the first core network device obtaining the SUPI of the second UE may refer to: the first core network device obtaining the SUPI of the second UE from the first request.

[0090] In one example, when the first request carries the GUTI of the second UE, the SUPI of the second UE is determined based on the GUTI of the second UE. In this example, the first request may carry only the GUTI of the second UE; accordingly, the first core network device obtaining the SUPI of the second UE may mean that the first core network device obtains the GUTI of the second UE from the first request and obtains the SUPI of the second UE based on the GUTI of the second UE.

[0091] In this embodiment, since the first request can carry the GUTI and / or SUPI of the second UE, the first core network device can directly obtain or determine the SUPI of the second UE; and then, in combination with the identifier of the second session and the SUPI of the second UE, search among all locally stored contexts to see whether there is a session context of the second session corresponding to the identifier of the second session and the SUPI of the second UE; after finding the session context of the second session, the identifier of the second core network device is directly obtained from the session context of the second session.

[0092] In one embodiment, the first request may not carry the identifier of the second UE, that is, the first request carries neither the GUTI of the second UE nor the SUPI of the second UE. After the first core network device receives the first request sent by the terminal, the method further includes: the first core network device obtains the SUPI of the second UE from a fourth core network device based on the identifier of the first UE.

[0093] This embodiment is applicable to a scenario where the terminal includes two UEs.

[0094] Specifically, the first core network device obtaining the SUPI of the second UE from the fourth core network device based on the identifier of the first UE may include: when the first request does not carry the GUTI of the second UE and does not carry the SUPI of the second UE, the first core network device determines that the first session is used for MASSS and / or determines that the first UE of the terminal supports MASSS based on the first indication carried in the first request; the first core network device obtains the SUPI of the second UE from the fourth core network device based on the identifier of the first UE. The fourth core network device may be a UDM. The identifier of the first UE may include the SUPI of the first UE and / or the GUTI of the first UE.

[0095] The first core network device obtains the SUPI of the second UE from the fourth core network device based on the identifier of the first UE, which can be: the first core network device sends the identifier of the first UE to the fourth core network device, and receives the SUPI of the second UE sent by the fourth core network device. Correspondingly, the processing of the fourth core network device may include: the fourth core network device receives the identifier of the first UE from the first core network device, locally searches for the SUPI of another UE associated with the first UE (such as belonging to the same user or the same terminal as the first UE) based on the identifier of the first UE, and sends the SUPI of the other UE as the SUPI of the second UE to the first core network device.

[0096] In some embodiments, the first core network device obtains the identifier of the second core network device based on the identifier of the second session, including: the first core network device sends first information to the fourth core network device, wherein the first information includes at least one of the following: the identifier of the second session, the SUPI of the second UE, and the identifier of the first UE; the first core network device receives the identifier of the second core network device sent by the fourth core network device.

[0097] In this embodiment, the first UE and the second UE of the terminal correspond to different AMFs. The first core network device, that is, the first AMF, is the AMF corresponding to the first UE of the terminal, and the second UE of the terminal can correspond to the third core network device. The third core network device can be the second AMF, and the second AMF is different from the first AMF.

[0098] In one embodiment, the first information may include an identifier of the second session and a SUPI of the second UE.

[0099] The first core network device sends first information to the fourth core network device, and the first core network device receives the identifier of the second core network device sent by the fourth core network device, which may include: the first core network device sends first information to the fourth core network device, wherein the first information includes the identifier of the second session and the SUPI of the second UE; the first core network device receives the identifier of the second core network device sent by the fourth core network device.

[0100] Specifically, the first core network device sends the first information to the fourth core network device, and the first core network device receives the identifier of the second core network device sent by the fourth core network device, which may include: when the first core network device determines that the session context of the second session is not stored locally based on the identifier of the second session and the SUPI of the second UE, the first core network device sends the first information including the identifier of the second session and the SUPI of the second UE to the fourth core network device; the first core network device receives the identifier of the second core network device sent by the fourth core network device.

[0101] The processing by which the first core network device determines whether the session context of the second session is stored locally based on the identifier of the second session and the SUPI of the second UE may include: the first core network device extracts the identifier of the second session from the first request; the first core network device obtains the SUPI of the second UE; the first core network device searches locally for whether the session context of the second session is stored based on the identifier of the second session and the SUPI of the second UE.

[0102] Here, the description of the identifier of the second core network device is the same as that in the previous embodiment and will not be repeated.

[0103] In this embodiment, the first request may carry at least one of the following: a globally unique temporary UE identifier (GUTI) of the second UE and a SUPI of the second UE; or the first request may not carry the GUTI of the second UE and the SUPI of the second UE. In either case, the process for the first core network device to obtain the SUPI of the second UE is the same as in the previous embodiment and is not repeated here.

[0104] Optionally, the first information only includes the identifier of the second session and the SUPI of the second UE. That is, the first request may also carry a first indication, but the first information does not include the first indication.

[0105] The processing of the fourth core network device may include: the fourth core network device receives the first information from the first core network device; the fourth core network device searches for the locally stored session context of the second session based on the identifier of the second session included in the first information and the SUPI of the second UE; the fourth core network device obtains the identifier of the second core network device from the session context of the second session; the fourth core network device sends the identifier of the second core network device to the first core network device.

[0106] Optionally, the first request also carries a first indication; the first information includes: an identifier of the second session, a SUPI of the second UE, and the first information also includes the first indication.

[0107] The processing of the fourth core network device may include: the fourth core network device receives the first information from the first core network device; the fourth core network device determines that the first session is used for MASSS based on the first indication included in the first information; the fourth core network device searches for the locally stored session context of the second session based on the identifier of the second session in the first information and the SUPI of the second UE; the fourth core network device obtains the identifier of the second core network device from the session context of the second session; the fourth core network device sends the identifier of the second core network device to the first core network device.

[0108] In one embodiment, the first information may include an identifier of the second session and an identifier of the first UE. In this embodiment, the first request may not carry the identifier of the second UE, that is, the first request does not carry the SUPI of the second UE nor the GUTI of the second UE. This embodiment is particularly applicable to scenarios where the terminal includes only two UEs.

[0109] Optionally, the first information only includes the identifier of the second session and the identifier of the first UE. That is, the first request may also carry a first indication, but the first information does not include the first indication.

[0110] The first core network device sends first information to the fourth core network device, and the first core network device receives the identifier of the second core network device sent by the fourth core network device, which may include: the first core network device sends first information to the fourth core network device, wherein the first information includes the identifier of the second session and the identifier of the first UE; the first core network device receives the identifier of the second core network device sent by the fourth core network device.

[0111] The processing of the fourth core network device may include: the fourth core network device receives the first information from the first core network device; the fourth core network device determines the SUPI of the second UE based on the identifier of the first UE in the first information; the fourth core network device searches for the locally stored session context of the second session based on the SUPI of the second UE and the identifier of the second session included in the first information; the fourth core network device obtains the identifier of the second core network device from the session context of the second session; the fourth core network device sends the identifier of the second core network device to the first core network device.

[0112] Among them, the fourth core network device determines the SUPI of the second UE based on the identifier of the first UE in the first information, which may include: the fourth core network device locally searches for the SUPI of another UE associated with the first UE (such as belonging to the same user or the same terminal as the first UE) based on the identifier of the first UE in the first information, and uses the SUPI of the other UE as the SUPI of the second UE.

[0113] Optionally, the first request also carries a first indication; the first information includes: an identifier of the second session, an identifier of the first UE, and the first information also includes the first indication.

[0114] The first core network device sends the first information to the fourth core network device, and the first core network device receives the identifier of the second core network device sent by the fourth core network device, which may include: the first core network device sends the first information to the fourth core network device, wherein the first information includes the identifier of the second session, the identifier of the first UE, and the first indication; the first core network device receives the identifier of the second core network device sent by the fourth core network device.

[0115] The processing of the fourth core network device may include: the fourth core network device receives the first information from the first core network device; the fourth core network device determines that the first session is used for MASSS based on the first indication included in the first information; the fourth core network device determines the SUPI of the second UE based on the identifier of the first UE in the first information; the fourth core network device searches for the locally stored session context of the second session based on the SUPI of the second UE and the identifier of the second session included in the first information; the fourth core network device obtains the identifier of the second core network device from the session context of the second session; the fourth core network device sends the identifier of the second core network device to the first core network device.

[0116] Optionally, when the fourth core network device sends the identifier of the second core network device to the first core network device, the fourth core network device may also send at least one of the following to the first core network device: a first indication, an identifier of the second session, an identifier of the second UE (specifically, the SUPI of the second UE).

[0117] In some possible implementations, after the first core network device receives the first request sent by the terminal, it may also include: the first core network device sends second information to the second core network device, wherein the second information includes at least one of the following: a first indication, an identifier of the second session, the GUTI of the second UE, the SUPI of the second UE, the identifier of the first session, the DNN corresponding to the first session, and the S-NSSAI corresponding to the first session; the first core network device receives third information sent by the second core network device, wherein the third information includes at least one of the following: an identifier of the first session and a MASSS rule.

[0118] The processing by the second core network device may include: the second core network device receiving second information sent by the first core network device, and the second core network device sending third information to the first core network device.

[0119] The second information may include at least part of the information carried in the first request. Preferably, the second information may carry all the information in the first request, for example, the second information may include an identifier of the second session corresponding to the second UE; the second information may also include any one of the first PDU session establishment request and the first PDU session modification request; the second information may also include at least one of the following: the first indication, the GUTI of the second UE, the SUPI of the second UE, the identifier of the first session, the DNN corresponding to the first session, and the S-NSSAI corresponding to the first session.

[0120] The processing timing for the first core network device to send the second information to the second core network device may be after the first core network device receives the first request sent by the first UE of the terminal and after the first core network device obtains the identifier of the second core network device.

[0121] Taking the first core network device as the first AMF and the second core network device as the SMF as an example, the way in which the first core network device sends the second information to the second core network device may include: the first AMF carries all the information carried in the first request received from the first UE of the terminal in the first information, and forwards the first information to the SMF by calling the first service of the first AMF. The second core network device sends the third information to the first core network device, which may include: the SMF carries the identifier of the first session and at least one of the MASSS rules in the third information, and sends the third information to the first AMF by calling the second service of the first AMF. The first service and the second service are not limited in this embodiment, and the first service and the second service are the same or different within the protection scope of this embodiment.

[0122] Optionally, the third information may include an identifier of the first session.

[0123] In one example, the second information and the first request include an identifier of the first session. The identifier of the first session is generated or determined by the first UE of the terminal. The identifier of the first session and the identifier of the second session may be the same or different. The method for generating or determining the identifier of the first session in this example is the same as that in the previous embodiment and is not repeated here.

[0124] In this example, when sending the third information, the second core network device can carry the identifier of the first session included in the second information in the third information and send it to the first core network device, so that the first core network device knows that the third information sent this time is a response or reply to the establishment or modification of the first session.

[0125] In one example, the second information and the first request do not include an identifier of the first session.

[0126] In this example, the second core network device can also generate or determine the identifier of the first session, and when sending the third information, carry the identifier of the first session in the third information and send it to the first core network device, so that the first core network device knows that the third information sent this time is a response or reply to the establishment or modification of the first session, and enables the first core network device to obtain the identifier of the first session.

[0127] In one case, the identifier of the second session is the same as the identifier of the first session. The manner in which the second core network device generates or determines the identifier of the first session may include: the second core network device obtains the identifier of the second session corresponding to the second UE of the terminal, and directly uses the identifier of the second session as the identifier of the first session.

[0128] In one case, the identifier of the second session is different from the identifier of the first session. The way in which the second core network device generates or determines the identifier of the first session may include: generating the identifier of the first session. Exemplarily, the second core network device may obtain the identifiers of the sessions corresponding to each UE of the terminal that has completed establishment or modification, and use the identifier that is different from the identifier of the session corresponding to each UE as the identifier of the first session. Taking the example of a terminal that only includes two UEs, namely the first UE and the second UE, the second core network device may obtain the identifier of the second session corresponding to the second UE of the terminal that has completed establishment or modification, and use the identifier that is different from the identifier of the second session corresponding to the second UE as the identifier of the first session.

[0129] Optionally, the third information may include one of the following: a first PDU session establishment accept message and a first PDU session modification command. If the first request includes a first PDU session establishment request, the third information includes the first PDU session establishment accept message; if the first request includes a first PDU session modification request, the third information includes the first PDU session modification command.

[0130] Further, the MASSS rule may be carried by the first PDU session establishment accept message in the third information, or the MASSS rule may be carried by the first PDU session modification command in the third information.

[0131] The MASSS rule is used to configure the terminal to select at least one of an access technology, an access mode, and a handover path for uplink data corresponding to multiple sessions, where the multiple sessions include at least one of the following: the first session and the second session. The MASSS rule may be generated by the second core network device based on actual conditions. This embodiment does not limit the manner in which the rule is generated.

[0132] Exemplarily, the multiple sessions may include the first session and the second session. Exemplarily, the multiple sessions may include the first session, the second session, and may also include other sessions that the terminal may establish, which are not limited or exhaustive here.

[0133] Exemplarily, the MASSS rules may include at least one of the following: an access technology used by the terminal to select the uplink data transmission corresponding to each session, an access technology used by the terminal to select the uplink data transmission corresponding to each session, and a switching path condition that needs to be met when the terminal selects the uplink data of each session for path switching.

[0134] The number of the access technologies may be one or more, for example, may include at least one of the following: E-UTRA (Evolved Universal Terrestrial Radio Access), NR terrestrial access, and NR satellite access.

[0135] The number of access modes may be one or more, for example, at least one of the following: Active-Standby, Smallest Delay, and Priority-based. Here, when the access mode is Active-Standby, it indicates that available access is used; when the access mode is Smallest Delay, it indicates that the access with the smallest delay is used; and when the access mode is Priority-based, it indicates that a higher priority access is used.

[0136] There may be one or more conditions for the switching path. For example, different sessions may correspond to different switching path conditions, or multiple sessions may correspond to the same switching path conditions. The conditions of any switching path are used to determine whether the corresponding switching path conditions are met when the terminal selects uplink data for path switching.

[0137] After the first core network device receives the third information sent by the second core network device, it also includes: the first core network device sends a first response to the terminal, wherein the first response is used to indicate the completion of establishing or modifying the first session, and the first response carries at least one of the following: the identifier of the first session, and the MASSS rule.

[0138] Correspondingly, after the terminal sends the first request to the first core network device, it also includes: the terminal receives a first response sent by the first core network device, wherein the first response is used to indicate the completion of establishing or modifying the first session, and the first response carries at least one of the following: the identifier of the first session, and the MASSS rule.

[0139] Specifically, the first core network device sending the first response to the terminal may be: the first core network device sending the first response to the first UE of the terminal. The terminal receiving the first response sent by the first core network device may be: the first UE of the terminal receives the first response sent by the first core network device.

[0140] The first response may be carried by a first DL (Downlink) NAS (Non-access stratum) message. Exemplarily, the first DL NAS message may be encapsulated in a first DL NAS Transfer message or signaling and transmitted.

[0141] The information carried in the first response is the same as the content included in the third information.

[0142] Exemplarily, when the third information includes a first PDU session establishment acceptance message and the first PDU session establishment acceptance message carries the MASSS rule, the first response also includes a first PDU session establishment acceptance message carrying the MASSS rule, and the first response is used to indicate the completion of establishing the first session.

[0143] Exemplarily, when the third information includes a first PDU session modification command and the first PDU session modification command carries a MASSS rule, the first response also includes a first PDU session modification command carrying a MASSS rule, and the first response is used to indicate the completion of the modification of the first session.

[0144] Exemplarily, when the third information includes the identifier of the first session, the first response also carries the identifier of the first session.

[0145] In some possible implementations, before the terminal sends the first request to the first core network device, it has at least completed establishing or modifying the second session corresponding to the second UE. This implementation describes the process of the terminal requesting to establish or modify the second session.

[0146] Before the terminal sends the first request to the first core network device, it also includes one of the following: the terminal sends the second request to the first core network device, wherein the second request is used to establish or modify the second session; the terminal sends the second request to the third core network device.

[0147] Furthermore, on the terminal side, the method also includes one of the following: the terminal receives a second response sent by the first core network device, wherein the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: an identifier of the second session, a MASSS rule; the terminal receives the second response sent by the third core network device.

[0148] In one embodiment, the first UE and the second UE both correspond to a first core network device. That is, the AMFs corresponding to the first UE and the second UE are the same, both being first AMFs.

[0149] In this embodiment, before the terminal sends the first request to the first core network device, the further step includes: the terminal sends the second request to the first core network device. Before the first core network device receives the first request sent by the terminal, the further step includes: the first core network device receives the second request sent by the terminal.

[0150] The terminal sending the second request to the first core network device may refer to: the second UE of the terminal sending the second request to the first core network device. The first core network device receiving the second request sent by the terminal may refer to: the first core network device receiving the second request sent by the second UE of the terminal.

[0151] The second request may be carried by a second UL (Uplink) NAS (Non-access stratum) message. Exemplarily, the second uplink NAS message may be encapsulated in a second UL NAS Transfer message or signaling and transmitted.

[0152] The second request may carry one of the following: a second PDU session establishment request (PDU Session Establish Request) or a second PDU session modification request (PDU Session Modification Request). Wherein, if the second request includes a second PDU session establishment request, the second request is used to establish a second session corresponding to the second UE; if the second request includes a second PDU session modification request, the second request is used to modify the second session corresponding to the second UE.

[0153] Optionally, the second request may carry at least one of the following: a second indication, the second indication being used to indicate that the second session is used for MASSS; an identifier of the second session; a DNN corresponding to the second session; and an S-NSSAI corresponding to the second session.

[0154] The second indication may be referred to as a second MASSS indication. The second session being used for MASSS may mean that the second session may be used to perform at least one of processes such as redirection, switching, and splitting between one or more sessions established with one or more other UEs of the terminal. In other words, through the second indication, the first core network device may determine that the second session currently requested to be established or modified by the second UE of the terminal can be used to perform at least one of processes such as redirection, switching, and splitting between sessions established with various other UEs of the terminal and also used for MASSS.

[0155] The identifier of the second session may be generated by the terminal. Specifically, the identifier of the second session may be generated by the second UE of the terminal.

[0156] This embodiment does not limit the determination or generation method of the DNN corresponding to the second session and the S-NSSAI corresponding to the second session.

[0157] After the first core network device receives the second request sent by the terminal, it also includes: the first core network device selects the second core network device corresponding to the second session based on at least one of the second indication, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; the first core network device saves the identifier of the second core network device corresponding to the second session.

[0158] Exemplarily, the first core network device selecting the second core network device corresponding to the second session based on at least one of the second indication, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session may include at least one of the following:

[0159] The first core network device determines, based on the DNN corresponding to the second session and the S-NSSAI corresponding to the second session, that there is a candidate SMF (or determines that there is a candidate SMF corresponding to the second session), that the candidate SMF is used as the second core network device corresponding to the second session;

[0160] When the first core network device determines that there are multiple candidate SMFs (or determines that there are multiple candidate SMFs corresponding to the second session) based on the DNN corresponding to the second session and the S-NSSAI corresponding to the second session, the first core network device selects an SMF that supports MASSS from multiple candidate SMFs as the second core network device corresponding to the second session based on the second indication.

[0161] Among them, the first core network device determines the specific processing method of one or more candidate SMFs based on the DNN corresponding to the second session and the S-NSSAI corresponding to the second session. This embodiment does not limit it.

[0162] Selecting an SMF that supports MASSS from multiple candidate SMFs as the second core network device corresponding to the second session may include one of the following: when there is only one candidate SMF that supports MASSS among multiple candidate SMFs, selecting the candidate SMF that supports MASSS as the second core network device corresponding to the second session; when there are multiple candidate SMFs that support MASSS among multiple candidate SMFs, selecting one of the multiple candidate SMFs that support MASSS as the second core network device corresponding to the second session.

[0163] The method of selecting one of multiple candidate SMFs supporting MASSS as the second core network device corresponding to the second session may be one of the following: selecting any one of multiple candidate SMFs supporting MASSS as the second core network device corresponding to the second session; or selecting one candidate SMF from multiple candidate SMFs supporting MASSS as the second core network device corresponding to the second session. The method of selecting a candidate SMF may be configured according to actual circumstances and is not limited in this embodiment.

[0164] Exemplarily, the first core network device saves the identifier of the second core network device corresponding to the second session, which may include: the first core network device saves the identifier of the second core network device corresponding to the second session as the session context of the second session. Specifically, the first core network device may add the identifier of the second core network device corresponding to the second session to the session context of the second session for storage. It should also be noted that the session context of the second session may also be bound or associated with the SUPI of the second UE, that is, the first core network device may also save the association or correspondence between the SUPI of the second UE and the session context of the second session.

[0165] In addition to including the identifier of the second core network device, the session context of the second session may also include other content. For example, the session context of the second session may also include the identifier of the second session. In addition, the session context of the second session may also include at least one of the DNN corresponding to the second session, the S-NSSAI of the second session, etc., which are not limited or exhaustive here.

[0166] The processing on the first core network device side also includes: the first core network device sends fourth information to the second core network device, wherein the fourth information includes at least one of the following: the second indication, the identifier of the second session, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; the first core network device receives fifth information sent by the second core network device, wherein the fifth information includes at least one of the following: the identifier of the second session and the MASSS rule.

[0167] The processing by the second core network device may include: the second core network device receiving fourth information sent by the first core network device, and the second core network device sending fifth information to the first core network device.

[0168] Here, the timing for the first core network device to send the fourth information to the second core network device may be after the first core network device selects the second core network device corresponding to the second session, or after the first core network device saves the identifier of the second core network device corresponding to the second session, which is not limited here.

[0169] The fourth information may include at least part of the information carried in the second request. Preferably, the fourth information may include all the information in the second request.

[0170] Taking the first core network device as the first AMF and the second core network device as the SMF as an example, the manner in which the first core network device sends the fourth information to the second core network device may include: the first AMF carries all the information carried in the second request received from the second UE of the terminal in the fourth information, and forwards the fourth information to the SMF by calling the third service of the first AMF. The second core network device sends the fifth information to the first core network device, which may include: the SMF carries the identifier of the second session and at least one of the MASSS rules in the fifth information, and sends the fifth information to the first AMF by calling the fourth service of the first AMF. The third service and the fourth service are not limited in this embodiment. Whether the third service is the same as or different from the fourth service, the first service is the same as or different from the third service, and the second service is the same as or different from the fourth service, all fall within the protection scope of this embodiment.

[0171] After the second core network device receives the fourth information sent by the first core network device, and before the second core network device sends the fifth information to the first core network device, the processing of the second core network device may also include: after the second core network device accepts the establishment or modification of the second session, the second core network device sends the sixth information to the fourth core network device by calling the service corresponding to the fourth core network device to register its own identifier to the fourth core network device, and the sixth information includes at least one of the following: the second indication, the identifier of the second session, the DNN corresponding to the second session, the S-NSSAI corresponding to the second session, and the identifier of the second core network device; the second core network device receives a response corresponding to the sixth information sent by the fourth core network device, and the response corresponding to the sixth information is used to indicate that the registration of the second core network device has passed or is successful.

[0172] Correspondingly, the processing of the fourth core network device may include: the fourth core network device receives the sixth information sent by the second core network device through its own corresponding service, and sends a response corresponding to the sixth information to the second core network device.

[0173] In a preferred example, the sixth information includes the identifier of the second session, the DNN corresponding to the second session, the S-NSSAI corresponding to the second session, and the identifier of the second core network device.

[0174] In this case, the fourth core network device can save the identifier of the second session, the DNN corresponding to the second session, the S-NSSAI corresponding to the second session, and the identifier of the second core network device locally as the session context of the second session.

[0175] In an optional example, in addition to the identifier of the second session, the DNN corresponding to the second session, the S-NSSAI corresponding to the second session, and the identifier of the second core network device, the sixth information may include a second indication.

[0176] In this case, the fourth core network device can determine that the second session is used for MASSS based on the second indication, and can save the second indication (optionally), the identifier of the second session, the DNN corresponding to the second session, the S-NSSAI corresponding to the second session, and the identifier of the second core network device locally as the session context of the second session.

[0177] Furthermore, regardless of which of the above examples, the fourth core network device can also save the association or correspondence between the SUPI of the second UE, the session context of the second session, the SUPI of the second UE and the session context of the second session on the fourth core network device side.

[0178] On the second core network device side, after receiving a response corresponding to the sixth information from the fourth core network device, the fifth information can be sent to the first core network device.

[0179] Optionally, the fifth information may include an identifier of the second session.

[0180] Optionally, the fifth information may include one of the following: a second PDU session establishment accept message and a second PDU session modification command. If the second request includes a second PDU session establishment request, the fifth information includes the second PDU session establishment accept message; if the second request includes a second PDU session modification request, the fifth information includes the second PDU session modification command.

[0181] Further, the MASSS rule may be carried by the second PDU session establishment accept message in the fifth information, or the MASSS rule may be carried by the second PDU session modification command in the fifth information.

[0182] The MASSS rule is used to configure the terminal to select at least one of an access technology, an access mode, and a handover path for uplink data corresponding to multiple sessions, where the multiple sessions include at least one of the following: the first session and the second session. The MASSS rule may be generated by the second core network device based on actual conditions. This embodiment does not limit the manner in which the rule is generated.

[0183] Exemplarily, the multiple sessions may include the first session. Exemplarily, the multiple sessions may include the first session and may also include other sessions that the terminal may establish, such as the second session, etc., which are not limited or exhaustive here.

[0184] The relevant description of the MASSS rule is similar to that of the aforementioned embodiment, and thus will not be repeated.

[0185] After the first core network device receives the fifth information sent by the second core network device, it also includes: the first core network device sends a second response to the terminal, wherein the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: an identifier of the second session, a MASSS rule.

[0186] Correspondingly, after the terminal sends the second request to the first core network device, it also includes: the terminal receives a second response sent by the first core network device, wherein the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: the identifier of the second session, and the MASSS rule.

[0187] Specifically, the first core network device sending the second response to the terminal may be: the first core network device sending the second response to the second UE of the terminal. The terminal receiving the second response sent by the first core network device may be: the second UE of the terminal receiving the second response sent by the first core network device.

[0188] The second response may be carried by a second DL (Downlink) NAS (Non-access stratum) message. Exemplarily, the second DL NAS message may be encapsulated in a second DL NAS Transfer message or signaling and transmitted.

[0189] The information carried in the second response is the same as the content included in the fifth information.

[0190] Exemplarily, when the fifth information includes a second PDU session establishment acceptance message and the second PDU session establishment acceptance message carries the MASSS rule, the second response also includes a second PDU session establishment acceptance message carrying the MASSS rule, and the second response is used to indicate the completion of establishing the second session.

[0191] Exemplarily, when the fifth information includes a second PDU session modification command and the second PDU session modification command carries a MASSS rule, the second response also includes a second PDU session modification command carrying a MASSS rule, and the second response is used to indicate the completion of the modification of the second session.

[0192] It should be pointed out that if the MASSS rules are carried in the fifth information and the second response, the MASSS rules may no longer be sent to the terminal during the subsequent process of the terminal sending the first request and receiving the first response, that is, the aforementioned third information and the first response may not carry the MASSS rules; or, if the MASSS rules are not carried in the fifth information and the second response, the MASSS rules may be configured and sent to the terminal during the subsequent process of the terminal sending the first request and receiving the first response, that is, the aforementioned third information and the first response may carry the MASSS rules.

[0193] Exemplarily, when the fifth information includes the identifier of the second session, the second response also carries the identifier of the second session.

[0194] In one embodiment, the first UE and the second UE correspond to different core network devices, that is, the first UE corresponds to a first core network device, and the second UE corresponds to a third core network device.

[0195] Exemplarily, the first core network device may be the first AMF, and the third core network device may be the second AMF.

[0196] In this embodiment, before the terminal sends the first request to the first core network device, the process further includes: the terminal sending the second request to the third core network device. The process further includes: the third core network device receiving the second request sent by the terminal.

[0197] The terminal sending the second request to the third core network device may refer to: the second UE of the terminal sending the second request to the third core network device. The third core network device receiving the second request sent by the terminal may refer to: the third core network device receiving the second request sent by the second UE of the terminal. The relevant description of the second request is similar to that of the aforementioned embodiment, except that the receiving object is replaced by the third core network device, and therefore will not be repeated.

[0198] After the third core network device receives the second request sent by the terminal, the method further includes: the third core network device selecting the second core network device corresponding to the second session based on at least one of the second indication, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; and the third core network device storing the identifier of the second core network device corresponding to the second session. The specific process of the third core network device selecting the second core network device is similar to the specific process of the first core network device selecting the second core network device in the aforementioned embodiment, and will not be repeated here.

[0199] The third core network device saving the identifier of the second core network device corresponding to the second session may include: the third core network device saving the identifier of the second core network device corresponding to the second session as the session context of the second session. Specifically, the third core network device may add the identifier of the second core network device corresponding to the second session to the session context of the second session for storage. It should also be noted that the session context of the second session may also be bound or associated with the SUPI of the second UE, that is, the third core network device may also save the association or correspondence between the SUPI of the second UE and the session context of the second session.

[0200] In addition, the third core network device may also store the association or correspondence between the SUPI of the second UE, the session context of the second session, the SUPI of the second UE, and the session context of the second session on the fourth core network device side.

[0201] The processing on the third core network device side also includes: the third core network device sends fourth information to the second core network device, wherein the fourth information includes at least one of the following: the second indication, the identifier of the second session, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; the third core network device receives fifth information sent by the second core network device, wherein the fifth information includes at least one of the following: the identifier of the second session and the MASSS rule.

[0202] The processing by the second core network device may include: the second core network device receiving fourth information sent by the third core network device, and the second core network device sending fifth information to the third core network device.

[0203] After the third core network device receives the fifth information sent by the second core network device, the method further includes: the third core network device sends a second response to the terminal. Correspondingly, after the terminal sends the second request to the third core network device, the method further includes: the terminal receives a second response sent by the third core network device, wherein the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: an identifier of the second session and a MASSS rule.

[0204] Here, the descriptions of the fourth information, the fifth information, and the like are similar to those in the aforementioned embodiment and are not repeated here. The processing related to the third core network device is also similar to the processing related to the first core network device in the aforementioned embodiment and is not repeated here. The descriptions of the second response are the same as in the aforementioned embodiment. The processing related to the third core network device sending the second response to the terminal is the same as the processing related to the first core network device sending the second response to the terminal in the aforementioned embodiment, and therefore are not repeated here.

[0205] It can be seen that by adopting the solution provided by the above embodiment, when there is a second UE in the terminal that has completed the establishment of the second session, when the terminal requests the first core network device to establish or modify the first session corresponding to the first UE, by carrying the identifier of the established second session in the corresponding request, the first core network device can select the second core network device corresponding to the second session, and then the network side can associate the multiple sessions established by the multiple UEs of the terminal with the same second core network device, thereby ensuring that the service data of the multiple sessions can be aggregated to the same core network device side, so as to ensure that the network side can realize MASSS of multiple sessions of the multiple UEs of the control terminal.

[0206] Next, multiple exemplary explanations are given of the communication method of the aforementioned embodiment in conjunction with Figures 8 and 9. In the scenarios illustrated in Figures 8 and 9, the terminal includes two UEs, specifically the first UE and the second UE included in the terminal; more specifically, in the examples of Figures 8 and 9, taking the first UE of the terminal as UE2, the second UE of the terminal as UE1, the second core network device as SMF, and the fourth core network device as UDM as an example, multiple exemplary explanations are given of the communication method provided in the embodiment of the present application. It should be pointed out that the AMF corresponding to UE2 can be the same or a different AMF from the AMF corresponding to UE1. This is because the position of the UE is taken into consideration when selecting the AMF, and UE1 and UE2 are in the same device (terminal), that is, in the same position, so UE1 and UE2 may be assigned the same AMF. However, because the selection of the AMF also takes into account the slice requested by the UE, different AMFs may also be selected.

[0207] Example 1: In the scenario illustrated in Figure 8, the UE1 and UE2 included in the terminal correspond to the same AMF. In this example, the AMF is the first core network device (first AMF) in the aforementioned embodiment. The specific process is shown in Figure 8, including the following steps:

[0208] Step 801: When UE1 is triggered to establish a PDU session that can be used for MASSS, UE1 sends an uplink NAS transfer (UL NAS transfer) message (i.e., the second request in the aforementioned embodiment) to the AMF, which includes MASSS indication 1 (i.e., the second indication in the aforementioned embodiment), the ID of PDU session 1 (which can be expressed as PDU Session 1 ID, i.e., the identifier of the second session in the aforementioned embodiment), DNN-1 (i.e., the DNN corresponding to the second session in the aforementioned embodiment), S-NSSAI-1 (i.e., the S-NSSAI corresponding to the second session in the aforementioned embodiment), and PDU session establishment request -1 (i.e., the second PDU session establishment request in the aforementioned embodiment). Among them, MASSS indication 1 is used to indicate that the PDU session (i.e., the second session) is used for MASSS, and the ID of PDU session 1 is allocated by UE1.

[0209] In step 802, the AMF selects an SMF that supports MASSS according to MASSS indication 1, DNN-1, and S-NSSAI-1. The AMF transfers the information received from UE1 (i.e., the fourth information in the aforementioned embodiment) to the SMF by calling an AMF service (such as Namf); the AMF saves the SMF ID or address as the context of the PDU session1.

[0210] In step 803, after the SMF accepts the establishment of the PDU session, the SMF registers its own address with the UDM. Specifically, the SMF sends at least one of the following (i.e., the sixth information in the aforementioned embodiment) to the UDM by calling the UDM service (such as Nudm): MASSS indication 1 (optional), PDU session 1 ID, DNN-1, S-NSSAI-1, and SMF address. The SMF address can be an SMF ID, an IP address, or an address within the operator.

[0211] Step 804: The UDM learns that the PDU session 1 is for MASSS according to the MASSS indication 1 and responds to the SMF. The response may be the response corresponding to the sixth information in the aforementioned embodiment, such as an ACK (acknowledgement) response.

[0212] In step 805, SMF calls an AMF service (such as Namf) and sends the ID of PDU session 1 and PDU session establishment accept (PDU session establishment accept)-1 (i.e., the second PDU session establishment accept in the aforementioned embodiment) to AMF.

[0213] Optionally, the PDU session establishment request-1 may include a MASSS rule, wherein the MASSS rule is used to configure conditions for selecting an access technology, mode, switching path, etc. to be used for uplink data.

[0214] In step 806, the AMF sends a downlink NAS transfer (DL NAS transfer) message (i.e., the second response of the aforementioned embodiment) to UE1, including the ID of the PDU session 1 received from the SMF and PDU session establishment acceptance-1 (which may include MASSS rules).

[0215] In step 807, when UE2 is triggered to establish PDU session 2 that can be used for MASSS, the trigger can come from one of the application layer, the terminal, or UE1. UE2 obtains the ID of PDU session 1 for establishing the above session from UE1, and optionally obtains the UE1 ID. UE2 sends an uplink NAS transfer (UL NAS transfer) message (i.e., the first request in the aforementioned embodiment) to the AMF, which includes MASSS indication 2 (i.e., the first indication in the aforementioned embodiment), the ID of PDU session 1 obtained from UE1, UE1 ID, DNN-2 (i.e., the DNN corresponding to the first session in the aforementioned embodiment), S-NSSAI-2 (i.e., the S-NSSAI corresponding to the first session in the aforementioned embodiment), and PDU session establishment request-2 (i.e., the first PDU session establishment request in the aforementioned embodiment). MASSS indication 2 is used to indicate that PDU session 2 is used for MASSS. UE1 ID, DNN-2, and S-NSSAI-2 are optional parameters. Optionally, if UE2 is also assigned an ID for PDU session 2, the ID of PDU session 2 may also be included.

[0216] The UE1 ID may be at least one of SUPI and GUTI.

[0217] The AMF learns from MASSS indication2 that the PDU session 2 is used for MASSS.

[0218] Optionally, if the AMF does not receive the UE1 ID, because UE2 supports MASSS, the AMF knows that UE1 and UE2 belong to the same user, and finds the associated UE1 ID = SUPI from the UDM according to the UE2 ID.

[0219] Optionally, if AMF receives UE1 ID = GUTI, AMF needs to find the SUPI corresponding to UE1's GUTI.

[0220] Afterwards, the AMF confirms whether there is a session context corresponding to the ID of UE1's PDU session1 based on the PDU session ID and UE1SUPI obtained from UE1, and obtains the SMF ID or address of PDU session 1 from the session context, that is, the SMF ID or address saved in step 802.

[0221] In step 808, the AMF transfers the information received from UE2 to the SMF by calling an AMF service (such as Namf). Here, the information sent by the AMF to the SMF may be the second information in the aforementioned embodiment. Exemplarily, the information sent by the AMF to the SMF specifically includes the following: MASSS indication 2, PDU session 1 ID, UE1 ID, PDU session 2 ID, DNN-2, S-NSSAI-2, and PDU session establishment request-2.

[0222] In step 809, SMF calls an AMF service (such as Namf) and sends the ID of PDU session 2 (which can be expressed as PDU session2 ID, which can be the same as the PDU session1 ID obtained from UE1 for establishing the above session) and PDU session establishment accept (PDU session establishment accept)-2 (that is, the first PDU session establishment accept in the aforementioned embodiment) to AMF.

[0223] Optionally, the PDU Session Establishment Accept-2 may include a MASSS rule. If no MASSS rule was sent in step 805, it is sent here. The MASSS rule is used to configure the conditions for selecting the access technology, mode, and switching path to be used for uplink data.

[0224] In step 810, the AMF sends a downlink NAS transfer (DL NAS transfer) message (i.e., the first response of the aforementioned embodiment) to UE2, including the ID of the PDU session 2 received from the SMF and the PDU session establishment acceptance-2 (which may include MASSS rules).

[0225] Through the above example 1, the two PDU sessions established by the two UEs included in the terminal are associated with the same SMF, and then the two sessions established by the two UEs can be associated with the same UPF through the same SMF, thereby ensuring that the business data of multiple PDU sessions of the terminal are aggregated to the same UPF to achieve MASSS.

[0226] Example 2: In the scenario illustrated in Figure 9, the UE1 and UE2 included in the terminal correspond to different AMFs. In this example, the AMF corresponding to UE1 is represented as UE1-AMF, and the AMF corresponding to UE2 is represented as UE2-AMF, where UE2-AMF is the first core network device (first AMF) in the aforementioned embodiment, and UE1-AMF is the third core network device (second AMF) in the aforementioned embodiment. The specific process is shown in Figure 9 and includes the following steps:

[0227] Step 901: When UE1 is triggered to establish a PDU session that can be used for MASSS, UE1 sends an uplink NAS transfer (UL NAS transfer) message (i.e., the second request in the aforementioned embodiment) to UE1-AMF, which includes MASSS indication 1 (i.e., the second indication in the aforementioned embodiment), the ID of PDU session 1 (which can be expressed as PDU Session 1 ID, i.e., the identifier of the second session in the aforementioned embodiment), DNN-1 (i.e., the DNN corresponding to the second session in the aforementioned embodiment), S-NSSAI-1 (i.e., the S-NSSAI corresponding to the second session in the aforementioned embodiment), and PDU session establishment request -1 (i.e., the second PDU session establishment request in the aforementioned embodiment). Among them, MASSS indication 1 is used to indicate that the PDU session (i.e., the second session) is used for MASSS, and the ID of PDU session 1 is allocated by UE1.

[0228] In step 902, UE1-AMF selects an SMF that supports MASSS according to MASSS indication 1, DNN-1, and S-NSSAI-1. UE1-AMF transfers the information received from UE1 (i.e., the fourth information in the aforementioned embodiment) to SMF by calling an AMF service (such as Namf); UE1-AMF saves the SMF ID or address as the context of the PDU session1.

[0229] The related processing of steps 903 to 904 is the same as that of steps 803 to 804 and will not be repeated.

[0230] In step 905, SMF calls a UE1-AMF service (such as Namf) and sends the ID of PDU session 1 and PDU session establishment accept (PDU session establishment accept)-1 (i.e., the second PDU session establishment accept in the aforementioned embodiment) to UE1-AMF.

[0231] Optionally, the PDU session establishment request-1 may include a MASSS rule, wherein the MASSS rule is used to configure conditions for selecting an access technology, mode, switching path, etc. to be used for uplink data.

[0232] In step 906, UE1-AMF sends a downlink NAS transfer (DL NAS transfer) message (i.e., the second response of the aforementioned embodiment) to UE1, including the ID of the PDU session 1 received from the SMF and PDU session establishment acceptance-1 (which may include MASSS rules).

[0233] In step 907, when UE2 is triggered to establish PDU session 2 that can be used for MASSS, the trigger can come from one of the application layer, the terminal, or UE1. UE2 obtains the ID of the PDU session 1 for establishing the above-mentioned session from UE1, and optionally obtains the UE1 ID. UE2 sends an uplink NAS transfer (UL NAS transfer) message (i.e., the first request in the aforementioned embodiment) to UE2-AMF, which includes MASSS indication 2 (i.e., the first indication in the aforementioned embodiment), the ID of PDU session 1 obtained from UE1, UE1 ID, DNN-2 (i.e., the DNN corresponding to the first session in the aforementioned embodiment), S-NSSAI-2 (i.e., the S-NSSAI corresponding to the first session in the aforementioned embodiment), and PDU session establishment request-2 (i.e., the first PDU session establishment request in the aforementioned embodiment). MASSS indication 2 is used to indicate that PDU session 2 is used for MASSS. UE1 ID, DNN-2, and S-NSSAI-2 are optional parameters. Optionally, if UE2 is also allocated an ID of PDU session 2, the ID of PDU session 2 may also be included.

[0234] The UE1 ID may be at least one of SUPI and GUTI.

[0235] UE2-AMF learns from MASSS indication2 that PDU session 2 is used for MASSS.

[0236] Optionally, if UE2-AMF does not receive UE1 ID, because UE2 supports MASSS, UE2-AMF knows that UE1 and UE2 belong to the same user, and then finds the associated UE1 ID = SUPI from UDM according to UE2 ID.

[0237] Optionally, if UE2-AMF receives UE1 ID = GUTI, UE2-AMF needs to find the SUPI corresponding to UE1's GUTI.

[0238] In step 908, the UE2-AMF invokes the UDM service (e.g., Nudm) to obtain the SMF ID or address and sends MASSS indication2, the PDU session 1 ID (the ID of PDU session 1) obtained from UE1, and the UE1 SUPI to the UDM. The information sent by the UE2-AMF to the UDM in this step may be the first information in the aforementioned embodiment.

[0239] In step 909, the UDM finds the session context corresponding to UE1's PDU session1 ID based on MASSS indication 2, the PDU session1 ID obtained from UE1, and the UE1 SUPI. The UDM obtains the SMF ID or address of PDU session1 from the session context. The UDM (which may call Nudm) returns the SMF ID or address to the UE2-AMF.

[0240] Optionally, when UDM returns the SMF ID or address to UE2-AMF, UDM may also provide UE2-AMF with at least one of the following: MASSS indication2, PDU session1 ID, UE1SUPI.

[0241] In step 910, UE2-AMF transfers the information received from UE2 to SMF by calling an AMF service (such as Namf). Here, the information sent by AMF to SMF can be the second information in the aforementioned embodiment. Exemplarily, the information sent by AMF to SMF specifically includes the following: MASSS indication 2, PDU session 1 ID, UE1 ID, PDU session 2 ID, DNN-2, S-NSSAI-2, and PDU session establishment request-2.

[0242] In step 911, SMF calls an AMF service (such as Namf) and sends the ID of PDU session 2 (which can be expressed as PDU session2 ID, which can be the same as the PDU session1 ID obtained from UE1 for establishing the above session) and PDU session establishment accept (PDU session establishment accept)-2 (that is, the first PDU session establishment accept in the aforementioned embodiment) to UE2-AMF.

[0243] Optionally, the PDU Session Establishment Accept-2 may include a MASSS rule. If the MASSS rule was not sent in step 905, it is sent here. The MASSS rule is used to configure the conditions for selecting the access technology, mode, and switching path to be used for uplink data.

[0244] In step 912, UE2-AMF sends a downlink NAS transfer (DL NAS transfer) message (i.e., the first response of the aforementioned embodiment) to UE2, including the ID of PDU session 2 received from SMF and PDU session establishment acceptance-2 (which may include MASSS rules).

[0245] Through the above example 2, the two PDU sessions established by the two UEs included in the terminal are associated with the same SMF, and then the two sessions established by the two UEs can be associated with the same UPF through the same SMF, thereby ensuring that the business data of multiple PDU sessions of the terminal are aggregated to the same UPF to achieve MASSS.

[0246] It should be noted that the RAN is also illustrated in Figures 8 and 9 corresponding to Example 1 and Example 2. The function of the RAN in Figures 8 and 9 may be used to forward or transmit messages between the terminal (UE1 and UE2) and the AMF (such as the AMF in Figure 8, UE1-AMF and UE2-AMF in Figure 9). This embodiment does not limit the related processing of the RAN.

[0247] In addition, the first PDU session establishment request / acceptance in the above examples 1 and 2 can be replaced by a first PDU session modification request / command; the second PDU session establishment request / acceptance can be replaced by a second PDU session modification request / command. The related processing after the first PDU session establishment request / acceptance is replaced by the first PDU session modification request / command and the second PDU session establishment request / acceptance is replaced by the second PDU session modification request / command is similar to the above examples and will not be repeated here.

[0248] FIG10 is a schematic diagram of the structure of a terminal according to an embodiment of the present application, including:

[0249] The first communication unit 1001 is used to send a first request to a first core network device, wherein the first request is used to establish or modify a first session corresponding to a first user equipment UE, the first request carries an identifier of a second session corresponding to a second UE, the identifier of the second session is used by the first core network device to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

[0250] The first request also carries a first indication, where the first indication is used to indicate that the first session is used for multi-access steering, handover, and splitting of MASSS.

[0251] The first request also carries at least one of the following: a globally unique temporary UE identity GUTI of the second UE and a user permanent identifier SUPI of the second UE.

[0252] The first request also carries at least one of the following: an identifier of the first session; a data network name DNN corresponding to the first session; and single network slice selection auxiliary information S-NSSAI corresponding to the first session.

[0253] The first communication unit is used to receive a first response sent by the first core network device, wherein the first response is used to indicate the completion of establishing or modifying the first session, and the first response carries at least one of the following: an identifier of the first session and a MASSS rule.

[0254] The first communication unit is used to perform one of the following: sending the second request to the first core network device, wherein the second request is used to establish or modify the second session; sending the second request to a third core network device.

[0255] The second request carries at least one of the following: a second indication, where the second indication is used to indicate that the second session is used for MASSS; an identifier of the second session; a DNN corresponding to the second session; and an S-NSSAI corresponding to the second session.

[0256] The first communication unit is used to perform one of the following: receiving a second response sent by the first core network device, wherein the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: an identifier of the second session, a MASSS rule; receiving the second response sent by the third core network device.

[0257] The MASSS rule is used to configure the terminal to select at least one of the access technology, access mode, and switching path conditions for uplink data corresponding to multiple sessions, and the multiple sessions include at least one of the following: the first session and the second session.

[0258] FIG11 is a schematic diagram of the composition structure of a first core network device according to an embodiment of the present application, including:

[0259] The second communication unit 1101 is used to receive a first request sent by the terminal, wherein the first request is used to establish or modify a first session corresponding to a first user equipment UE, the first request carries an identifier of a second session corresponding to a second UE, the identifier of the second session is used to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

[0260] As shown in FIG11 , the first core network device further includes:

[0261] The second processing unit 1102 is configured to obtain an identifier of the second core network device based on the identifier of the second session.

[0262] The second processing unit is configured to obtain the identifier of the second core network device from the session context of the second session when it is determined that the session context of the second session is locally stored based on the identifier of the second session and the SUPI of the second UE.

[0263] The second communication unit is used to send first information to the fourth core network device, wherein the first information includes the identifier of the second session and the SUPI of the second UE; and receive the identifier of the second core network device sent by the fourth core network device.

[0264] The first information also includes a first indication.

[0265] The first request also carries at least one of the following: a globally unique temporary UE identity GUTI of the second UE and a SUPI of the second UE.

[0266] When the first request carries the GUTI of the second UE, the SUPI of the second UE is determined based on the GUTI of the second UE.

[0267] The second communication unit is configured to obtain the SUPI of the second UE from a fourth core network device based on the identifier of the first UE.

[0268] The first request also carries a first indication.

[0269] The first request also carries at least one of the following: an identifier of the first session; a data network name DNN corresponding to the first session; and single network slice selection auxiliary information S-NSSAI corresponding to the first session.

[0270] The second communication unit is used to send second information to the second core network device, wherein the second information includes at least one of the following: a first indication, an identifier of the second session, a GUTI of the second UE, a SUPI of the second UE, an identifier of the first session, a DNN corresponding to the first session, and an S-NSSAI corresponding to the first session; and receive third information sent by the second core network device, wherein the third information includes at least one of the following: an identifier of the first session, multi-access steering, switching and splitting MASSS rules.

[0271] The second communication unit is used to send a first response to the terminal, wherein the first response is used to indicate completion of establishment or modification of the first session, and the first response carries at least one of the following: an identifier of the first session and a MASSS rule.

[0272] The first indication is used to indicate that the first session is used for MASSS.

[0273] The second communication unit is configured to receive a second request sent by the terminal, wherein the second request is used to establish or modify the second session.

[0274] The second request carries at least one of the following: a second indication, where the second indication is used to indicate that the second session is used for MASSS; an identifier of the second session; a DNN corresponding to the second session; and an S-NSSAI corresponding to the second session.

[0275] The second processing unit is used to select the second core network device corresponding to the second session based on at least one of the second indication, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; and save the identifier of the second core network device corresponding to the second session.

[0276] The second communication unit is used to send fourth information to the second core network device, wherein the fourth information includes at least one of the following: the second indication, the identifier of the second session, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; and receive fifth information sent by the second core network device, wherein the fifth information includes at least one of the following: the identifier of the second session and the MASSS rule.

[0277] The second communication unit is used to send a second response to the terminal, wherein the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: an identifier of the second session and a MASSS rule.

[0278] The MASSS rule is used to configure the terminal to select at least one of the access technology, access mode, and switching path conditions for uplink data corresponding to multiple sessions, and the multiple sessions include at least one of the following: the first session and the second session.

[0279] The device of the embodiment of the present application can realize the corresponding functions of each device in the aforementioned authentication method embodiment. The corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the terminal or the first core network device can be found in the corresponding description in the above method embodiment, which will not be repeated here. It should be noted that the functions described in the terminal of the embodiment of the application or each module (sub-module, unit or component, etc.) in the first core network device can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).

[0280] Figure 12 is a schematic structural diagram of a communication device 1200 according to an embodiment of the present application. The communication device 1200 includes a processor 1210. The processor 1210 can retrieve and execute a computer program from a memory to enable the communication device 1200 to implement the method according to the embodiment of the present application. In one possible implementation, the communication device 1200 may also include a memory 1220. The processor 1210 can retrieve and execute a computer program from the memory 1220 to enable the communication device 1200 to implement the method according to the embodiment of the present application. The memory 1220 may be a separate device independent of the processor 1210 or integrated into the processor 1210. In one possible implementation, the communication device 1200 may also include a transceiver 1230. The processor 1210 can control the transceiver 1230 to communicate with other devices. Specifically, the transceiver 1230 can send information or data to other devices or receive information or data sent by other devices. The transceiver 1230 may include a transmitter and a receiver. The transceiver 1230 may further include an antenna, which may be one or more antennas.

[0281] In one possible implementation, the communication device 1200 may be a terminal or a first core network device in an embodiment of the present application, and the communication device 1200 may implement the corresponding processes implemented by the terminal or the first core network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0282] Figure 13 is a schematic structural diagram of a chip 1300 according to an embodiment of the present application. Chip 1300 includes a processor 1310, which can retrieve and execute computer programs from a memory to implement the methods in the embodiments of the present application. In one possible implementation, chip 1300 may also include a memory 1320. Processor 1310 can retrieve and execute computer programs from the memory 1320 to implement the methods in the embodiments of the present application performed by a terminal or a first core network device. Memory 1320 may be a separate device independent of processor 1310 or integrated into processor 1310. In one possible implementation, chip 1300 may also include an input interface 1330. Processor 1310 may control input interface 1330 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips. In one possible implementation, chip 1300 may also include an output interface 1340. The processor 1310 may control the output interface 1340 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0283] In one possible implementation, the chip can be applied to the terminal or the first core network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal or the first core network device in the various methods of the embodiment of the present application. For the sake of brevity, they are not described here. It should be understood that the chip mentioned in the embodiment of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc. The processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above can be a microprocessor or any conventional processor, etc. The memory mentioned above 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). It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application can also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DR RAM), etc. That is, the memory in the embodiment of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0284] Figure 14 is a schematic block diagram of a communication system 1400 according to an embodiment of the present application. Communication system 1400 includes a terminal 1410 and a first core network device 1420. Terminal 1410 can be used to implement the corresponding functions implemented by the terminal in the above-described method. First core network device 1420 can be used to implement the corresponding functions implemented by the first core network device in the above-described method. For the sake of brevity, these details are not further described here.

[0285] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0286] It should be understood that in the various embodiments of the present application, the size of the sequence number of each process mentioned above does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application, which should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claim.

Claims

1. A communication method, comprising: A terminal sends a first request to a first core network device, where the first request is used to establish or modify a first session corresponding to a first user equipment (UE), the first request carries an identifier of a second session corresponding to a second UE, and the identifier of the second session is used for the first core network device to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

2. The method according to claim 1, wherein The first request further carries a first indication, and the first indication is used to indicate that the first session is for multi-access steering, handover, and splitting (MASSS).

3. The method according to claim 1 or 2, wherein The first request further carries at least one of the following: the globally unique temporary UE identifier (GUTI) of the second UE, the permanent user identifier (SUPI) of the second UE.

4. The method according to any one of claims 1-3, wherein, The first request further carries at least one of the following: the identifier of the first session; the data network name (DNN) corresponding to the first session; the single network slice selection assistance information (S-NSSAI) corresponding to the first session.

5. The method according to any one of claims 1-4, wherein After the terminal sends the first request to the first core network device, it further includes: The terminal receives a first response sent by the first core network device, where the first response is used to indicate the completion of establishing or modifying the first session, and the first response carries at least one of the following: the identifier of the first session, MASSS rules.

6. The method according to any one of claims 1-5, wherein, Before the terminal sends the first request to the first core network device, it further includes one of the following: The terminal sends a second request to the first core network device, where the second request is used to establish or modify the second session; The terminal sends the second request to a third core network device.

7. The method according to claim 6, wherein The second request carries at least one of the following: A second indication, and the second indication is used to indicate that the second session is for MASSS; The identifier of the second session; The DNN corresponding to the second session; The S-NSSAI corresponding to the second session.

8. The method according to claim 6 or 7, wherein The method further includes one of the following: The terminal receives a second response sent by the first core network device, where the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: the identifier of the second session, MASSS rules; The terminal receives the second response sent by the third core network device.

9. The method according to claim 5 or 8, wherein The MASSS rules are used to configure at least one of the access technology, access mode, and handover path conditions for the terminal to select for using uplink data corresponding to multiple sessions, and the multiple sessions include at least one of the following: the first session, the second session.

10. A communication method, comprising: A first core network device receives a first request sent by a terminal, where the first request is used to establish or modify a first session corresponding to a first user equipment (UE), the first request carries an identifier of a second session corresponding to a second UE, and the identifier of the second session is used to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

11. The method according to claim 10, wherein, After the first core network device receives the first request sent by the terminal, it further includes: The first core network device obtains the identifier of the second core network device based on the identifier of the second session.

12. The method according to claim 11, wherein, The first core network device obtaining the identifier of the second core network device based on the identifier of the second session includes: When the first core network device determines that the session context of the second session is locally stored based on the identifier of the second session and the SUPI of the second UE, the first core network device obtains the identifier of the second core network device from the session context of the second session.

13. The method according to claim 11, wherein, The first core network device obtaining the identifier of the second core network device based on the identifier of the second session includes: The first core network device sends first information to the fourth core network device, where the first information includes the identifier of the second session and the SUPI of the second UE. The first core network device receives the identifier of the second core network device sent by the fourth core network device.

14. The method according to claim 13, wherein, The first information further includes a first indication.

15. The method according to any one of claims 12 - 14, wherein, The first request further carries at least one of the following: the globally unique temporary UE identifier GUTI of the second UE, the SUPI of the second UE.

16. The method according to claim 15, wherein, When the first request carries the GUTI of the second UE, the SUPI of the second UE is determined based on the GUTI of the second UE.

17. The method according to any one of claims 12 - 14, wherein, After the first core network device receives the first request sent by the terminal, it further includes: The first core network device obtains the SUPI of the second UE from the fourth core network device based on the identifier of the first UE.

18. The method according to any one of claims 10-17, wherein, The first request further carries a first indication.

19. The method according to any one of claims 10 - 18, wherein, The first request further carries at least one of the following: the identifier of the first session; the data network name DNN corresponding to the first session; the single network slice selection assistance information S-NSSAI corresponding to the first session.

20. The method according to any one of claims 10 - 19, wherein, After the first core network device receives the first request sent by the terminal, it further includes: The first core network device sends second information to the second core network device, where the second information includes at least one of the following: a first indication, the identifier of the second session, the GUTI of the second UE, the SUPI of the second UE, the identifier of the first session, the DNN corresponding to the first session, the S-NSSAI corresponding to the first session. The first core network device receives third information sent by the second core network device, where the third information includes at least one of the following: the identifier of the first session, multi-access steering, handover and splitting MASSS rules.

21. The method according to claim 20, wherein After the first core network device receives the third information sent by the second core network device, it further includes: The first core network device sends a first response to the terminal, where the first response is used to indicate the completion of establishing or modifying the first session, and the first response carries at least one of the following: the identifier of the first session, MASSS rules.

22. The method according to any one of claims 14, 18, 20, and 21, wherein, The first indication is used to indicate that the first session is for MASSS.

23. The method according to any one of claims 10 to 12, wherein, Before the first core network device receives the first request sent by the terminal, it further includes: The first core network device receives a second request sent by the terminal, where the second request is used to establish or modify the second session.

24. The method according to claim 23, wherein The second request carries at least one of the following: A second indication, where the second indication is used to indicate that the second session is for MASSS; The identifier of the second session; The DNN corresponding to the second session; The S-NSSAI corresponding to the second session.

25. The method according to claim 24, wherein After the first core network device receives the second request sent by the terminal, it further includes: The first core network device selects the second core network device corresponding to the second session based on at least one of the second indication, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; The first core network device saves the identifier of the second core network device corresponding to the second session.

26. The method according to claim 25, wherein, The method further includes: The first core network device sends fourth information to the second core network device, where the fourth information includes at least one of the following: the second indication, the identifier of the second session, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; The first core network device receives fifth information sent by the second core network device, where the fifth information includes at least one of the following: the identifier of the second session, MASSS rules.

27. The method according to claim 26, wherein After the first core network device receives the fifth information sent by the second core network device, it further includes: The first core network device sends a second response to the terminal, where the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: the identifier of the second session, MASSS rules.

28. The method according to any one of claims 20, 21, 26, and 27, wherein, The MASSS rules are used to configure at least one of the access technology, access mode, and conditions for switching paths used by the terminal to select uplink data corresponding to multiple sessions, and the multiple sessions include at least one of the following: the first session, the second session.

29. A terminal, including: A first communication unit, configured to send a first request to a first core network device, where the first request is used to establish or modify a first session corresponding to a first user equipment UE, and the first request carries the identifier of a second session corresponding to a second UE, and the identifier of the second session is used for the first core network device to select the second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

30. The terminal according to claim 29, wherein, The first request further carries a first indication, where the first indication is used to indicate that the first session is for multi-access steering, handover, and splitting MASSS.

31. The terminal according to claim 29 or 30, wherein, The first request further carries at least one of the following: the globally unique temporary UE identifier GUTI of the second UE, the subscriber permanent identifier SUPI of the second UE.

32. The terminal according to any one of claims 29-31, wherein, The first request further carries at least one of the following: the identifier of the first session; the data network name DNN corresponding to the first session; the single network slice selection assistance information S-NSSAI corresponding to the first session.

33. The terminal according to any one of claims 29-32, wherein, The first communication unit is configured to receive a first response sent by the first core network device, where the first response is used to indicate the completion of establishing or modifying the first session, and the first response carries at least one of the following: an identifier of the first session, a MASSS rule.

34. The terminal according to any one of claims 29-33, wherein, The first communication unit is configured to perform one of the following: Send a second request to the first core network device, where the second request is used to establish or modify the second session; send the second request to a third core network device.

35. The terminal according to claim 34, wherein, The second request carries at least one of the following: a second indication, where the second indication is used to indicate that the second session is for MASSS; an identifier of the second session; a DNN corresponding to the second session; an S-NSSAI corresponding to the second session.

36. The terminal according to claim 34 or 35, wherein, The first communication unit is configured to perform one of the following: Receive a second response sent by the first core network device, where the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: an identifier of the second session, a MASSS rule; receive the second response sent by the third core network device.

37. The terminal according to claim 33 or 36, wherein, The MASSS rule is used to configure at least one of an access technology, an access mode, and conditions for a handover path used by the terminal to select uplink data corresponding to multiple sessions, where the multiple sessions include at least one of the following: the first session, the second session.

38. A first core network device, comprising: A second communication unit, configured to receive a first request sent by a terminal, where the first request is used to establish or modify a first session corresponding to a first user equipment (UE), the first request carries an identifier of a second session corresponding to a second UE, and the identifier of the second session is used to select a second core network device corresponding to the second session, and the terminal includes the first UE and the second UE.

39. The first core network device according to claim 38, wherein, The first core network device further comprises: A second processing unit, configured to obtain an identifier of the second core network device based on the identifier of the second session.

40. The first core network device according to claim 39, wherein, The second processing unit is configured to obtain the identifier of the second core network device from the session context of the second session when it is determined that the session context of the second session is locally stored based on the identifier of the second session and the SUPI of the second UE.

41. The first core network device according to claim 39, wherein, The second communication unit is configured to send first information to a fourth core network device, where the first information includes the identifier of the second session and the SUPI of the second UE; receive the identifier of the second core network device sent by the fourth core network device.

42. The first core network device according to claim 41, wherein, The first information further includes a first indication.

43. The first core network device according to any one of claims 40-42, wherein, The first request further carries at least one of the following: a globally unique temporary UE identifier (GUTI) of the second UE, the SUPI of the second UE.

44. The first core network device according to claim 43, wherein, When the first request carries the GUTI of the second UE, the SUPI of the second UE is determined based on the GUTI of the second UE.

45. The first core network device according to any one of claims 40-42, wherein, The second communication unit is configured to obtain the SUPI of the second UE from the fourth core network device based on the identifier of the first UE.

46. The first core network device according to any one of claims 38-45, wherein, The first request further carries a first indication.

47. The first core network device according to any one of claims 38-46, wherein, The first request also carries at least one of the following: the identifier of the first session; the data network name (DNN) corresponding to the first session; the single network slice selection assistance information (S-NSSAI) corresponding to the first session.

48. The first core network device according to any one of claims 38-47, wherein, The second communication unit is configured to send second information to the second core network device, where the second information includes at least one of the following: a first indication, the identifier of the second session, the GUTI of the second UE, the SUPI of the second UE, the identifier of the first session, the DNN corresponding to the first session, the S-NSSAI corresponding to the first session; and receive third information sent by the second core network device, where the third information includes at least one of the following: the identifier of the first session, multi-access steering, handover and split (MASSS) rules.

49. The first core network device according to claim 48, wherein, The second communication unit is configured to send a first response to the terminal, where the first response is used to indicate the completion of establishing or modifying the first session, and the first response carries at least one of the following: the identifier of the first session, MASSS rules.

50. The first core network device according to any one of claims 42, 46, 48, and 49, wherein, The first indication is used to indicate that the first session is for MASSS.

51. The first core network device according to any one of claims 38 - 40, wherein, The second communication unit is configured to receive a second request sent by the terminal, where the second request is used to establish or modify the second session.

52. The first core network device according to claim 51, wherein, The second request carries at least one of the following: a second indication, where the second indication is used to indicate that the second session is for MASSS; the identifier of the second session; the DNN corresponding to the second session; the S-NSSAI corresponding to the second session.

53. The first core network device according to claim 52, wherein, The second processing unit is configured to select the second core network device corresponding to the second session based on at least one of the second indication, the DNN corresponding to the second session, and the S-NSSAI corresponding to the second session; Save the identifier of the second core network device corresponding to the second session.

54. The first core network device according to claim 53, wherein, The second communication unit is configured to send fourth information to the second core network device, where the fourth information includes at least one of the following: the second indication, the identifier of the second session, the DNN corresponding to the second session, the S-NSSAI corresponding to the second session; and receive fifth information sent by the second core network device, where the fifth information includes at least one of the following: the identifier of the second session, MASSS rules.

55. The first core network device according to claim 54, wherein, The second communication unit is configured to send a second response to the terminal, where the second response is used to indicate the completion of establishing or modifying the second session, and the second response carries at least one of the following: the identifier of the second session, MASSS rules.

56. The first core network device according to any one of claims 48, 49, 54, and 55, wherein, The MASSS rules are used to configure at least one of the access technology, access mode, and conditions for the handover path used by the terminal to select the uplink data corresponding to multiple sessions, where the multiple sessions include at least one of the following: the first session, the second session.

57. A terminal, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver being configured to communicate with other devices, and the processor being configured to call and run the computer program stored in the memory, so that the terminal executes the method according to any one of claims 1 to 9.

58. A first core network device, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver being configured to communicate with other devices, and the processor being configured to call and run the computer program stored in the memory, so that the first core network device executes the method according to any one of claims 10 to 28.

59. A chip, comprising: A processor for calling and running a computer program from a memory, such that a device installed with the chip executes the method according to any one of claims 1 to 9, or claims 10 to 28.

60. A computer-readable storage medium for storing a computer program, which when run on a device causes the device to execute the method according to any one of claims 1 to 9, or claims 10 to 28.

61. A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 9, or claims 10 to 28.

62. A computer program that causes a computer to execute the method according to any one of claims 1 to 9, or claims 10 to 28.

Images