Communication method and device

Abstract

The invention relates to a communication method, equipment, a computer readable storage medium, a computer program product and a computer program. The method comprises the steps that a first terminal sends first information, the first information is used for requesting to distribute a first context of the first terminal, and the first context of the first terminal is related to at least part of the context of a second terminal.

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] With the development and popularization of electronic devices, users have access to a wide range of different terminal types. Each terminal has its own advantages, and the same user may use different electronic devices in different situations. However, how to switch the same service between different terminals and achieve multi-terminal collaboration on different devices has become a problem that needs to be solved.

[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] An embodiment of the present application provides a communication method, including:

[0006] A first terminal sends first information, where the first information is used to request allocation of a first context of the first terminal, and the first context of the first terminal is related to at least a portion of a context of a second terminal.

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

[0008] The first network device receives first information, wherein the first information is used to request allocation of a first context of a first terminal, where the first context of the first terminal is related to at least a portion of a context of a second terminal.

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

[0010] The second terminal sends a third indication message, wherein the third indication message is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the current terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the current terminal.

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

[0012] The second network device receives third indication information, wherein the third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the current terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the current terminal.

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

[0014] The first communication unit is configured to send first information, wherein the first information is used to request allocation of a first context of the first terminal, where the first context of the first terminal is related to at least a portion of a context of the second terminal.

[0015] An embodiment of the present application provides a first network, including:

[0016] The second communication unit is configured to receive first information, wherein the first information is used to request allocation of a first context of a first terminal, and the first context of the first terminal is related to at least a portion of the context of the second terminal.

[0017] An embodiment of the present application provides a second terminal device, including:

[0018] A third communication unit is used to send a third indication information, wherein the third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

[0019] An embodiment of the present application provides a second network device, including:

[0020] A fourth communication unit is used to receive third indication information, wherein the third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

[0021] An embodiment of the present application provides a first terminal, 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 terminal executes the above method.

[0022] An embodiment of the present application provides a first 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 network device executes the above method.

[0023] An embodiment of the present application provides a second 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 execute the computer program stored in the memory, so that the second terminal performs the above method.

[0024] An embodiment of the present application provides a second network device, 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 execute the computer program stored in the memory, so that the second network device performs the above method.

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

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

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

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

[0029] By adopting the solution provided in this embodiment, the first terminal can request that a context related to at least part of the context of the second terminal be assigned to it by sending the first information. Thus, by assigning the context related to the second terminal to the first terminal, at least part of the second terminal's services can be migrated to a different device, thereby achieving the effect of coordinating the same service on multiple devices, and ensuring service continuity while achieving service migration. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0031] Figure 2 is a schematic diagram of the 5GC system.

[0032] FIG3 is a schematic diagram of the QoS mechanism in the network architecture of the relevant protocols.

[0033] FIG4 is a schematic diagram of scenarios in which the same user uses different electronic devices in different situations.

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

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

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

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

[0038] FIG9 is a schematic diagram of a scenario of allocating context according to an embodiment of the present application.

[0039] 10 to 13 are various exemplary flow charts of the processing flow of the communication method according to the embodiment of the present application.

[0040] FIG14 is a schematic block diagram of a first terminal according to an embodiment of the present application.

[0041] FIG15 is a schematic block diagram of a first network device according to an embodiment of the present application.

[0042] FIG16 is a schematic block diagram of a second terminal according to an embodiment of the present application.

[0043] FIG17 is a schematic block diagram of a second network device according to an embodiment of the present application.

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

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

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

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

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

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

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

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

[0052] 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 device. 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.

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

[0054] 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 security context 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 a 5G core network that 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 the 5GC nodes, between the UE and the Radio Access Network (RAN), and between the RAN and the 5GC nodes through corresponding interfaces. For example, as shown in Figure 2: Data is transmitted between the AMF and NSSF in the 5GC through interface N22; the AMF transmits data to the SMF through interface N11; the AMF transmits data to the AUSF through N12; and the AMF transmits data to the UDM through interface N8. Data is transmitted between the SMF and the UPF through interface N4. The UPF transmits data to the external data network through interface N6 and to the AN through interface N3. The UE establishes an access layer connection with the AN through the Uu port, exchanges access layer messages and wireless data transmission, and establishes a non-access layer (NAS) connection with the AMF through the N1 port, 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 described one by one.

[0055] Currently, when the UE performs the registration process and the PDU session establishment process, the core network elements such as AMF and SMF will generate a context for the UE based on the corresponding subscription information (such as access and mobility subscription, session management context, network slicing subscription, etc.) of the SUPI in the UDM according to the subscription information and local configuration policies. AM context and SM Context are the two most important contexts, generated by AMF and SMF respectively. The main contents include the following: UE context in AMF (UE context in AMF) and SM context (session management context). It should be understood that the context that can be generated for the same UE can include at least one of the two types of UE context in AMF (UE context in AMF) and SM context (session management context) mentioned above.

[0056] As shown in Table 1 below, the main parts of the UE context in the AMF include at least one of the following: access frequency point related information (for example, the RFSP Index in Use in Table 1 may include access frequency point related information), paging related information (for example, it may include DRX related information, and the DRX related information may include at least one of the UE Specific DRX Parameters in Table 1, UE Specific DRX Parameters for NB-IoT, Extended idle mode DRX Parameters, etc.), mobility restriction information, location related information (such as TAI list and User location in Table 1), UE temporary identification information (such as 5G-GUTI in Table 1), access management (AM) policy association information (PCF of the service (such as PCF ID in Table 1) and the established association (such as AM Policy Information in Table 1)), UE policy association information, UE's NWDAF association information, allowed network slices (such as 5G-GUTI in Table 1), and the like. The UE context in AMF may include: S-NSSAI) information (such as the Allowed NSSAI in Table 1, which consists of one or more S-NSSAIs), parameters for each PDU session (such as the S-NSSAI, DNN, SMF information, Network Slice Instance ID, Access Type in Table 1), etc. It should be pointed out that the above is only an exemplary description of the possible contents of the UE context in the AMF. In fact, the more fine-grained contents that the UE context in the AMF may contain can be found in Table 1, but they are not described here one by one.

[0057] Table 1

[0058] The specific parameters of the session management context (SM context) are shown in Table 2 below. The main parts include at least one of the following: UE identification information (such as SUPI in Table 2), attribute parameters of the PDU session (such as S-NSSAI, DNN, PDU session identifier, etc. in Table 2), information on interaction with the application server (such as DNAI, UE IP address in Table 2), QoS parameter information of each QoS data flow (such as 5QI, ARP, etc. in Table 2), data flow description (such as TFT) and binding information, EPS bearer mapping information, etc. It should be pointed out that the above is only an exemplary description of part of the content of the SM context. In fact, the more fine-grained content that the SM context may contain can be found in Table 2, but they are not described here one by one.

[0059] Table 2

[0060] The QoS mechanism in the network architecture of the relevant protocols is as follows: The core network element (SMF) determines PCC rules based on policy information, subscription information, and local configuration. Based on the PCC rules, it generates QoS rules, PDRs (Packet Detection Rules), and QoS parameters. QoS rules are used by the UE to bind uplink service data flows to QoS flows, while PDRs are used by the UPF to bind downlink service data flows to QoS flows. QoS parameters are used to generate each QoS flow. These QoS parameters are sent to the RAN to generate the corresponding DRBs for the QoS flow, ensuring end-to-end transmission quality (both on the air interface and the core network). For example, in uplink transmission, the UE receives data packets from applications, maps them to QoS flows based on QoS rules, and applies a QoS flow marking. The UE then marks all packets in the QoS flow with the same QFI, maps the QoS flow to AN resources, and sends it to the AN. The RAN (i.e., the AN shown in Figure 3) converts the QoS flows mapped to AN resources (i.e., the AN resources corresponding to each QoS flow generated by the AN based on QoS parameters) into PDU sessions, which are then sent to the UPF. In downlink transmission, the PDF side receives data packets from the application, classifies the data packets based on the PDR for QoS flow marking and other operations, marks all data packets in the QoS flow with the same QFI, combines the QoS flow into a PDU session, and sends the PDU session to the RAN (i.e., the AN shown in Figure 3). The RAN side transmits the received PDU (Protocol Data Unit) session to the UE side through AN resources.

[0061] With the development and popularization of electronic devices, there are now many different types of terminals available for consumer use, each with its own advantages. For example, as shown in Figure 4, users can own multiple electronic devices simultaneously, but different electronic devices may have different advantages and disadvantages. For example, in Figure 4, a mobile phone is a frequently used device. Its advantages include convenient input, powerful computing power, rich functions (including communication, multimedia, positioning, etc.), extremely high user stickiness, massive storage capacity, and high privacy. Its disadvantages are a small screen, heavy weight and size, and heavy workload. Smart screens have advantages such as high-definition resolution, large screen, fixed location, remote control interaction, and public devices. However, their disadvantages are immobility, inconvenient interaction, and insufficient privacy. Watches have the advantages of being convenient, wearable, portable, small screen, good touch, physiological data detection, and private devices. However, their disadvantages are that they are not suitable for complex interactions and content. Tablets have the advantages of good touch and large screen size, but their disadvantages are large size and weight, making them difficult to carry around. AR / VR has the advantages of good display and high privacy, but their disadvantages are low computing power and unstable wearing comfort. The same user may use different electronic devices in different occasions. However, how to enable the same service to be switched freely between different terminals, and how to achieve multi-terminal collaboration for specific users and / or specific services on different devices based on scenario needs by supporting communication, computing and business continuity requirements to provide the best business experience, have become problems that need to be solved.

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

[0063] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0064] Figure 5 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.

[0065] S510: A first terminal sends first information, where the first information is used to request allocation of a first context of the first terminal, and the first context of the first terminal is related to at least a portion of a context of a second terminal.

[0066] Figure 6 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.

[0067] S610: A first network device receives first information, where the first information is used to request allocation of a first context of a first terminal, and the first context of the first terminal is related to at least a portion of a context of a second terminal.

[0068] Figure 7 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.

[0069] S710: The second terminal sends third indication information, where the third indication information is used to indicate that the second terminal has a first capability, where the first capability includes at least one of the following: an ability to allocate at least part of the context-related context of one or more other terminals to the terminal itself, and an ability to allocate at least part of the context-related context of the terminal itself to one or more other terminals. Here, the terminal itself may be the second terminal.

[0070] FIG8 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.

[0071] S810. The second network device receives third indication information, where the third indication information is used to indicate that the second terminal has a first capability, where the first capability includes at least one of the following: an ability to support or allow acquisition of context related to at least part of the context of one or more other terminals, and an ability to support or allow one or more other terminals to acquire context related to at least part of the context of the current terminal. Here, the current terminal may be the second terminal.

[0072] Here, the first network device may be any device serving the first terminal. In one embodiment, the first network device may be a first access network device serving the first terminal. In one embodiment, the first network device may be a first core network device serving the first terminal, for example, the first network device may be a first access and mobility management function (AMF) or a first session management function (SMF). It should be understood that the above is only an exemplary description. In actual processing, the first network device is not limited to the network elements of the core network listed above, and all possible network elements of the first network device are not exhaustively listed here.

[0073] The second network device can be any device serving the second terminal. In one embodiment, the second network device can be a second access network device serving the second terminal. In one embodiment, the second network device can be a second core network device serving the second terminal, for example, the second network device can be a second AMF or a second SMF. It should be understood that the above is merely an example. In actual processing, the second network device is not limited to the core network network elements listed above, and all possible network elements of the second network device are not exhaustively listed here.

[0074] The first terminal and the second terminal may be 3GPP terminals, ie, terminals that can access a 3GPP network to send and receive data. This embodiment does not exhaustively list or limit various possible types of the first terminal and the second terminal.

[0075] In some embodiments, the network devices serving the first terminal and the network devices serving the second terminal are the same, that is, the first network device and the second network device can be the same. In such embodiments, the first network device and the second network device may not be distinguished. For example, the first network device can serve the first terminal and the second terminal. In some embodiments, the network devices serving the first terminal and the network devices serving the second terminal are different, that is, the first network device and the second network device are different.

[0076] In some possible implementations, the network side (for example, a first network device serving the first terminal and the second terminal, or a second network device serving the second terminal) has allocated a context related to the second terminal. This implementation describes the relevant processing of the first terminal in this state.

[0077] The first terminal sending the first information may specifically include: the first terminal sending the first information to the first network device. Correspondingly, the first network device receiving the first information may specifically include: the first network device receiving the first information sent by the first terminal.

[0078] The first information may be carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message. It should be understood that, while any one of the registration request message, the registration update message, the session establishment request message, and the session modification request message carries the first information, it may also carry the content required to be carried by the registration request message, the registration update message, the session establishment request message, and the session modification request message according to the original protocol, but this embodiment does not exhaustively list and limit them. For example, if the registration request message carries the first information, then in addition to carrying the first information, the registration request message may also carry other information specified by the relevant protocol. For example, the registration request message may also carry at least one of the following: UE ID (such as IMSI or SUPI), network slice identifier (such as Single Network Slice Selection Assistance information (S-NSSAI, single network slice selection assistance information)), etc.; this embodiment does not exhaustively list the various types of information and functions that may be carried by the registration request message as specified by the protocol. The description of the other messages is similar to that of the registration request message and will not be repeated one by one.

[0079] The first information may specifically include first request information, where the first request information is used to request allocation of a first context for the first terminal; more specifically, the first request information may be used to request a first network device to allocate the first context for the first terminal.

[0080] After the first network device receives the first information, the method further includes: the first network device acquiring a context related to the second terminal; and the first network device generating a context of the first terminal based on the context related to the second terminal.

[0081] Optionally, the first network device obtaining the context related to the second terminal may include: the first network device obtaining a locally stored context related to the second terminal. Here, the first network device serves the first terminal and the second terminal.

[0082] Optionally, the first network device obtains the context related to the second terminal, including one of the following: the first network device sends fourth information to the second network device, receives the context related to the second terminal sent by the second network device, wherein the fourth information is used to request the acquisition of the context related to the second terminal; the first network device sends fifth information to the third network device, receives the context related to the second terminal sent by the third network device, wherein the fifth information is used to request the acquisition of the context related to the second terminal. The first network device serves the first terminal; the second network device serves the second terminal; and the third network device is used to store the context related to the second terminal. The fourth information includes a first identifier, and / or the fifth information includes a first identifier. The third network device includes at least one of the following: a unified data management function (UDM) or a unified data repository function (UDR).

[0083] In some possible embodiments, the context related to the second terminal includes at least one of the following: the context corresponding to the second terminal; the context corresponding to the first service run by the second terminal; the context corresponding to the first user using the second terminal; the context corresponding to the first protocol data unit (PDU) session of the second terminal; and the context corresponding to the first quality of service (QoS) flow of the second terminal.

[0084] In some possible implementations, the first information includes a first identifier, that is, the first information includes the first identifier and the first request information. The first identifier includes at least one of the following: an identifier of the second terminal, an identifier of the first service, an identifier of the first user, an identifier of the first PDU session, or an identifier of the first QoS flow.

[0085] In some embodiments, the first identification includes only an identification of the second terminal.

[0086] The identifier of the second terminal may include, but is not limited to, at least one of the following: the SUPI (Subscription Permanent Identifier) ​​of the second terminal, the SUCI (Subscription Concealed Identifier) ​​of the second terminal, the PEI (Permanent Equipment Identifier) ​​of the second terminal, the 5G-GUTI (5G Globally Unique Temporary Identifier) ​​of the second terminal, the Internal-Group Identifier (IGI) of the second terminal, the GPSI (Generic Public Subscription Identifier) ​​of the second terminal, etc. SUPI is a globally unique 5G user permanent identifier that should be assigned to each user in the 5G system and configured in the UDM / UDR. SUPI is only used within the 3GPP system. SUPI may include: IMSI (International Mobile Subscriber Identity), or an identifier for a specific network, which can be used for a private network. SUCI is a privacy-preserving identifier that includes a hidden SUPI. The format supported by the PEI parameter is IMEI (International Mobile Station Equipment Identity).

[0087] In this embodiment, the context related to the second terminal obtained by the first network device based on the identifier of the second terminal may refer to the context corresponding to the second terminal. The context corresponding to the second terminal may be part or all of the context corresponding to the second terminal. Further, the context corresponding to the second terminal may be a context of the second terminal or all of the context that can be assigned to other terminals.

[0088] In an example, the process of the first network device acquiring the context related to the second terminal may include: when the first network device determines that the context corresponding to the second terminal is locally stored based on the identifier of the second terminal, acquiring the locally stored context corresponding to the second terminal.

[0089] In one example, the processing of the first network device obtaining the context related to the second terminal may include: when the first network device determines based on the identifier of the second terminal that the context corresponding to the second terminal is not stored locally, the first network device sends fourth information to the second network device and receives the context corresponding to the second terminal sent by the second network device; the fourth information may include the identifier of the second terminal.

[0090] Accordingly, the processing of the second network device may include: based on the identifier of the second terminal in the fourth information, locally acquiring the context corresponding to the second terminal, and feeding back the context corresponding to the second terminal to the first network device.

[0091] The first network device may determine the second network device by determining the second network device corresponding to the second terminal based on the identifier of the second terminal. This embodiment does not limit the specific determination method.

[0092] In one example, the process of the first network device acquiring the context related to the second terminal may include: when the first network device determines, based on the identifier of the second terminal, that the context corresponding to the second terminal is not locally stored, the first network device sending fifth information to a third network device, and receiving the context corresponding to the second terminal sent by the third network device. The fifth information may include the identifier of the second terminal.

[0093] Correspondingly, the processing of the third network device may include: the third network device obtains the context corresponding to the second terminal locally based on the identifier of the second terminal in the fifth information, and feeds back the context corresponding to the second terminal to the first network device; or, the third network device determines the second network device corresponding to the second terminal based on the identifier of the second terminal in the fifth information, obtains the context corresponding to the second terminal from the second network device, and feeds back the context corresponding to the second terminal to the first network device.

[0094] In some embodiments, the first identifier only includes an identifier of the first service.

[0095] The identifier of the first service may include at least one of the following: a name of the first service, an ID of the first service, a number of the first service, etc. It should be understood that the identifier of the first service may also be replaced by an identifier of the first application, such as a name of the first application, an ID of the first application, a number of the first application, etc.

[0096] In this embodiment, the context related to the second terminal obtained by the first network device based on the identifier of the first service may refer to the context corresponding to the first service running on the second terminal, that is, the context corresponding to the first service contained in the context corresponding to the second terminal. Alternatively, the context related to the second terminal obtained by the first network device based on the identifier of the first application may refer to the context corresponding to the first application running on the second terminal, that is, the context corresponding to the first application contained in the context corresponding to the second terminal. For the sake of simplicity, this embodiment will be described below using only the first service as an example. The descriptions related to the first service below can be replaced with the first application, but will not be repeated.

[0097] In one example, the processing of the first network device obtaining the context related to the second terminal may include: the first network device determines, based on the identifier of the first service, that the context corresponding to the first service run by the second terminal is locally stored, and then obtains the context corresponding to the first service run by the second terminal that is locally stored.

[0098] The processing of the first network device determining whether the context corresponding to the first service run by the second terminal is stored locally based on the identifier of the first service may include: the first network device determining whether there are one or more other terminals running the first service and having a binding relationship with the first terminal locally based on the identifier of the first service; if so, using one of the one or more other terminals running the first service and having a binding relationship with the first terminal as the second terminal, and determining that the context corresponding to the first service run by the second terminal is stored locally.

[0099] The one or more other terminals that have a binding relationship with the first terminal may be pre-stored on the first network device. This embodiment does not limit the manner in which the first network device obtains or obtains the binding relationship between the first terminal and the one or more other terminals. Here, the binding relationship can also be alternatively described as an association relationship, a correlation, etc. This embodiment does not exhaustively list or limit all possible descriptions of the binding relationship. It should be noted that the one or more other terminals refer to other terminals different from the first terminal.

[0100] There are two situations in which one of the one or more other terminals that run the first service and have a binding relationship with the first terminal is used as the second terminal: in one situation, there is only one other terminal that runs the first service and has a binding relationship with the first terminal, and the other terminal is directly used as the second terminal. In another situation, there are multiple other terminals that run the first service and have a binding relationship with the first terminal. In this case, other terminals that meet the first preset conditions can be selected from the multiple other terminals as the second terminal. The first preset condition may include at least one of the following: the context corresponding to the designated terminal and the first service is recently or newly generated. The designated terminal may be pre-configured or default, for example, the designated terminal may be a smartphone, or the designated terminal may be a laptop, etc. All possible types of designated terminals are not exhaustively listed here.

[0101] In one example, the first network device may obtain the context related to the second terminal by processing: based on the identifier of the first service, if the first network device determines that there are no one or more other terminals locally running the first service and having a binding relationship with the first terminal, the first network device sends fourth information to the second network device, and receives the context corresponding to the first service running on the second terminal from the second network device. The fourth information may include the identifier of the first service. Furthermore, the fourth information may also include the identifier of the first terminal.

[0102] Accordingly, the processing of the second network device may include: based on the identifier of the first service in the fourth information, querying locally one or more other terminals that run the first service and have a binding relationship with the first terminal, using one of the one or more other terminals that run the first service and have a binding relationship with the first terminal as the second terminal, extracting the context corresponding to the first service run by the second terminal from the context corresponding to the second terminal, and feeding back the context corresponding to the first service run by the second terminal to the first network device. In this example, the processing of the second network device using one of the one or more other terminals that run the first service and have a binding relationship with the first terminal as the second terminal is similar to the description of the processing of the first network device in the aforementioned example and is not repeated here.

[0103] In one example, the process of the first network device obtaining the context related to the second terminal may include: based on the identifier of the first service, when the first network device determines that there are no one or more other terminals locally running the first service and having a binding relationship with the first terminal, the first network device sends fifth information to a third network device, and receives the context corresponding to the first service running by the second terminal from the third network device. The fifth information may include the identifier of the first service. Furthermore, the fifth information may also include the identifier of the first terminal.

[0104] The processing of the third network device may include: the third network device locally queries one or more other terminals that run the first service and have a binding relationship with the first terminal based on the identifier of the first service in the fifth information, takes one of the one or more other terminals that run the first service and have a binding relationship with the first terminal as the second terminal, extracts the context corresponding to the first service run by the second terminal from the context corresponding to the second terminal, and feeds back the context corresponding to the first service run by the second terminal to the first network device.

[0105] Alternatively, the processing of the third network device may include: the third network device queries one or more other terminals that run the first service and have a binding relationship with the first terminal from multiple candidate network devices based on the identifier of the first service in the fifth information; when it is determined that a second network device among the multiple candidate network devices stores a context corresponding to a second terminal that meets the first preset condition, the third network device extracts the context corresponding to the first service run by the second terminal from the second network device based on the identifier of the first service, and feeds back the context corresponding to the first service run by the second terminal to the first network device.

[0106] In one embodiment, the first identification includes only the identification of the first user.

[0107] The identification of the first user includes at least one of the following: the ID of the first user and the biometric information of the first user. The biometric information may include at least one of the following: fingerprint, facial features, voice features, etc. The biometric information may refer to at least one of the specific feature information of a fingerprint, specific feature information of a facial feature, and specific feature information of a voice feature, or the biometric information may refer to at least one of the fingerprint ID, facial feature ID, and voice feature ID. In this embodiment, the context related to the second terminal obtained by the first network device based on the identification of the first user may refer to the context corresponding to the first user using the second terminal.

[0108] In one example, the processing of the first network device obtaining the context related to the second terminal may include: the first network device determines, based on the identifier of the first user, that the context corresponding to the first user using the second terminal is locally stored, and then obtains the locally stored context corresponding to the first user using the second terminal.

[0109] The processing by which the first network device determines, based on the identifier of the first user, whether a context corresponding to the first user using the second terminal is stored locally may include: the first network device determines, based on the identifier of the first user, whether there are one or more other terminals used by the first user and having a binding relationship with the first terminal locally; if so, one of the one or more other terminals used by the first user and having a binding relationship with the first terminal is used as the second terminal, and determining that a context corresponding to the first user using the second terminal is stored locally.

[0110] There are two situations in which one of the one or more other terminals used by the first user and bound to the first terminal is used as the second terminal: In one situation, there is only one other terminal used by the first user and bound to the first terminal, and the other terminal is directly used as the second terminal. In another situation, there are multiple other terminals used by the first user and bound to the first terminal. In this case, another terminal that meets the second preset condition can be selected from the multiple other terminals as the second terminal. The second preset condition may include at least one of the following: the context corresponding to the designated terminal and the first user is recently or newly generated. The description of the designated terminal is the same as that in the previous embodiment and is not repeated here.

[0111] In one example, the first network device may obtain the context related to the second terminal by processing: based on the identifier of the first user, if the first network device determines that there are no one or more other terminals used by the first user and bound to the first terminal locally, the first network device sends fourth information to the second network device, and receives the context corresponding to the first user using the second terminal from the second network device. The fourth information may include the identifier of the first user. Furthermore, the fourth information may also include the identifier of the first terminal.

[0112] Accordingly, the processing of the second network device may include: based on the identifier of the first user in the fourth information, querying locally one or more other terminals used by the first user and having a binding relationship with the first terminal, using one of the one or more other terminals used by the first user and having a binding relationship with the first terminal as the second terminal, extracting the context corresponding to the first user using the second terminal from the context corresponding to the second terminal and sending it to the first network device. In this example, the processing of the second network device using one of the one or more other terminals used by the first user and having a binding relationship with the first terminal as the second terminal is similar to the description of the processing of the first network device in the aforementioned example and will not be repeated here.

[0113] In one example, the first network device may obtain the context related to the second terminal by processing: based on the identifier of the first user, if the first network device determines that there are no one or more other terminals used by the first user and bound to the first terminal locally, the first network device sends fifth information to a third network device, and receives the context corresponding to the first user using the second terminal from the third network device. The fifth information may include the identifier of the first user. Furthermore, the fifth information may also include the identifier of the first terminal.

[0114] The processing of the third network device may include: the third network device locally queries one or more other terminals used by the first user and having a binding relationship with the first terminal based on the identifier of the first user in the fifth information, uses one of the one or more other terminals used by the first user and having a binding relationship with the first terminal as the second terminal, extracts the context corresponding to the first user using the second terminal from the context corresponding to the second terminal, and feeds back the context corresponding to the first user using the second terminal to the first network device.

[0115] Alternatively, the processing of the third network device may include: the third network device queries one or more other terminals used by the first user and having a binding relationship with the first terminal from multiple candidate network devices based on the identifier of the first service in the fifth information; when it is determined that a second network device among the multiple candidate network devices stores a context corresponding to a second terminal that meets a second preset condition, the third network device extracts the context corresponding to the first user using the second terminal from the second network device based on the identifier of the first service, and feeds back to the first network device the context corresponding to the first service run by the second terminal. The definition of the second preset condition is the same as that in the above example and is not repeated here.

[0116] In some embodiments, the first identifier includes an identifier of the second terminal, and the first identifier also includes at least one of the following: an identifier of the first service, an identifier of the first user, an identifier of the first PDU session, and an identifier of the first QoS flow.

[0117] Optionally, the first identifier may include the identifier of the second terminal and the identifier of the first service, and the context associated with the second terminal includes the context corresponding to the first service running on the second terminal. Optionally, the first identifier may include the identifier of the second terminal and the identifier of the first user, and the context associated with the second terminal includes the context corresponding to the first user using the second terminal. Optionally, the first identifier may include the identifier of the second terminal, the identifier of the first service, and the identifier of the first user, and the context associated with the second terminal includes the context corresponding to the first service running under the identifier of the first user using the second terminal. Optionally, the first identifier may include the identifier of the second terminal and the identifier of the first PDU session, that is, the first identifier is an identifier used to indicate the first PDU session of the second terminal, and the context associated with the second terminal includes the context corresponding to the first PDU session of the second terminal. Optionally, the first identifier may include the identifier of the second terminal and the identifier of the first QoS flow, that is, the first identifier is an identifier used to indicate the first QoS flow of the second terminal, and the context associated with the second terminal includes the context corresponding to the first QoS flow of the second terminal. Optionally, the first identifier may include the identifier of the second terminal, the identifier of the first PDU session, and the identifier of the first QoS flow, and the context associated with the second terminal includes the context corresponding to the first QoS flow of the first PDU session of the second terminal.

[0118] It should be understood that the above is only an exemplary explanation. In actual processing, different combinations of the contents of the first identifier can correspond to different contexts related to the second terminal. However, an exhaustive list is not given here. As long as at least one of the first identifiers is included and at least one context related to the second terminal is obtained, it is within the scope of protection of this embodiment.

[0119] In one example, the process of the first network device obtaining the context related to the second terminal may include, when the first network device determines that the context corresponding to the second terminal is locally stored based on the identifier of the second terminal included in the first identifier, the first network device obtains the locally stored context related to the second terminal based on at least one of the identifier of the first service, the identifier of the first user, the identifier of the first PDU session, and the identifier of the first QoS flow included in the first identifier. The specific content of the context related to the second terminal corresponding to different combinations of first identifiers is the same as the above example, and therefore will not be repeated one by one.

[0120] In one example, the process of the first network device obtaining the context related to the second terminal may include: when the first network device determines that the context corresponding to the second terminal is not stored locally based on the identifier of the second terminal included in the first identifier, the first network device sends fourth information to the second network device and receives the context corresponding to the second terminal sent by the second network device; the first network device obtains the context related to the second terminal from the context corresponding to the second terminal based on at least one of the identifier of the first service, the identifier of the first user, the identifier of the first PDU session, and the identifier of the first QoS flow included in the first identifier; the fourth information may include the identifier of the second terminal. Accordingly, the process of the second network device may include: based on the identifier of the second terminal in the fourth information, obtaining the context corresponding to the second terminal from the local computer, and feeding back the context corresponding to the second terminal to the first network device.

[0121] In one example, the process of the first network device obtaining the context related to the second terminal may include: when the first network device determines that the context corresponding to the second terminal is not stored locally based on the identifier of the second terminal included in the first identifier, the first network device sends fourth information to the second network device and receives the context related to the second terminal sent by the second network device; the fourth information may include all the contents of the first identifier, for example, the first identifier includes the identifier of the second terminal, and the first identifier also includes at least one of the identifier of the first service, the identifier of the first user, the identifier of the first PDU session, and the identifier of the first QoS flow. Accordingly, the process of the second network device may include: the second network device obtains the context corresponding to the second terminal stored locally based on the identifier of the second terminal in the first identifier, and obtains the context related to the second terminal from the context corresponding to the second terminal based on at least one of the identifier of the first service, the identifier of the first user, the identifier of the first PDU session, and the identifier of the first QoS flow included in the first identifier, and sends the context related to the second terminal to the first network device.

[0122] In one example, the process of the first network device obtaining the context related to the second terminal may include: when the first network device determines that the context corresponding to the second terminal is not stored locally based on the identifier of the second terminal included in the first identifier, the first network device sends fifth information to the third network device and receives the context related to the second terminal sent by the third network device; the fifth information may include all the contents of the first identifier, for example, the first identifier includes the identifier of the second terminal, and the first identifier also includes at least one of the identifier of the first service, the identifier of the first user, the identifier of the first PDU session, and the identifier of the first QoS flow.

[0123] Correspondingly, the processing of the third network device may include: the third network device obtains the context corresponding to the second terminal locally based on the identifier of the second terminal in the fifth information, and obtains the context related to the second terminal from the context corresponding to the second terminal based on at least one of the identifier of the first service, the identifier of the first user, the identifier of the first PDU session, and the identifier of the first QoS flow contained in the first identifier, and sends it to the first network device; or, the third network device determines the second network device corresponding to the second terminal based on the identifier of the second terminal in the fifth information, and obtains the context related to the second terminal from the second network device based on at least one of the identifier of the first service, the identifier of the first user, the identifier of the first PDU session, and the identifier of the first QoS flow contained in the first identifier, and sends it to the first network device.

[0124] In various possible examples where the first information includes the first request information and contains the first identifier, the context related to the second terminal may be obtained through a third network device; accordingly, before the first network device sends the fifth information to the third network device, it may also include: the first network device determines the third network device. Exemplarily, the first network device determines the third network device, which may refer to: the first network device determines the corresponding third network device based on the first identifier. That is, there may be multiple network devices on the core network side, and the first network device may select one from one or more candidate network devices as the third network device. The selected third network device may refer to any one of the one or more candidate network devices that can obtain or save the context information corresponding to the first identifier.

[0125] In some possible embodiments, the first information only includes the first request information and does not include the first identifier. In this embodiment, the context related to the second terminal may include the context corresponding to the second terminal.

[0126] It should be noted that if the first network device pre-configures or defaults at least one of the following: the identifier of the first service, the identifier of the first user, the identifier of the first PDU session, and the identifier of the first QoS flow, then the context related to the second terminal may also include at least one of the following: the context corresponding to the first service running on the second terminal; the context corresponding to the first user using the second terminal; the context corresponding to the first PDU session of the second terminal; the context corresponding to the first QoS flow of the second terminal. For example, the first service may be a specified service pre-configured on the first network device, and the first network device may default to obtaining the context corresponding to the specified service running on the second terminal. All possible situations are not enumerated here.

[0127] For the sake of convenience, the following description is given by taking the context related to the second terminal including the context corresponding to the second terminal as an example:

[0128] In an example, the process of the first network device acquiring the context related to the second terminal may include: when the first network device determines that the context corresponding to the second terminal is stored locally, the first network device acquires the locally stored context related to the second terminal.

[0129] In one example, the process of the first network device determining whether the context corresponding to the second terminal is stored locally may include: the first network device determining whether there are one or more other terminals with a binding relationship with the first terminal locally; if so, one of the one or more other terminals with a binding relationship with the first terminal is used as the second terminal, and determining that the context corresponding to the second terminal is stored locally. Here, there are two situations in which one of the one or more other terminals with a binding relationship with the first terminal is used as the second terminal: in one situation, there is only one other terminal with a binding relationship with the first terminal, and the other terminal is directly used as the second terminal; in another situation, there are multiple other terminals with a binding relationship with the first terminal, and other terminals among the multiple other terminals that meet a third preset condition can be used as the second terminal. The third preset condition may include at least one of the following: the context is a recently or newly generated, specified terminal.

[0130] In one example, the processing of the first network device obtaining the context related to the second terminal may include: when the first network device determines that the context corresponding to the second terminal is not stored locally, the first network device sends fourth information to the second network device, and receives the context corresponding to the second terminal sent by the second network device; the fourth information may include the first request information, and may also include the identifier of the first terminal.

[0131] Accordingly, the processing of the second network device may include: determining one or more other terminals with a binding relationship with the first terminal based on the fourth information, using one of the one or more other terminals with a binding relationship with the first terminal as the second terminal, and sending the context corresponding to the second terminal to the first network device. Here, the processing of the second network device using one of the one or more other terminals with a binding relationship with the first terminal as the second terminal is the same as the above example and is not further described.

[0132] In one example, the first network device obtaining the context associated with the second terminal may include: if the first network device determines that the context corresponding to the second terminal is not locally stored, the first network device sending fifth information to a third network device, and receiving the context corresponding to the second terminal from the third network device. The fifth information may include the first request information and may also include an identifier of the first terminal.

[0133] Accordingly, the processing of the third network device may include: the third network device determines one or more other terminals with a binding relationship with the first terminal based on the fifth information, uses one of the one or more other terminals with a binding relationship with the first terminal as the second terminal, and sends the context corresponding to the second terminal to the first network device. Alternatively, the processing of the third network device may include: the third network device determines one or more other terminals with a binding relationship with the first terminal based on the fifth information, uses one of the one or more other terminals with a binding relationship with the first terminal as the second terminal, determines the second network device corresponding to the second terminal, obtains the context corresponding to the second terminal from the second network device, and feeds back the context corresponding to the second terminal to the first network device.

[0134] The above is an exemplary explanation based on the example of the context related to the second terminal including the context corresponding to the second terminal. Regarding the case where the context related to the second terminal includes other finer-grained contexts, the difference from the case where the context related to the second terminal includes the context corresponding to the second terminal is that the first network device (or the second network device, or the third network device) needs to further extract the context of corresponding granularity from the context corresponding to the second terminal based on at least one of the identifier of the first service, the identifier of the first user, the identifier of the first PDU, and the identifier of the first QoS flow when executing the processing of each example, so it is not repeated here.

[0135] Regarding the various embodiments in which the first network device obtains the context related to the second terminal, it should also be noted that if the first network device receives the context related to the second terminal from the second network device, the second network device may also directly release or delete the context related to the second terminal, or the second network device may also maintain or save the context related to the second terminal. If the first network device receives the context related to the second terminal from the third network device, the third network device may also directly delete the context related to the second terminal, or the third network device may also maintain or save the context related to the second terminal. If the first network device receives the context related to the second terminal from the third network device, and the third network device extracts the context related to the second terminal from the second network device, the second network device and the third network device may also directly delete the context related to the second terminal, or the second network device and the third network device may also maintain or save the context related to the second terminal. Various possible implementation methods of the second network device and the third network device are not exhaustively listed and limited here.

[0136] In some possible implementations, the first context of the first terminal includes at least one of the following: a first portion of parameters in a context related to the second terminal; and related parameters of a second portion of parameters in a context related to the second terminal.

[0137] The second terminal-related context may include: a second terminal-related context that can be assigned to one or more terminals other than the second terminal. It should be noted that the second terminal-related context that can be assigned to one or more terminals other than the second terminal does not necessarily include all of the second terminal's contexts. For example, in some possible scenarios, the second terminal's all contexts may include, in addition to the second terminal-related context that can be assigned to one or more terminals other than the second terminal, other contexts of the second terminal. Such other contexts of the second terminal refer to contexts of the second terminal that cannot be assigned to one or more terminals other than the second terminal.

[0138] Similarly, the first context of the first terminal includes the first portion of parameters in the context associated with the second terminal, and / or related parameters of the second portion of parameters in the context associated with the second terminal. In some possible cases, in addition to the first portion of parameters in the context associated with the second terminal, and / or related parameters of the second portion of parameters in the context associated with the second terminal (that is, the first context of the first terminal), the entire context of the first terminal may also include the context of the first terminal itself, which is different from and / or unrelated to any context of the second terminal.

[0139] Here, one or more other terminals other than the second terminal may include the first terminal. It should be understood that, whether in the foregoing or the following text, the other terminals involved are relative concepts, that is, the other terminals are relative to the first terminal or the second terminal. When describing any other terminal mentioned in relation to the first terminal, such as one or more other terminals having a binding relationship with the first terminal mentioned in the foregoing embodiment, any other terminal refers to another terminal different from the first terminal. In this case, the other terminal does not include the first terminal. When describing any other terminal mentioned in relation to the second terminal, such as one or more other terminals other than the second terminal, any other terminal refers to another terminal different from the second terminal. In this case, the any other terminal is not the second terminal and may be the first terminal.

[0140] In one embodiment, the first context of the first terminal may include the first portion of parameters in the context associated with the second terminal. Accordingly, the first network device generating the first context of the first terminal based on the context associated with the second terminal may include: the first network device generating the first context of the first terminal based on the first portion of parameters in the context associated with the second terminal. For example, the first network device may directly add the first portion of parameters in the context associated with the second terminal to the first context of the first terminal.

[0141] The first part of parameters may be all or part of the parameters of the context related to the second terminal. Furthermore, the first part of parameters may be part or all of the parameters of the context related to the second terminal that can be allocated to one or more other terminals other than the second terminal.

[0142] In this embodiment, the first network device generates the first context of the first terminal based on the first part of the parameters in the context related to the second terminal, which may include: the first network device combines the subscription information of the first terminal (for example, the MM subscription information of the first terminal obtained from the third network device), the local related configuration of the first network device, and the first part of the parameters in the context related to the second terminal to generate the entire context of the first terminal, the entire context of the first terminal includes the first context of the first terminal, the first context of the first terminal includes the first part of the parameters in the context related to the second terminal, and in addition, the entire context of the first terminal may also include the context of the first terminal itself. The specific method of generating the context of the first terminal itself is not limited in this embodiment.

[0143] Optionally, after the first network device generates the first context for the first terminal, the first network device may release or delete the first portion of parameters in the context related to the second terminal. In this case, if the first portion of parameters is not all the parameters in the context related to the second terminal, the first network device may continue to maintain or save the remaining parameters in the context related to the second terminal except for the first portion of parameters. If the first portion of parameters is all the parameters in the context related to the second terminal, the first network device directly releases or deletes the context related to the second terminal. That is, the first network device migrates the first portion of parameters in the context related to the second terminal to the first terminal.

[0144] Optionally, after the first network device generates the first context of the first terminal, the first network device may still maintain or save the context related to the second terminal.

[0145] In one embodiment, the first context of the first terminal may include relevant parameters of the second portion of parameters in the context related to the second terminal. Accordingly, the first network device generating the first context of the first terminal based on the context related to the second terminal may include: the first network device processing the second portion of parameters in the context related to the second terminal to obtain relevant parameters of the second portion of parameters in the context related to the second terminal; and generating the first context of the first terminal based on the relevant parameters of the second portion of parameters in the context related to the second terminal.

[0146] In this case, the second part of parameters may be all or part of the parameters of the context associated with the second terminal. Furthermore, the second part of parameters may be part or all of the parameters of the context associated with the second terminal that can be allocated to one or more other terminals other than the second terminal.

[0147] The first network device processes the second portion of parameters in the context associated with the second terminal to obtain relevant parameters of the second portion of parameters in the context associated with the second terminal, which may include: the first network device adjusts the second portion of parameters in the context associated with the second terminal based on the relevant information of the first terminal to obtain relevant parameters of the second portion of parameters in the context associated with the second terminal. Here, the relevant parameters of the second portion of parameters in the context associated with the second terminal are mapped or associated with the second portion of parameters in the context associated with the second terminal.

[0148] For example, the relevant information of the first terminal and the second terminal are different. For example, the relevant information of the first terminal may include at least one of the bitrate supported by the first terminal, the resolution supported by the first terminal, the computing power supported by the first terminal, the communication capability of the first terminal, the display clarity of the first terminal, etc. The relevant information of the first terminal may have been pre-acquired by the first network device, and the manner in which the first network device obtains the relevant information of the first terminal is not limited herein.

[0149] In this embodiment, the generation of the first context of the first terminal based on the relevant parameters of the second part of the parameters in the context related to the second terminal can be: the first network device combines the contract information of the first terminal (for example, the MM contract information of the first terminal can be obtained from the third network device), the local relevant configuration of the first network device, and the relevant parameters of the second part of the parameters in the context related to the second terminal to generate the entire context of the first terminal, the entire context of the first terminal includes the first context of the first terminal, the first context of the first terminal includes the relevant parameters of the second part of the parameters in the context related to the second terminal, and in addition, the entire context of the first terminal can also include the context of the first terminal itself.

[0150] In this embodiment, the first network device adjusts the second part of the parameters in the context related to the second terminal in combination with the relevant information of the first terminal, and can obtain the relevant parameters of the second part of the parameters in the context related to the second terminal, and then generate the first context of the first terminal based on the relevant parameters of the second part of the parameters in the context related to the second terminal, so that the first context of the first terminal is more applicable or has higher applicability in the first terminal.

[0151] The first context of the first terminal ultimately assigned by the first network device is mapped or associated with the second portion of parameters in the context associated with the second terminal. For example, the first network device adjusts the second portion of parameters in the context associated with the second terminal based on the relevant information of the first terminal and a preset mapping relationship table (or association relationship table) to obtain relevant parameters of the second portion of parameters in the context associated with the second terminal that are applicable to the first terminal; the first network device then uses the relevant parameters of the second portion of parameters in the context associated with the second terminal as the first context of the first terminal.

[0152] The mapping relationship table and the association relationship table may be pre-configured or obtained through negotiation, and this embodiment does not impose any restrictions thereon. In actual processing, as long as the relevant information of the first terminal and the second terminal is different, corresponding adjustment methods may exist. As long as the relevant parameters of the second part of the parameters in the context related to the second terminal after adjustment are applicable to the first terminal, they are within the scope of protection of this embodiment, and this is not an exhaustive list.

[0153] Optionally, after the first network device generates the first context of the first terminal, the first network device may release or delete the second portion of parameters in the context related to the second terminal. In this case, if the second portion of parameters is not all the parameters in the context related to the second terminal, the first network device may continue to maintain or save the remaining parameters in the context related to the second terminal except for the second portion of parameters. If the second portion of parameters is all the parameters in the context related to the second terminal, the first network device directly releases or deletes the context related to the second terminal. Optionally, after the first network device generates the first context of the first terminal, the first network device may still maintain or save the context related to the second terminal.

[0154] In one embodiment, the first context of the first terminal may include the first portion of parameters in the context related to the second terminal and relevant parameters of the second portion of parameters in the context related to the second terminal. Accordingly, the first network device generating the first context of the first terminal based on the context related to the second terminal may include: the first network device directly adding the first portion of parameters in the context related to the second terminal to the first context of the first terminal; and the first network device processing the second portion of parameters in the context related to the second terminal to obtain relevant parameters of the second portion of parameters in the context related to the second terminal, and adding the relevant parameters of the second portion of parameters in the context related to the second terminal to the first context of the first terminal.

[0155] In this example, the first and second parameters are different. The combination of the first and second parameters may include some or all parameters of the context associated with the second terminal that can be assigned to one or more other terminals other than the second terminal. The processing of the first and second parameters of the context associated with the second terminal by the first network device is the same as in the corresponding embodiments described above and is not repeated here.

[0156] Optionally, after the first network device generates the context of the first terminal, the first network device may release or delete the first part of the parameters and the second part of the parameters in the context related to the second terminal. In this case, if the first part of the parameters and the second part of the parameters are not all the parameters in the context related to the second terminal, the first network device may continue to maintain or save the remaining parameters in the context related to the second terminal except for the first part of the parameters and the second part of the parameters. If the first part of the parameters and the second part of the parameters are all the parameters in the context related to the second terminal, the first network device directly releases or deletes the context related to the second terminal. Optionally, after the first network device generates the context of the first terminal, the first network device may still maintain or save the context related to the second terminal.

[0157] The first context of the first terminal may include: a first part of parameters in the context related to the second terminal, and / or parameters that are mapped or associated with the second part of parameters in the context related to the second terminal. For example, in conjunction with Figure 9, Figure 9 illustrates UE-1 and UE-2, and the UE-1 and UE-2 serve the same user A or the same application A. Assuming that UE-1 is the first terminal and UE-2 is the second terminal, the first network device has allocated context-2 corresponding to user A (or application A) to UE-2, and can allocate context-1 corresponding to user A (or application A) to UE-1. The parameter values ​​of context-1 and context-2 can be partially the same, and / or partially different, and / or partially related, or the parameter values ​​of context-1 and context-2 corresponding to user A (or application A) allocated to UE-1 are all the same. For example, UE-1 and UE-2 serve the same user A. The second part of the context-2 parameters assigned to UE-2 includes S-NSSAI-2, while the context-1 assigned to UE-1 includes S-NSSAI-1. The association between the two can be based on pre-configuration or negotiation. For another example, UE-1 and UE-2 serve the same application A. The second part of the context-2 parameters assigned to UE-2 includes MBR-2 and GBR-2, while the context-1 assigned to UE-1 includes MBR-1 and GBR-1. UE-1's context-1 also includes the same parameters as the first part of UE-2's context-2 parameters. For example, UE-1 and UE-2 use the same QoS parameters. There are many reasons why the context parameters of UE-1 and UE-2 may differ, such as different computing capabilities, communication capabilities, or display resolutions of UE-1 and UE-2, which may result in different context parameter values. It should also be noted with respect to Figure 9 that UE-1 and UE-2 are merely any two UEs serving the same user A or the same application A. In actual processing, there may be more UEs serving the same user A or the same application A. For example, in addition to UE-1 and UE-2, there may also be UE-3, UE-4, etc. that also serve the same user A or the same application A. Similar processing between UE-1 and UE-2 can be performed between any two UEs serving the same user A or the same application A. However, for the sake of simplicity in Figure 9, more UEs are not illustrated one by one.

[0158] In some possible implementations, after the first network device generates the first context of the first terminal, the first network device may locally store the first context of the first terminal.

[0159] In this embodiment, in addition to locally storing the first context of the first terminal, the first network device may also process the first network device by sending second information, where the second information includes at least some parameters of the first context of the first terminal. Accordingly, after the first terminal sends the first information, the method further includes receiving second information by the first terminal, where the second information includes at least some parameters of the first context of the first terminal.

[0160] The first network device sending the second information means that the first network device sends the second information to the first terminal; correspondingly, the first terminal receiving the second information means that the first terminal receives the second information sent by the first network device.

[0161] Among them, at least part of the parameters of the first context of the first terminal may be part or all of the parameters of the first context of the first terminal. This embodiment does not exhaustively list or limit the parameter content or type of the first context synchronized by the first network device to the first terminal.

[0162] That is, after the first network device generates a first context for the first terminal, the first context of the first terminal may be allocated to a network element serving the first terminal (eg, may include the first network device) and / or the first terminal.

[0163] In some possible implementations, the first terminal may further report relevant indication information of the first capability, so that the first network device determines that the first terminal has the first capability.

[0164] The processing of the first terminal may also include: the first terminal sends a first indication message, wherein the first indication message is used to indicate that the first terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the terminal. Accordingly, the processing of the first network device may also include: the first network device receives a first indication message, wherein the first indication message is used to indicate that the first terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the terminal.

[0165] The first terminal has the first capability, which may mean that the first terminal supports or allows any processing related to the first terminal under the operation corresponding to the first capability, and also supports or allows the network side (such as the first network device) to perform processing related to the first capability.

[0166] Here, the first terminal sending the first indication information is the first terminal sending the first indication information to the first network device; correspondingly, the first network device receiving the first indication information is the first network device receiving the first indication information sent by the first terminal.

[0167] In the first capability of the first terminal mentioned in the first indication information, the terminal involved refers to the first terminal; any other terminal involved refers to other terminals other than the first terminal. The other terminal is not used to specifically refer to one or more terminals, and as long as it is different from the first terminal, it is within the protection scope of this embodiment.

[0168] The first indication information can indicate that the first terminal has the first capability through the descriptive information in a designated field. The descriptive information of the designated field can be configured according to the actual situation, such as directly describing that the first terminal has the first capability and / or the specific content of the first capability without limiting it. Alternatively, the first indication information can indicate whether the first terminal has the first capability through the value of the indicator bit in the designated field. For example, when the value of the indicator bit is the first value, it is used to indicate that the first terminal has the first capability. When the value of the indicator bit is the second value, it is used to indicate that the first terminal does not have the first capability. The first value and the second value can be set according to the actual situation. For example, the first value can be 0 and the second value can be 1, or the first value can be 1 and the second value can be 0. They are not exhaustively listed and limited here. This embodiment does not limit which field in the message that carries the first indication information the designated field is.

[0169] Optionally, the first capability may only include a capability of supporting or allowing at least part of the context-related contexts of one or more other terminals to be allocated to the terminal.

[0170] In this case, the first network device may determine that the first terminal can only be assigned a context related to at least part of the context of any other terminal, and cannot assign the context related to the first terminal to any other terminal other than the first terminal. Alternatively, the first network device may determine that the first terminal can not only be assigned a context related to at least part of the context of any other terminal, but can also assign the context related to the first terminal to any other terminal other than the first terminal. All of the above possibilities are within the scope of protection of this embodiment.

[0171] Among them, the at least partial context of the one or more other terminals includes: the context related to at least part of the context of each other terminal in at least part of the one or more other terminals different from the first terminal, or the context related to at least part of the context of any one of the one or more other terminals different from the first terminal. Furthermore, the context related to at least part of the context of any other terminal may include the first part of the parameters in the context related to any other terminal, and / or the relevant parameters of the second part of the parameters in the context related to any other terminal. The description of the context related to any other terminal is similar to that of the context related to the second terminal; accordingly, the description of the first part of the parameters and the second part of the parameters is also similar to that of the first part of the parameters and the second part of the parameters in the context related to the second terminal, so they are not repeated here.

[0172] Optionally, the first capability may only include a capability of supporting or allowing at least part of the context-related context of the terminal to be distributed to one or more other terminals.

[0173] In this case, the first network device may determine that the first terminal can only allocate context related to at least part of the context of the terminal to one or more other terminals, and cannot be allocated context related to at least part of the context of any other terminal. Alternatively, the first network device may determine that the first terminal can not only be allocated context related to at least part of the context of any other terminal, but also be allocated context related to the first terminal to any other terminal other than the first terminal. All of the above may fall within the protection scope of this embodiment.

[0174] The at least partially context-related context of the terminal may include a first portion of parameters in the context related to the first terminal and / or parameters related to a second portion of parameters in the context related to the first terminal. The description of the context related to the first terminal is similar to that of the context related to the second terminal and is therefore not repeated here.

[0175] Optionally, the first capability may include the ability to support or allow at least part of the context-related context of the current terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the current terminal. In this case, the first network device may determine that the first terminal can not only be allocated at least part of the context-related context of any other terminal, but also be able to allocate the context related to the first terminal to any terminal other than the first terminal.

[0176] In some embodiments, the first indication information is also used to indicate at least one of the following: the first terminal requests to execute the function corresponding to the first capability; the first terminal requires to execute the function corresponding to the first capability; the first terminal supports the execution of the function corresponding to the first capability; the first terminal agrees to execute the function corresponding to the first capability; the first terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

[0177] The first indication information may include identifiers of the one or more other terminals, including the second terminal. The identifiers of the one or more other terminals include the identifier of each of the one or more other terminals. The one or more other terminals may be one or more other terminals different from the first terminal, or one or more other terminals other than the first terminal.

[0178] In some possible implementations, the first terminal sending the first indication information and the first terminal sending the first information may be performed simultaneously.

[0179] The first indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, or a session modification request message. In this embodiment, the first indication information and the first information may be carried in the same message, that is, the first information and the first indication information may be carried simultaneously by one of the following: a registration request message, a registration update message, a session establishment request message, or a session modification request message.

[0180] Optionally, if the first indication information is sent simultaneously with the first information, the first indication information may be used only to indicate that the first terminal possesses the first capability; and the first indication information, combined with the first information, may enable the first network device to determine that the first terminal possesses the first capability, and the first terminal requests the first network device to begin allocating a context related to at least part of the second terminal's context to the first terminal to generate the first context of the first terminal. The processing of the first network device is the same as in the aforementioned embodiment and will not be repeated.

[0181] Optionally, if the first indication information is sent simultaneously with the first information, then in addition to indicating that the first terminal has the first capability, the first indication information can also be used to indicate that the first terminal requests to execute the function corresponding to the first capability, the first terminal requires to execute the function corresponding to the first capability, the first terminal supports the execution of the function corresponding to the first capability, the first terminal agrees to execute the function corresponding to the first capability, and the first terminal requests permission to execute the function corresponding to the first capability with one or more other terminals. Similarly, the first indication information combined with the first information can enable the first network device to determine that the first terminal has the first capability, and the first terminal requests the first network device to start executing the process of allocating a context related to at least part of the context of the second terminal to the first terminal to generate the first context of the first terminal. No repeated explanation is given.

[0182] Specifically, the first terminal's request for permission to execute the function corresponding to the first capability with one or more other terminals may refer to the first terminal requesting permission to execute the function corresponding to the first capability with one or more other terminals. In this case, the first network device may determine whether the first terminal is permitted to execute the function corresponding to the first capability with one or more other terminals. This embodiment does not limit the rules or method for the first network device to determine whether the first terminal is permitted to execute the function corresponding to the first capability with one or more other terminals.

[0183] It should be noted that the first indication information may also include the identifiers of one or more other terminals, that is, indicating to the first network device which other terminals are bound or associated with the first terminal, so that the first network device can determine which other terminals can mutually allocate contexts with the first terminal. Furthermore, this first indication information, combined with the first information, can enable the first network device to determine that the first terminal has the first capability, and that the first terminal requests the first network device to begin allocating a context related to at least part of the second terminal's context to the first terminal, so as to generate the first context of the first terminal. This is not further described here.

[0184] In some embodiments, in a scenario where the first terminal reports the first information and the first indication information at the same time, after the first network device generates the first context of the first terminal, the first network device may only send the second information to the first terminal, and the content of the second information will not be repeated.

[0185] In some embodiments, in a scenario where the first terminal simultaneously reports the first information and the first indication information, after the first network device receives the first information and the first indication information, the processing of the first network device may further include: the first network device sends second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to perform the function corresponding to the first capability, and requiring the first terminal to perform the function corresponding to the first capability. Accordingly, the processing of the first terminal may further include: the first terminal receives the second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to perform the function corresponding to the first capability, and requiring the first terminal to perform the function corresponding to the first capability.

[0186] The first network device sending the second indication information means that the first network device sends the second indication information to the first terminal; and the first terminal receiving the second indication information means that the first terminal receives the second indication information sent by the first network device.

[0187] In this embodiment, the first network device may not send the second information to the first terminal, but may only send the second indication information to the first terminal. The second indication information may be sent after the first network device completes the allocation of the first context to the first terminal; or the second indication information may be sent after the first network device confirms that the first context can be allocated to the first terminal. In this case, the first network device may not have yet generated or allocated the first context to the first terminal.

[0188] Preferably, in this embodiment, the second indication information is used to instruct the first network device to support the first terminal in executing the function corresponding to the first capability. That is, the first network device can store the first terminal's first context and only indicate to the first terminal through the second indication information that it supports the first terminal in executing the function corresponding to the first capability. Accordingly, upon receiving the second indication information, the first terminal can determine that the first network device will allocate the first context to the first terminal, or that the first network device has already allocated the first context to the first terminal.

[0189] In some embodiments, in a scenario where the first terminal reports both the first information and the first indication information, after the first network device receives the first information and the first indication information, the first network device may send the second information and the second indication information to the first terminal. The details of the second information and the second indication information are not described in detail here.

[0190] The second information and the second indication information may be sent simultaneously, for example, they may be carried by the same message, or they may be carried by different messages sent simultaneously. Alternatively, the second information and the second indication information may be sent at different times, for example, they may be carried by different messages sent at different times. In this case, the order in which the first network device sends the second indication information and the second information is not limited, and the second indication information may be sent first and then the second information. This does not exhaustively list all possible transmission scenarios for the second information and the second indication information.

[0191] This embodiment is particularly applicable to situations where the first indication information is used to instruct the first terminal to request permission to execute the function corresponding to the first capability with one or more other terminals. Because in this situation, the first terminal requires the first network device to determine whether to allow it to be assigned the context of the other terminal, the first network device can notify the first terminal through the second indication information to support execution of the function corresponding to the first capability.

[0192] Preferably, in this embodiment, the second indication information is used to instruct the first network device to support the first terminal in executing a function corresponding to the first capability.

[0193] In some possible implementations, the first terminal sending the first indication information and the first terminal sending the first information may not be performed simultaneously. In this implementation, the first terminal may send the first indication information first and then send the first information.

[0194] The first indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, or a session modification request message. In this embodiment, the first indication information and the first information may be carried in different messages. For example, the first indication information may be carried in a registration request message, and the first information may be carried in any one of a registration update message, a session establishment request message, and a session modification request message. For another example, the first indication information may be carried in a session establishment request message, and the first information may be carried in a session modification request message. This does not exhaustively enumerate or limit all possible messages in which the first information and the first indication information may be carried.

[0195] Optionally, when the first indication information is used to indicate that the first terminal requests to execute the function corresponding to the first capability, the first terminal requires to execute the function corresponding to the first capability, the first terminal supports executing the function corresponding to the first capability, and the first terminal agrees to execute at least one of the functions corresponding to the first capability, the first network device can record the context related to at least part of the context of other terminals that can be assigned to the first terminal, and / or the first network device can start to generate a second context of the first terminal for the first terminal, and the second context includes at least part of the context that can be assigned to one or more other terminals. It should be pointed out that any other terminal is only used to represent other terminals different from the first terminal, without specifically referring to which other terminals or terminals.

[0196] Optionally, the first indication information is used to instruct the first terminal to request permission to perform the function corresponding to the first capability with one or more other terminals. This may mean that the first terminal requests the first network device whether permission to perform the function corresponding to the first capability with one or more other terminals is permitted. In this case, the first network device may first determine whether the first terminal is permitted to perform the function corresponding to the first capability with one or more other terminals. This embodiment does not limit the rules or method for the first network device to make this determination.

[0197] It should be noted that the first indication information may include the identifiers of one or more other terminals. That is, the first indication information can simultaneously report to the first network device which other terminals the first terminal is bound to or associated with. Using the identifiers of the one or more other terminals, the first network device can determine the binding or association relationship between the first terminal and the other terminals.

[0198] In some embodiments, in a scenario where the first terminal sends the first indication information before sending the first information, the first network device may generate a second context for the first terminal after receiving the first indication information.

[0199] After the first network device receives the first indication information, the method also includes: the first network device obtains the contract information of the first terminal from the third network device, and the contract information of the first terminal includes at least part of the contract information that can be used by one or more other terminals; the first network device generates a second context of the first terminal based on the contract information of the first terminal, and the second context of the first terminal includes at least part of the context that can be allocated to one or more other terminals.

[0200] The at least partial contract information that can be used by one or more other terminals may refer to: at least part of the contract information in the contract information of the first terminal can be used by other terminals other than the first terminal; or, related information of at least part of the contract information in the contract information of the first terminal can be used by other terminals other than the first terminal. The contract information may include mobility management (MM) contract information, and it should be understood that it may also include other contract information, which is not limited or exhaustive here.

[0201] The second context of the first terminal includes at least part of the context that can be assigned to one or more other terminals, which means that the second context of the first terminal can include at least part of the context that can be assigned to any other terminal except the first terminal.

[0202] The first network device may obtain the contract information of the first terminal from the third network device, which may include: the first network device sends a second request message to the third network device, the second request message includes an indication that the first terminal has the first capability, and the first network device receives the contract information of the first terminal sent by the third network device. Accordingly, the processing of the third network device may include: the third network device receives the second request message sent by the first network device, the second request message includes an indication that the first terminal has the first capability, and the third network device sends the contract information of the first terminal to the first network device. Here, the third network device can determine that the first terminal has the first capability through the second request message, so the third network device can allocate, generate, or select contract information of the first terminal that meets the first capability for the first terminal.

[0203] The first network device generates a second context for the first terminal based on the subscription information of the first terminal, which may include: the first network device generates the second context for the first terminal based on the subscription information of the first terminal, an indication that the first terminal has a first capability, and a local configuration; wherein, the local configuration refers to the relevant configuration on the first network device side for allocating the context, and this embodiment does not limit its specific content.

[0204] Before the first network device sends the second request message to the third network device, the method may further include: the first network device determines the third network device. Exemplarily, the first network device determining the third network device may refer to: the first network device determining the third network device corresponding to the first terminal, or the first network device may select a candidate network device that supports the first capability from multiple candidate network devices that can serve the first terminal and generate subscription information as the third network device.

[0205] Optionally, the processing of the first network device may further include: the first network device obtaining a policy and charging control (PCC) rule of the first terminal from a fourth network device, where the PCC rule of the first terminal includes at least some PCC rules that can be used by one or more other terminals. The first network device generates a second context for the first terminal based on the subscription information of the first terminal, including: the first network device generates the second context for the first terminal based on the subscription information of the first terminal and the PCC rule of the first terminal.

[0206] The fourth network device may include a PCF (Policy Control Function).

[0207] The at least part of the PCC rules that can be used by one or more other terminals may refer to: at least part of the PCC rules of the first terminal can be used by other terminals other than the first terminal; or, at least part of the relevant information of the PCC rules in the PCC rules of the first terminal can be used by other terminals other than the first terminal.

[0208] The first network device may obtain the PCC rules of the first terminal from the fourth network device, which may include: the first network device sends a third request message to the fourth network device, the third request message includes an indication that the first terminal has the first capability, and the first network device receives the PCC rules of the first terminal sent by the fourth network device. Correspondingly, the processing of the fourth network device may include: the fourth network device receives the third request message sent by the first network device, and the fourth network device sends the PCC rules of the first terminal to the first network device. Here, the fourth network device can determine that the first terminal has the first capability through the third request message, and therefore the fourth network device can allocate, generate, or select PCC rules for the first terminal that meet the first capability for the first terminal.

[0209] The first network device generates a second context for the first terminal based on the subscription information of the first terminal and the PCC rule of the first terminal, which may include: the first network device generates the second context for the first terminal based on the subscription information of the first terminal, the PCC rule of the first terminal, an indication that the first terminal has a first capability, and a local configuration.

[0210] Before the first network device sends the third request message to the fourth network device, the method may further include: the first network device determining the fourth network device. Exemplarily, the first network device determining the fourth network device may refer to: the first network device determining the fourth network device corresponding to the first terminal, or the first network device may select a candidate network device that supports the first capability from multiple candidate network devices that can serve the first terminal and generate PCC rules as the fourth network device.

[0211] In some embodiments, in a scenario where the first terminal sends the first indication information before sending the first information, after the first network device generates the second context of the first terminal, the first network device may locally store the second context of the first terminal.

[0212] The processing after the first network device generates the second context for the first terminal may further include: the first network device sending third information, wherein the third information includes at least some parameters of the second context for the first terminal. Accordingly, after the first terminal sends the first indication information, the method further includes: the first terminal receiving third information, wherein the third information includes at least some parameters of the second context for the first terminal, and the second context for the first terminal includes at least some context that can be allocated to one or more other terminals.

[0213] The first network device sending the third information means that the first network device sends the third information to the first terminal; correspondingly, the first terminal receiving the third information means that the first terminal receives the third information sent by the first network device.

[0214] Among them, at least part of the parameters of the second context of the first terminal may be part or all of the parameters of the second context of the first terminal. This embodiment does not exhaustively enumerate or limit the parameter content or type of the second context synchronized by the first network device to the first terminal.

[0215] That is, after the first network device generates the second context for the first terminal, the second context of the first terminal may be allocated to a network element serving the first terminal (eg, may include the first network device) and / or the first terminal.

[0216] In some embodiments, in a scenario where a first terminal sends first indication information before sending a first message, after the first network device receives the first indication information, the processing of the first network device may further include: the first network device sends second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to perform the function corresponding to the first capability, or requiring the first terminal to perform the function corresponding to the first capability. Correspondingly, the processing of the first terminal may further include: the first terminal receives second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to perform the function corresponding to the first capability, or requiring the first terminal to perform the function corresponding to the first capability.

[0217] In this embodiment, the first network device may not send the third information to the first terminal, but may only send the second indication information to the first terminal. The second indication information may be sent after the first network device completes allocation of the second context to the first terminal; or the second indication information may be sent after the first network device confirms that the second context can be allocated to the first terminal. In this case, the first network device may not have yet allocated or generated the second context for the first terminal.

[0218] The second indication information is used to indicate support for the first terminal to perform the function corresponding to the first capability, which may mean that the first network device agrees, allows, or supports the first terminal's future request for allocation of the first context of the first terminal. In this case, the first terminal can start sending the first information at any desired time after receiving the second indication information.

[0219] The second indication information is used to instruct the first terminal to execute the function corresponding to the first capability, and may refer to the first network device instructing the first terminal to begin requesting allocation of the first context of the first terminal. In this case, the first terminal may begin sending the first information after receiving the second indication information; alternatively, the first terminal may begin sending the first information at any desired time after receiving the second indication information.

[0220] In this embodiment, after the first network device generates the second context of the first terminal, it may be stored locally.

[0221] In some embodiments, in a scenario where the first terminal sends the first indication information before sending the first information, the first network device may send the third information and the second indication information to the first terminal.

[0222] The third information and the second indication information may be sent simultaneously, for example, they may be carried in the same message, or carried in different messages sent simultaneously. Alternatively, the third information and the second indication information may be sent at different times, for example, they may be carried in different messages sent at different times. There is no limitation on the order in which the first network device sends the second indication information and the third information.

[0223] In some embodiments, the first terminal may send the first information to the first network device after receiving the third information and / or the second indication information. The processing of the first network device after receiving the first information will not be repeated here.

[0224] In some possible embodiments, in a scenario where a first terminal sends first indication information before sending a first message, if the first network device determines that the first terminal is not permitted to perform the function corresponding to the first capability, the first network device may send information to the first terminal indicating that the first terminal is denied or not permitted to perform the function corresponding to the first capability. In this case, the first network device and other related third network devices and / or fourth network devices may execute subsequent processing procedures for the first terminal in accordance with the provisions of the relevant protocol, which are not limited here.

[0225] In some possible implementations, the processing of the first device sending the first information needs to be based on the network side (for example, it can be the first network device serving the first terminal and the second terminal, or the second network device serving the second terminal) having allocated the context related to the second terminal. Therefore, the following describes the processing of sending the third indication information that the second terminal needs to perform before the first device sends the first information, and the processing of allocating the context related to the second terminal that the second network device needs to complete.

[0226] The second terminal sending the third indication information may specifically be: the second terminal sending the third indication information to the second network device. Correspondingly, the second network device receiving the third indication information may be: the second network device receiving the third indication information sent by the second terminal. The third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the current terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the current terminal.

[0227] It should be pointed out that in order to clarify the relevant processing performed by the network side on the second terminal, the network devices corresponding to the second terminal are referred to as second network devices below. However, the description of the second network device below does not mean that it cannot be used for the first network device. When the first network device serves the first terminal and the second terminal at the same time, the second network devices involved below can be replaced by the first network device, but the description will not be repeated.

[0228] The third indication information may be carried by one of the following: a registration request message, a registration update message, a session establishment request message, or a session modification request message.

[0229] In this embodiment, the second terminal may refer to any terminal except the first terminal, or the second terminal may be any terminal that has the first capability and has a binding relationship with the first terminal.

[0230] In the first capability mentioned in the aforementioned third indication information, the terminal involved refers to the second terminal; any one of the one or more other terminals involved refers to any other terminal except the second terminal.

[0231] The third indication information may indicate that the second terminal has the first capability through descriptive information in a designated field, or the third indication information may indicate whether the second terminal has the first capability through the value of an indication bit in a designated field. The description of the carrying method of the third indication information is similar to the first indication information in the related description of the first terminal in the aforementioned embodiment and is not repeated here.

[0232] Optionally, the first capability may only include the ability to assign at least part of the context-related context of one or more other terminals to this terminal (i.e., the second terminal). In this case, the second network device may determine that the second terminal can only be assigned at least part of the context-related context of any other terminal, and cannot assign the context related to the second terminal to any other terminal other than the second terminal. Alternatively, the second network device may determine that the second terminal can not only be assigned at least part of the context-related context of any other terminal, but also assign the context related to the second terminal to any other terminal other than the second terminal. The above may all be within the scope of protection of this embodiment. Among them, the relevant description of at least part of the context of one or more other terminals is also similar to the aforementioned embodiment, the only difference is that in this embodiment, the other terminal is a terminal different from the second terminal, and will not be repeated here.

[0233] Optionally, the first capability may only include the ability to allocate at least part of the context-related context of the terminal (i.e., the second terminal) to one or more other terminals. In this case, the second network device may determine that the second terminal can only allocate at least part of the context-related context of the terminal to one or more other terminals, and cannot be allocated at least part of the context-related context of any other terminal. Alternatively, the second network device may determine that the second terminal can not only be allocated at least part of the context-related context of any other terminal, but also can allocate the context related to the second terminal to any other terminal other than the second terminal. The above may all be within the protection scope of this embodiment. Among them, the description of the context related to the second terminal is the same as that of the aforementioned embodiment, so it will not be repeated here.

[0234] Optionally, the aforementioned first capability may include the ability to allocate at least part of the context-related context of the current terminal (i.e., the second terminal) to one or more other terminals, and the ability to allocate at least part of the context-related context of one or more other terminals to the current terminal (i.e., the second terminal). In this case, the second network device may determine that the second terminal can not only be allocated at least part of the context-related context of any other terminal, but also be able to allocate the context related to the second terminal to any terminal other than the second terminal.

[0235] After receiving the third indication information, the second network device may determine that the second terminal has the first capability.

[0236] In some embodiments, the third indication information is also used to indicate at least one of the following: the second terminal requests to execute the function corresponding to the first capability; the second terminal requires to execute the function corresponding to the first capability; the second terminal supports executing the function corresponding to the first capability; the second terminal agrees to execute the function corresponding to the first capability; the second terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

[0237] The third indication information includes an identifier of the one or more other terminals. The one or more other terminals refer to one or more other terminals different from the second terminal, or one or more other terminals other than the second terminal. The one or more other terminals may include the first terminal.

[0238] The second terminal requests to execute the function corresponding to the first capability, which may mean that the second terminal requests the second network device to start executing the function corresponding to the first capability, such as requesting the second network device to start allocating at least part of the context related to the second terminal to other terminals, and / or requesting to allocate at least part of the context related to the second terminal that can be allocated to one or more other terminals.

[0239] The second terminal's request to execute the function corresponding to the first capability is similar to the aforementioned second terminal's request to execute the function corresponding to the first capability, and will not be elaborated on.

[0240] The second terminal supports the execution of the function corresponding to the first capability, which may mean that the second terminal notifies the second network device that it can support the execution of the function corresponding to the first capability. In this case, the second terminal does not clearly indicate which terminal or terminals start to execute the function corresponding to the first capability. It may be that the second network device can directly execute the function corresponding to the first capability of the second terminal after receiving the relevant request.

[0241] The second terminal agrees to execute the function corresponding to the first capability, which is similar to the relevant description of the second terminal supporting the execution of the function corresponding to the first capability, which means: the second terminal notifies the second network device that it agrees to execute the function corresponding to the first capability when necessary.

[0242] The second terminal requesting permission to execute the function corresponding to the first capability with one or more other terminals may refer to the second terminal requesting the second network device whether permission to execute the function corresponding to the first capability with one or more other terminals is permitted. In this case, the second network device may determine whether the second terminal is permitted to execute the function corresponding to the first capability with one or more other terminals. This embodiment does not limit the rules or method for the second network device to determine whether the second terminal is permitted to execute the function corresponding to the first capability with one or more other terminals.

[0243] It should be noted that the third indication information may include the identifiers of one or more other terminals. That is, which other terminals are bound or associated with the second terminal can be simultaneously reported to the second network device via the third indication information. Using the identifiers of the one or more other terminals, the second network device can determine which other terminals can be associated with the second terminal.

[0244] In some embodiments, after receiving the third indication information, the second network device may generate a second terminal-related context, wherein the second terminal-related context includes at least a portion of a context that can be allocated to one or more other terminals.

[0245] After the second network device receives the third indication information, the method also includes: the second network device obtains the contract information of the second terminal from the third network device, and the contract information of the second terminal includes at least part of the contract information that can be used by one or more other terminals; the second network device generates a context related to the second terminal based on the contract information of the second terminal, and the context related to the second terminal includes at least part of the context that can be allocated to one or more other terminals.

[0246] The at least part of the contract information that can be used by one or more other terminals may refer to: at least part of the contract information in the contract information of the second terminal can be used by other terminals other than the second terminal; or, relevant information of at least part of the contract information in the contract information of the second terminal can be used by other terminals other than the second terminal.

[0247] The second network device obtaining the contract information of the second terminal from the third network device may include: the second network device sending a fourth request message to the third network device, the fourth request message including an indication that the second terminal has the first capability, and the second network device receiving the contract information of the second terminal sent by the third network device. Correspondingly, the processing of the third network device may include: the third network device receiving the fourth request message sent by the second network device, and sending the contract information of the second terminal to the second network device. Here, the description of the third network device allocating the contract information of the second terminal is similar to the description of the third network device allocating the contract information of the first terminal in the aforementioned embodiment, and will not be repeated.

[0248] The second network device generating a context related to the second terminal based on the subscription information of the second terminal may include: the second network device generating a context related to the second terminal based on the subscription information of the second terminal, an indication that the second terminal has the first capability, and a local configuration. The process of the second network device selecting or determining the third network device is similar to the process of the first network device determining the third network device in the aforementioned embodiment and is not further described.

[0249] Optionally, the processing by the second network device may further include: the second network device obtaining PCC rules of the second terminal from a fourth network device, where the PCC rules of the second terminal include at least some PCC rules that can be used by one or more other terminals. The second network device generating a context related to the second terminal based on the subscription information of the second terminal includes: the second network device generating a context related to the second terminal based on the subscription information of the second terminal and the PCC rules of the second terminal.

[0250] The PCC rules of the second terminal include at least some PCC rules that can be used by one or more other terminals, which is the same as the description of the first terminal including at least some PCC rules that can be used by one or more other terminals in the aforementioned embodiment. The only difference lies in the relative concepts of the other terminals, so they are not repeated here.

[0251] The second network device obtaining the PCC rules of the second terminal from the fourth network device may include: the second network device sending a fifth request message to the fourth network device, the fifth request message including an indication that the second terminal has the first capability, and the second network device receiving the PCC rules of the second terminal sent by the fourth network device. Accordingly, the processing of the fourth network device may include: the fourth network device receiving the fifth request message sent by the second network device, and the fourth network device sending the PCC rules of the second terminal to the second network device. Here, the processing of the fourth network device is similar to the related processing of the fourth network device sending the PCC rules of the first terminal to the first network device in the aforementioned embodiment, the only difference being that this embodiment is for the second terminal, and therefore will not be described in detail.

[0252] The second network device generates a context related to the second terminal based on the subscription information of the second terminal and the PCC rule of the second terminal, which may include: the second network device generates a context related to the second terminal based on the subscription information of the second terminal, the PCC rule of the second terminal, the indication that the second terminal has the first capability and the local configuration.

[0253] The process of the second network device selecting or determining the fourth network device is similar to the process of the first network device determining the fourth network device in the aforementioned embodiment, and is not described in detail.

[0254] In some embodiments, after the second network device generates the context related to the second terminal, the second network device may locally store the context related to the second terminal.

[0255] The processing after the second network device generates the context related to the second terminal may further include: the second network device sending sixth information, wherein the sixth information includes at least some parameters of the context related to the second terminal. Correspondingly, after the second terminal sends the third indication information, the method further includes: the second terminal receiving sixth information, wherein the sixth information includes at least some parameters of the context related to the second terminal, and the context related to the second terminal includes at least some context that can be allocated to one or more other terminals.

[0256] The description of the exchange of the sixth information between the second network device and the second terminal is similar to the description of the exchange of the third information between the first network device and the first terminal in the aforementioned embodiment, and therefore is not repeated herein.

[0257] In some embodiments, after the second network device receives the third indication information, the method further includes: the second network device sending fourth indication information, wherein the fourth indication information is used to indicate one of the following: supporting the second terminal to perform the function corresponding to the first capability, or requiring the second terminal to perform the function corresponding to the first capability. Accordingly, the processing of the second terminal may further include: the second terminal receiving the fourth indication information, wherein the fourth indication information is used to indicate one of the following: supporting the second terminal to perform the function corresponding to the first capability, or requiring the second terminal to perform the function corresponding to the first capability.

[0258] The detailed description of the fourth indication information is similar to that of the second indication information in the aforementioned embodiment, with the only difference being that the second indication information corresponds to the first terminal and the fourth indication information corresponds to the second terminal, and a repeated description is omitted here.

[0259] In this embodiment, the second network device may not send the sixth information to the second terminal, but may only send the fourth indication information to the second terminal. The timing of sending the fourth indication information may be after the second network device completes the allocation of the context related to the second terminal; or after the second network device confirms that the context is related to the second terminal.

[0260] In this embodiment, after the second network device generates the context related to the second terminal, it may be stored locally.

[0261] In some embodiments, after the second network device receives the third indication information, the second network device may send the sixth information and the fourth indication information to the second terminal. The sixth information and the fourth indication information may be sent simultaneously or at different times.

[0262] In other possible embodiments, if the second network device determines that the second terminal is not allowed to perform the function corresponding to the first capability, the second network device may send fifth indication information to the second terminal, where the fifth indication information may be used to indicate that the second terminal is denied or not allowed to perform the function corresponding to the first capability. In this case, the second network device and other related third network devices and / or fourth network devices may execute subsequent processes for the second terminal in accordance with the provisions of the relevant protocol, which is not limited here.

[0263] It should be understood that the above embodiment only describes how to generate a context related to the second terminal. In actual processing, after completing the allocation of the context related to the second terminal, the second terminal can also execute the aforementioned first terminal sending the first information and the related processing thereafter. For example, the second terminal can be used as the new first terminal in the aforementioned embodiment, the third terminal can be used as the new second terminal in the aforementioned embodiment, and various processing related to the first terminal in the aforementioned embodiment can be executed. No repeated explanation will be given here.

[0264] The types of context involved in this embodiment may include UE context in AMF and / or SM context. The various parameters that may be included in these two types of contexts have been detailed in Tables 1 and 2 in the aforementioned embodiments and will not be repeated here. Through the communication method provided in the aforementioned embodiment, the context can be migrated or copied, thereby migrating the data stream (partial and / or full, uplink and / or downlink) of the second terminal to the first terminal and the network element serving the first terminal, and the first terminal continues to send or receive subsequent data.

[0265] Next, the communication method provided in the above embodiment is described in different processes by combining different possible network elements of the first network device and the second network device and possible types of contexts.

[0266] In one embodiment, the second network device may be a second AMF, and the third indication information may be carried by a registration request message or a registration update message. The type of context related to the second terminal may be a context of the second terminal in the AMF (UE context in AMF); for example, if the second terminal is represented as UE1 and the second AMF is represented as AMF1, then the context of the second terminal in the second AMF may specifically be UE1context in AMF1.

[0267] The parameter types that can be included in the context of any terminal in the AMF (UE context in AMF) are shown in Table 1 and are not repeated here. It should be noted that in this embodiment, the context associated with the second terminal can include at least a portion of the context that can be allocated to one or more other terminals. In conjunction with the UE context in AMF in Table 1, illustratively, the at least a portion of the context that can be allocated to one or more other terminals in the context associated with the second terminal can include all the parameters in Table 1. Exemplarily, some of the parameters of at least a portion of the context that can be allocated to one or more other terminals in the context associated with the second terminal can include, for example, access management policy association information (such as the PCF of the service and the established association), UE policy association information, allowed network slice (Allowed S-NSSAI) information, and at least one of the parameters of each PDU session. All possible parameters are not exhaustively listed here. In this embodiment, the processing performed by the second AMF is the same as the processing performed by the second network device in the aforementioned embodiment and is not repeated here.

[0268] In one embodiment, the first network device may be a first AMF, the first indication information may be carried by a registration request message, or may be carried by a registration update message, and in this embodiment, the first terminal first sends the first indication information and does not send the first information at the same time.

[0269] The type of the second context of the first terminal may be the context of the first terminal in the AMF (UE context in AMF), and the parameter types that may be included may be as shown in Table 1, which will not be repeated here. It should be noted that, in this embodiment, the second context of the first terminal may include at least part of the context that can be allocated to one or more other terminals. With reference to the UE context in AMF in Table 1 above, illustratively, at least part of the context that can be allocated to one or more other terminals in the second context of the first terminal may include all the parameters in Table 1. Exemplarily, some parameters of at least part of the context that can be allocated to one or more other terminals in the second context of the first terminal may include, for example, access management policy association information (such as the PCF of the service and the established association), UE policy association information, allowed network slice (Allowed S-NSSAI) information, and at least one of the parameters of each PDU session. All possible parameters are not exhaustively listed here.

[0270] In one embodiment, the second network device may be a second SMF, and the third indication information may be carried in a session establishment request message or a session modification request message. The type of the context associated with the second terminal may be an SM context. The parameter types that may be included in the SM context are as shown in Table 2 and are not described again here. It should be noted that in this embodiment, the context associated with the second terminal may include at least a portion of the context that can be allocated to one or more other terminals. With reference to the SM context in Table 2, for example, the at least portion of the context associated with the second terminal that can be allocated to one or more other terminals may include all the parameters in Table 2. For example, the partial parameters of the at least portion of the context associated with the second terminal that can be allocated to one or more other terminals may include at least one of the following parameters in Table 2: attribute parameters of the PDU session (such as S-NSSAI, DNN, SSC mode, PDU session identifier, etc.), information on interaction with the application server (such as DNAI, UE IP address), QoS parameter information for each QoS data flow, etc., although all possible parameters are not exhaustively listed here. In this embodiment, the processing performed by the second SMF is the same as the processing performed by the second network device in the aforementioned embodiment and is not described again here.

[0271] In one embodiment, the first network device may be a first SMF, and the first indication information may be carried by a session establishment request message or a session modification request message. In this embodiment, the first terminal first sends the first indication information and does not send the first information simultaneously. The type of the second context of the first terminal may be an SM context. The description of the SM context of the first terminal is similar to the description of the SM context of the second terminal in the aforementioned embodiment and is not repeated here.

[0272] In one embodiment, the second network device may be a second AMF, which has allocated a context related to the second terminal, that is, the aforementioned context of the second terminal in the AMF (UE context in AMF). In this case, the first network device may be the first AMF.

[0273] Optionally, if the first terminal has already sent the first indication information, the first terminal may send first information to the first AMF. The first information may include the aforementioned first request information and / or the first identifier. The first information may be carried in a registration request message or a registration update message.

[0274] Optionally, if the first terminal has not sent the first indication information, the first terminal may send the first information and the first indication information to the first AMF. The first information may include the aforementioned first request information and / or the first identifier. The first information and the first indication information may be carried in a registration request message or a registration update message.

[0275] Optionally, the first terminal may have sent the first indication information, but the first terminal may still send the first information and the first indication information to the first AMF. The first information may include the aforementioned first request information and / or the first identifier. This situation is particularly applicable when the first terminal has moved after sending the first indication information, and the first network device serving the first terminal may have changed.

[0276] Correspondingly, the first AMF may generate a first context for the first terminal based on the context related to the second terminal. The specific processing is the same as the specific processing of generating the first context for the first terminal in the aforementioned embodiment, and will not be repeated.

[0277] The type of the first context of the first terminal may be the context of the first terminal in the AMF (UE context in AMF). It should be noted that in this embodiment, the first context of the first terminal may include a context related to at least part of the context that can be allocated to the first terminal by the second terminal. With reference to the UE context in AMF in Table 1 above, illustratively, at least part of the context that can be allocated to the first terminal in the context related to the second terminal may include all the parameters in Table 1. Exemplarily, at least part of the context that can be allocated to the first terminal in the context related to the second terminal may include some of the parameters in Table 1, such as at least one of the following: access management policy association information (such as the PCF of the service and the established association) (so that the first terminal and the second terminal can use the same PCF), UE policy association information, allowed network slice (Allowed S-NSSAI) information, and parameters for each PDU session. All possible parameters are not exhaustively listed here.

[0278] In one embodiment, the second network device may be a second SMF, which has been allocated a context related to the second terminal, ie, the SM context of the second terminal. In this case, the first network device may be the first SMF.

[0279] Optionally, if the first terminal has already sent the first indication information, the first terminal may send the first information to the first SMF. The first information may include the aforementioned first request information and / or the first identifier. The first information may be carried in a session establishment request message or a session modification request message.

[0280] Optionally, if the first terminal has not sent the first indication information, the first terminal may send the first information and the first indication information to the first SMF. The first information may include the aforementioned first request information and / or the first identifier. The first information and the first indication information may be carried by a session establishment request message or a session modification request message.

[0281] Accordingly, the first SMF may generate the first context of the first terminal based on the context related to the second terminal. The specific process is the same as that of generating the first context of the first terminal in the aforementioned embodiment and will not be repeated.

[0282] The type of the first context of the first terminal may be the SM context of the first terminal. The parameter types that may be included in the SM context are shown in Table 2 and are not repeated here. It should be noted that in this embodiment, the first context of the first terminal may include a context related to at least part of the context that can be assigned to the first terminal by the second terminal. With reference to the SM context in Table 2, for example, at least part of the context related to the second terminal that can be assigned to the first terminal may include some of the parameters in Table 2. For example, at least part of the context related to the second terminal that can be assigned to the first terminal may include at least one of the following parameters in Table 2: attribute parameters of the PDU session (such as S-NSSAI, DNN, SSC mode, PDU session identifier, etc.) (used by the first terminal to obtain the same session attributes as the second terminal), information on interaction with the application server (such as DNAI, UE IP address) (to ensure better service continuity), QoS parameter information for each QoS data flow, etc. All possible parameters are not exhaustively listed here. In this embodiment, the processing performed by the second SMF is the same as the processing performed by the second network device in the aforementioned embodiment and is not repeated here.

[0283] The following describes the aforementioned method with reference to various embodiments. The underlying assumption for the processes in each of the following embodiments is that the second terminal is the terminal that initially serves user A, and the first terminal is the terminal that subsequently takes over some of the second terminal's services to serve user A. Therefore, the processes for the first and second terminals are described separately. It should be understood that the first terminal can obtain the context of another UE (e.g., the second terminal) and can also obtain its own context from the second terminal; the same applies to the second terminal.

[0284] 10 , the process of the first terminal or the second terminal sending the indication of the first capability is exemplarily described, specifically:

[0285] Step 1001: The UE sends a registration request message to the AMF, carrying an indication of the "first capability".

[0286] In this embodiment, since only one UE reporting the first capability is described, FIG10 may include only one UE.

[0287] In one case, the UE in Figure 10 can be the second terminal, and the AMF in Figure 10 can be the second network device (such as the second AMF) serving the second terminal. The indication of the first capability in step 1001 can be the third indication information in the aforementioned embodiment, that is, the third indication information is carried by the registration request message. In addition to the third indication information, the registration request message can also carry other content specified by the protocol, which is not limited here. In another case, the UE in Figure 10 can be the aforementioned first terminal, and the AMF in Figure 10 can be the aforementioned first network device (such as the first AMF) serving the first terminal. The indication of the first capability in step 1001 can be the first indication information in the aforementioned embodiment, that is, the first indication information is carried by the registration request message. In addition to the first indication information, the registration request message can also carry other content specified by the protocol, which is not limited here. It should be understood that in some possible cases, the AMF can be a network device serving the first terminal and the second terminal.

[0288] The indication of the first capability can be understood as at least one of the following: the UE has the "first capability", and the detailed description of the first capability is the same as that in the aforementioned embodiment and will not be repeated here; the UE requests, or requires, or supports, or agrees to perform the migration or replication of part or all of the parameters of the UE1 context, that is, the UE requests, or requires, or supports, or agrees to perform the function corresponding to the first capability; the UE requests the network side (specifically, the AMF in Figure 10) whether to allow or require multiple terminals to perform the function described by the "first capability", that is, in the aforementioned embodiment, the UE requests permission to perform the function corresponding to the first capability with one or more other terminals.

[0289] Step 1002 (optional): After receiving the "first capability" indication, the AMF selects the corresponding PCF and / or UDM according to the "first capability". The PCF is the fourth network device in the aforementioned embodiment, and the UDM is the third network device in the aforementioned embodiment.

[0290] Step 1002 may be optional. In other words, in one possible scenario, after step 1001 is completed, step 1003 may be performed without selecting a PCF and / or UDM. In another possible scenario, after step 1001 is completed, step 1002 may need to be performed to select a PCF and / or UDM. The manner in which the AMF selects the PCF and / or UDM is the same as in the previous embodiment and is not repeated here.

[0291] Step 1003: The AMF initiates a PCF association establishment or modification (association est. / mod.) message to the PCF, which includes an indication of the "first capability". The PCF can subsequently send the same or associated UE policy to other associated UEs based on this.

[0292] Step 1004: AMF sends a message to UDM to request contract information (the message may be a user contract data acquisition service (Nudm_SDM_Get) message as shown in FIG10 ), which includes a “first capability” indication.

[0293] In one case, the AMF in Figure 10 may be a second network device serving the second terminal (e.g., the second AMF in the aforementioned embodiment). The user subscription data acquisition service (Nudm_SDM_Get) message in step 1004 may be the fourth request message in the aforementioned embodiment. In another case, the AMF in Figure 10 may be a first network device serving the first terminal (e.g., the first AMF). The user subscription data acquisition service (Nudm_SDM_Get) message in step 1004 may be the second request message in the aforementioned embodiment.

[0294] Step 1005: The UDM replies to the AMF with the MM subscription information of the UE. All or part of the parameters of the MM subscription information may be used by other UEs. In this step, the MM subscription information of the UE replied by the UDM to the AMF may be carried in the User Subscription Data Get Service Response Message (Nudm_SDM_Get_response) shown in Figure 10.

[0295] Step 1006: The AMF generates a UE Context in AMF based on the subscription information of UE1 obtained from the UDM, the indication of the "first capability", and the local configuration. Some or all parameters in the UE Context in AMF may be used by other UEs. In this step, if the UE is a first terminal, the UE Context in AMF may be the second context of the first terminal in the aforementioned embodiment; if the UE is a second terminal, the UE Context in AMF may be the context related to the second terminal in the aforementioned embodiment.

[0296] Step 1007: The AMF includes a confirmation indication in the Registration Accept message, which notifies UE1 that it is permitted or required to execute the function corresponding to the "first capability." In this step, if the UE is the first terminal, the confirmation indication may refer to the second indication information in the aforementioned embodiment; if the UE is the second terminal, the confirmation indication may refer to the fourth indication information in the aforementioned embodiment.

[0297] It should be noted that Figure 10 also illustrates other network devices, such as the SMF and RAN. The SMF is a core network device and is shown in Figure 10 for the sake of architectural integrity. The role of the SMF in the example of Figure 10 is not limited here. The RAN can be an access network device serving UE1, and its role in the example of Figure 10 is also not limited.

[0298] The process shown in Figure 10 can be executed in advance for both the first terminal and the second terminal, so that the corresponding devices on the network side know that the first terminal and the second terminal have the first capability. Then, when the first terminal needs to allocate context associated with other UEs, the process shown in Figure 11 is executed. In Figure 11, UE-2 is the first terminal in the aforementioned embodiment, UE-1 is the second terminal in the aforementioned embodiment, AMF-1 is the second network device in the aforementioned embodiment, AMF-2 is the first network device in the aforementioned embodiment, and UDM / UDR is the third network device in the aforementioned embodiment. Figure 11 mainly focuses on the processing flow when UE-2 takes over part or all of UE-1's services and needs to send UE-1's context to UE-2 for use. Specifically:

[0299] Step 1101: UE-2 sends a Registration Request message to AMF-2, which carries at least one of the following parameters: a first capability indication, i.e., the first indication information in the aforementioned embodiment, which is not described in detail here; a first request information, which indicates that AMF-2 needs to allocate some or all of the context, policy, and other information of other UEs to UE-2 for use; a first identifier, which may include one or more of the following: an identifier of the associated UE-1, i.e., the existing UE context of the UE to be allocated; an associated service (or application) identifier (i.e., the identifier of the first service), i.e., the UE context corresponding to the service to be allocated, which may be used together with the identifier of UE-1 to further define the content to be allocated, or may be used alone; an associated user identifier (i.e., the identifier of the first user), i.e., the UE context corresponding to the user identifier to be allocated, etc. Multiple UEs, such as UE-1 and UE-2, may be used by the same user, and therefore, context information between multiple UEs may be associated through the user identifier. It should be understood that the above is merely exemplary, and the first identifier may also include at least one of the identifier of the first PDU session and the identifier of the first QoS flow, etc., as shown in the aforementioned embodiment, which are not exhaustive here.

[0300] Step 1102: AMF-2 selects the corresponding PCF or UDM / UDR. The process of AMF-2 selecting the PCF and / or UDM / UDR is the same as that in the previous embodiment, and the steps are not repeated here.

[0301] Step 1103: AMF-2 sends a PCF association establishment or modification request to PCF-2, which is used to trigger PCF to send or update UE policy to the current UE-2. This embodiment does not limit the processing of this step.

[0302] The aforementioned steps 1102 and 1103 are both optional steps and are not limited here.

[0303] If the AMF serving UE-1 and UE-2 is the same, for example, both are AMF-2, then there is no need to perform the interaction processing of steps 1104a and 1104b, and step 1105 is directly executed. If the AMF serving UE-1 and UE-2 is different, step 1104a or step 1104b is executed:

[0304] In step 1104a, AMF-2 interacts with AMF-1 to obtain the UE Context allocated to UE-1 by sending a UE context request to AMF-1. The UE context request sent by AMF-2 to AMF-1 may carry an indication of the first capability and / or the first request and / or the first identifier.

[0305] In step 1104b, AMF-2 obtains the UE Context allocated to UE-1 pre-stored by AMF-1 by sending a UE context request to UDM / UDR. The UE context request sent by AMF-2 to UDM / UDR may carry the indication of the aforementioned first capability and / or the first request and / or the first identifier.

[0306] Step 1105: AMF-2 generates UE Context of UE-2 based on the obtained UE Context of UE-1. Here, UE Context of UE-2 can be the same as that of UE-1, or partially the same or partially modified. Note: The acquisition of UE Context allocated to UE-1 mentioned above can be the acquisition of all, part or related content, which is not limited here.

[0307] Step 1106: AMF-2 sends a registration accept message to UE-2. The registration accept message may carry the second information in the aforementioned embodiment, that is, the UE Context generated for UE-2 (or at least part of the parameters of the UE context) may be sent to UE-2.

[0308] It should be noted that other network devices (such as RAN, PCF-1) are also illustrated in Figure 11, which are mainly displayed in Figure 11 for the completeness of the illustrated architecture. Regarding the role of network elements illustrated in Figure 11 but not described in the aforementioned steps, this embodiment does not limit their functions.

[0309] Another exemplary description of the process of the first terminal or the second terminal sending the indication of the first capability is given in conjunction with FIG12, specifically:

[0310] Step 1201: The UE sends a session establishment request and / or session modification request message to the SMF, which may carry an indication of a "first capability". In this embodiment, since the first capability is reported for only one UE, Figure 12 may only include one UE. In one case, the UE in Figure 12 may be the aforementioned second terminal, and the SMF may be the aforementioned second network device serving the second terminal (such as the second SMF in the aforementioned embodiment); the indication of the first capability in step 1201 may be the third indication information in the aforementioned embodiment. In another case, the UE in Figure 12 may be the aforementioned first terminal, and the SMF may be the aforementioned first network device serving the first terminal (such as the first SMF in the aforementioned embodiment), and the indication of the first capability in step 1201 may be the first indication information in the aforementioned embodiment.

[0311] Step 1202: The SMF receives an indication of the first capability sent to the PCF. The PCF is the fourth network device in the aforementioned embodiment. In one case, the SMF may be the second network device serving the second terminal (such as the second SMF in the aforementioned embodiment), and the indication of the first capability in step 1202 may be carried by the fifth request message in the aforementioned embodiment. In another case, the SMF may be the first network device serving the first terminal (such as the first SMF in the aforementioned embodiment), and the indication of the first capability in step 1202 may be carried by the third request message in the aforementioned embodiment.

[0312] Step 1203: The PCF sends the PCC rules of the UE to the SMF. At least part of the PCC rules of the UE can be used by other UEs except the UE.

[0313] Step 1204: The SMF sends an indication of the first capability to the UDM / UDR. The UDM / UDR is the third network device in the aforementioned embodiment. In one case, the SMF may be the aforementioned second network device serving the second terminal (such as the second SMF in the aforementioned embodiment), and the indication of the first capability in step 1204 may be carried by the fourth request message in the aforementioned embodiment. In another case, the SMF may be the aforementioned first network device serving the first terminal (such as the first SMF in the aforementioned embodiment), and the indication of the first capability in step 1204 may be carried by the second request message in the aforementioned embodiment.

[0314] Step 1205: UDM / UDR replies to SMF with the contract information of the UE. The contract information here may be MM contract information, and all or part of the parameters of the MM contract information may be used in other UEs.

[0315] The execution order of the aforementioned steps 1202-1203 can be after steps 1204-1205 or before step 1204. There is no limitation on this. As long as the processing of steps 1202-1205 is completed before step 1206, it is within the protection scope of this example.

[0316] Step 1206: The SMF generates an SM Context for the UE based on the UE's subscription information, the UE's PCC rules, the "first capability" indication, and local configuration. Some or all parameters in the SM Context of the UE may be used by other UEs. In this step, if the UE is a first terminal, the SM Context of the UE may be the second context of the first terminal in the aforementioned embodiment; if the UE is a second terminal, the SM Context of the UE may be the context related to the second terminal in the aforementioned embodiment.

[0317] Step 1207: The SMF sends a confirmation indication to the UE, which is used to inform the UE that it is allowed or required to perform the function corresponding to the "first capability". In this step, if the UE is the first terminal, the confirmation indication may refer to the second indication information in the aforementioned embodiment; if the UE is the second terminal, the confirmation indication may be the fourth indication information in the aforementioned embodiment. It should also be understood that after step 1207 is completed, or after step 1206, the SMF may also send at least some parameters in the UE's SM Context to the UE. If the UE is the first terminal, at least some parameters of the UE's SM Context may be sent through the third information; if the UE is the second terminal, at least some parameters of the UE's SM Context may be sent through the sixth information.

[0318] It should be noted that other network devices, such as RAN, AMF, and UPF, are also illustrated in Figure 12. The AMF and UPF are devices on the core network side and are shown in Figure 12 to illustrate the completeness of the architecture. The roles of the AMF and UPF are not limited here. The RAN can be an access network device serving the UE, and the role of the RAN in the example of Figure 12 is also not limited.

[0319] In addition to the UE Context in AMF (what we usually call MM / RM Context), the UE context also has an important context, namely the SM Context (including QoS parameters, IP address, etc.). Therefore, when a service is migrated from UE-1 to UE-2, the context generated for UE-2 also needs to be consistent with or associated with the context previously generated for UE-1. The process shown in Figure 13 is mainly to achieve the purpose of ensuring that the context generated for UE-2 is consistent with or associated with the context previously generated for UE-1 when a service is migrated from UE-1 to UE-2. In Figure 13, UE-2 is the first terminal in the aforementioned embodiment, UE-1 is the second terminal in the aforementioned embodiment, SMF-1 is the second network device in the aforementioned embodiment, SMF-2 is the first network device in the aforementioned embodiment, and UDM / UDR is the third network device in the aforementioned embodiment. Specifically:

[0320] Step 1300: UE-1 completes the PDU session establishment process, generates the SM context of UE-1, and transmits data of a specific service through the PDU session.

[0321] Step 1301: UE-2 sends a PDU session establishment / modification request message to SMF-2, which includes one or more of the following parameters:

[0322] - "First Request": The "First Request" is used to indicate that some or all of the context, policy, and other information of other UEs needs to be allocated to UE-2 for use;

[0323] - "First identity" includes one or more of the following: 1) the identity of the associated UE-1: i.e., the existing UE context of the UE to be assigned, etc.; 2) the identity of the associated first service (or first application): i.e., the UE context corresponding to the service to be assigned, etc. This identity can be used together with the identity of UE-1 to further limit the content to be assigned, or it can be used alone; 3) the identity of the associated first user: i.e., the UE context corresponding to the user identity to be assigned, etc. Multiple UEs such as UE-1 and UE-2 can be used by the same user, so the context information between multiple UEs can be associated through the user identity; 4) the first PDU session ID and / or first QoS flow ID of UE-1: indicating that the SM Context of this UE-2 needs to be generated based on the context of the specific PDU session and / or QoS data flow of UE-1.

[0324] If the SMF serving UE-1 and UE-2 is the same, for example, both are SMF-2, there is no need to execute step 1302a or 1302b, and step 1303 is executed directly.

[0325] If two different SMFs serve UE-1 and UE-2, step 1302a or 1302b needs to be performed:

[0326] Step 1302a: SMF-2 requests an SM context (which may include a first request and / or a first identifier) ​​from SMF-1. Specifically, SMF-2 obtains the SM context allocated to UE-1 by sending an SM context request to SMF-1.

[0327] Step 1302b: SMF-2 requests an SM context from the UDM / UDR (which may include a first request and / or a first identifier). SMF-2 obtains the SM context allocated to UE-1 by sending an SM context request to the UDM / UDR.

[0328] Step 1303: SMF-2 generates UE-2's SM Context based on the obtained UE-1's SM Context parameters, UE-2's own subscription information and / or local configuration. UE-2's SM Context parameters may be the same as, partially the same as, or modified from those of UE-1. This is because different UEs have different parameters, such as different resolutions and bit rates. Some parameters, such as QOS, will be adjusted accordingly rather than directly copied.

[0329] Steps 1304-1307: SMF-2 interacts with other core network elements (such as UPF), RAN, and UE-2 based on UE-2's SM Context to complete the establishment / modification of the PDU session.

[0330] For example, in step 1304, SMF-2 sends an N4 session establishment / modification request to the UPF, and then starts executing other existing session establishment steps. In step 1305, SMF-2 sends an N1 and N2 interface communication message transfer message (Namf_Communiaction_N1N2Message Transfer) to the AMF (for example, it can be the AMF-2 serving UE-2). In step 1306, the AMF sends a request (N2PDU Session Request) (NAS message) to allocate PDU session resources to the RAN. In step 1307, AN related resources are established (that is, RAN and UE-2 establish related resources). At the same time as the resources are established, the RAN will send a downlink PDU session establishment reply message containing the SM context (Context) on the UE-2 side.

[0331] Step 1308: If some of UE-1's SM context parameters (e.g., IP address) are allocated to UE-2, the corresponding parameters for UE-1's PDU session need to be released. This is because some or all of UE-1's SM context has been generated for UE-2, so the corresponding parameters for UE-1's PDU session need to be modified or deleted. This step is optional.

[0332] By adopting the solution provided in this embodiment, the first terminal can request that a context related to at least part of the context of the second terminal be assigned to it by sending the first information. Thus, by assigning the context related to the second terminal to the first terminal, at least part of the second terminal's services can be migrated to a different device, thereby achieving the effect of coordinating the same service on multiple devices, and ensuring service continuity while achieving service migration.

[0333] Furthermore, the solution provided in this embodiment can be enhanced in the existing registration / session process to achieve the migration or copying of at least part of the context of the second terminal to the first terminal and its network-side device for use; in this embodiment, the migration or copying of context content can also be achieved by indicating a first identifier, such as a first service identifier, a first user identifier or an association relationship between terminals.

[0334] FIG14 is a schematic diagram of the structure of a first terminal according to an embodiment of the present application, including:

[0335] The first communication unit 1401 is configured to send first information, where the first information is used to request allocation of a first context of the first terminal, where the first context of the first terminal is related to at least a portion of a context of the second terminal.

[0336] The first context of the first terminal includes at least one of the following: a first part of parameters in the context related to the second terminal; and related parameters of a second part of parameters in the context related to the second terminal.

[0337] The context related to the second terminal includes at least one of the following: the context corresponding to the second terminal; the context corresponding to the first service run by the second terminal; the context corresponding to the first user using the second terminal; the context corresponding to the first protocol data unit PDU session of the second terminal; the context corresponding to the first quality of service QoS flow of the second terminal.

[0338] The first information includes a first identifier, wherein the first identifier includes at least one of the following: an identifier of the second terminal, an identifier of the first service, an identifier of the first user, an identifier of the first PDU session, and an identifier of the first QoS flow.

[0339] The first communication unit is configured to receive second information, wherein the second information includes at least some parameters of a first context of the first terminal.

[0340] The first information is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

[0341] The first communication unit is used to send a first indication information, wherein the first indication information is used to indicate that the first terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

[0342] The first indication information is also used to indicate at least one of the following: the first terminal requests to execute the function corresponding to the first capability; the first terminal requires to execute the function corresponding to the first capability; the first terminal supports the execution of the function corresponding to the first capability; the first terminal agrees to execute the function corresponding to the first capability; the first terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

[0343] The first indication information includes identifiers of the one or more other terminals, and the one or more other terminals include the second terminal.

[0344] The first communication unit is used to receive second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to perform the function corresponding to the first capability, and requiring the first terminal to perform the function corresponding to the first capability.

[0345] The first communication unit is configured to receive third information, wherein the third information includes at least some parameters of the second context of the first terminal, and the second context of the first terminal includes at least some context that can be allocated to one or more other terminals.

[0346] The first indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

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

[0348] The second communication unit 1501 is configured to receive first information, wherein the first information is used to request allocation of a first context of a first terminal, where the first context of the first terminal is related to at least a portion of a context of a second terminal.

[0349] The first context of the first terminal includes at least one of the following: a first part of parameters in the context related to the second terminal; and related parameters of a second part of parameters in the context related to the second terminal.

[0350] The context related to the second terminal includes at least one of the following: the context corresponding to the second terminal; the context corresponding to the first service run by the second terminal; the context corresponding to the first user using the second terminal; the context corresponding to the first protocol data unit PDU session of the second terminal; the context corresponding to the first quality of service QoS flow of the second terminal.

[0351] The first information includes a first identifier.

[0352] As shown in FIG15 , the first network device further includes a second processing unit 1502:

[0353] The second processing unit 1502 is configured to generate a first context of the first terminal based on the context related to the second terminal;

[0354] The second communication unit is configured to obtain a context related to the second terminal.

[0355] The first network device serves the first terminal and the second terminal.

[0356] The second communication unit is used to perform one of the following: sending fourth information to the second network device, and receiving the context related to the second terminal sent by the second network device, wherein the fourth information is used to request to obtain the context related to the second terminal; sending fifth information to the third network device, and receiving the context related to the second terminal sent by the third network device, wherein the fifth information is used to request to obtain the context related to the second terminal.

[0357] The fourth information includes the first identifier, and / or the fifth information includes the first identifier.

[0358] The first identifier includes at least one of the following: an identifier of the second terminal, an identifier of the first service, an identifier of the first user, an identifier of the first PDU session, and an identifier of the first QoS flow.

[0359] The first network device serves the first terminal; the second network device serves the second terminal; and the third network device is used to store context related to the second terminal.

[0360] The second communication unit is configured to send second information, wherein the second information includes at least some parameters of the first context of the first terminal.

[0361] The first information is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

[0362] The second communication unit is used to receive first indication information, wherein the first indication information is used to indicate that the first terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

[0363] The first indication information is also used to indicate at least one of the following: the first terminal requests to execute the function corresponding to the first capability; the first terminal requires to execute the function corresponding to the first capability; the first terminal supports the execution of the function corresponding to the first capability; the first terminal agrees to execute the function corresponding to the first capability; the first terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

[0364] The first indication information includes an identifier of each of the one or more other terminals, and the one or more other terminals include the second terminal.

[0365] The second communication unit is used to send second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to perform the function corresponding to the first capability, and requiring the first terminal to perform the function corresponding to the first capability.

[0366] The second communication unit is configured to obtain the contract information of the first terminal from the third network device, where the contract information of the first terminal includes at least part of the contract information that can be used by one or more other terminals;

[0367] The second processing unit is configured to generate a second context of the first terminal based on the subscription information of the first terminal, where the second context of the first terminal includes at least a portion of the context that can be allocated to one or more other terminals.

[0368] The second communication unit is configured to obtain a policy and charging control (PCC) rule of the first terminal from a fourth network device, where the PCC rule of the first terminal includes at least part of the PCC rules that can be used by one or more other terminals;

[0369] The second processing unit is configured to generate a second context of the first terminal based on the subscription information of the first terminal and the PCC rule of the first terminal.

[0370] The second communication unit is configured to send third information, wherein the third information includes at least some parameters of the second context of the first terminal.

[0371] The fourth network device includes: a policy control function PCF.

[0372] The first indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

[0373] The third network device includes at least one of the following: a unified data management function UDM, a unified data warehouse function UDR.

[0374] The first network device includes a first access and mobility management function AMF, and the second network device includes a second AMF; or, the first network device includes a first session management function SMF, and the second network device includes a second SMF.

[0375] FIG16 is a schematic diagram of the structure of a second terminal according to an embodiment of the present application, including:

[0376] The third communication unit 1601 is used to send a third indication information, wherein the third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

[0377] The third indication information is also used to indicate at least one of the following: the second terminal requests to execute the function corresponding to the first capability; the second terminal requires to execute the function corresponding to the first capability; the second terminal supports executing the function corresponding to the first capability; the second terminal agrees to execute the function corresponding to the first capability; the second terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

[0378] The third indication information includes identifiers of the one or more other terminals.

[0379] The third communication unit is used to receive fourth indication information, wherein the fourth indication information is used to indicate one of the following: supporting the second terminal to perform the function corresponding to the first capability, and requiring the second terminal to perform the function corresponding to the first capability.

[0380] The third communication unit is configured to receive sixth information, wherein the sixth information includes at least some parameters of the context related to the second terminal, and the context related to the second terminal includes at least some context that can be allocated to one or more other terminals.

[0381] The third indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

[0382] FIG17 is a schematic diagram of the structure of a second network device according to an embodiment of the present application, including:

[0383] The fourth communication unit 1701 is used to receive third indication information, wherein the third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

[0384] The third indication information is also used to indicate at least one of the following: the second terminal requests to execute the function corresponding to the first capability; the second terminal requires to execute the function corresponding to the first capability; the second terminal supports executing the function corresponding to the first capability; the second terminal agrees to execute the function corresponding to the first capability; the second terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

[0385] The third indication information includes an identifier of each other terminal in the one or more other terminals.

[0386] The fourth communication unit is used to send fourth indication information, wherein the fourth indication information is used to indicate one of the following: supporting the second terminal to perform the function corresponding to the first capability, and requiring the second terminal to perform the function corresponding to the first capability.

[0387] As shown in FIG17 , the second network device further includes a fourth processing unit 1702:

[0388] The fourth processing unit 1702 is configured to generate a context related to the second terminal based on the subscription information of the second terminal, where the context related to the second terminal includes at least a portion of the context that can be allocated to one or more other terminals;

[0389] The fourth communication unit is used to obtain the contract information of the second terminal from the third network device, where the contract information of the second terminal includes at least part of the contract information that can be used by one or more other terminals.

[0390] The fourth communication unit is configured to obtain a policy and charging control (PCC) rule of the second terminal from a fourth network device, where the PCC rule of the second terminal includes at least part of the PCC rules that can be used by one or more other terminals;

[0391] The fourth processing unit is configured to generate a context related to the second terminal based on the subscription information of the second terminal and the PCC rule of the second terminal.

[0392] The fourth communication unit is configured to send sixth information, wherein the sixth information includes at least some parameters of the context related to the second terminal.

[0393] The third indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

[0394] The second network device includes a second access and mobility management function AMF or a second session management function SMF.

[0395] The device of the embodiment of the present application can realize the corresponding functions of each device in the aforementioned communication method embodiment. The process, function, implementation method and beneficial effect corresponding to each module (submodule, unit or component, etc.) in the first terminal device, or the first network device, or the second terminal, or the second 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 first terminal device, or the first network device, or the second terminal, or the second network device of the embodiment of the application can be implemented by different modules (submodules, units or components, etc.), or by the same module (submodule, unit or component, etc.).

[0396] Figure 18 is a schematic diagram of a communication device 1800 according to an embodiment of the present application. The communication device 1800 includes a processor 1810, which can retrieve and execute computer programs from a memory to enable the communication device 1800 to implement the methods according to the embodiments of the present application. In one possible implementation, the communication device 1800 may also include a memory 1820. The processor 1810 can retrieve and execute computer programs from the memory 1820 to enable the communication device 1800 to implement the methods according to the embodiments of the present application. The memory 1820 may be a separate device independent of the processor 1810 or integrated into the processor 1810. In one possible implementation, the communication device 1800 may also include a transceiver 1830. The processor 1810 may control the transceiver 1830 to communicate with other devices. Specifically, the transceiver 1830 may send information or data to other devices or receive information or data sent by other devices. The transceiver 1830 may include a transmitter and a receiver. The transceiver 1830 may further include one or more antennas.

[0397] In one possible implementation, the communication device 1800 may be the first terminal device, or the first network device, or the second terminal, or the second network device of the embodiment of the present application, and the communication device 1800 may implement the corresponding processes implemented by the first terminal device, or the first network device, or the second terminal, or the second network device in the various methods of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0398] Figure 19 is a schematic structural diagram of a chip 1900 according to an embodiment of the present application. The chip 1900 includes a processor 1910, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application. In one possible implementation, the chip 1900 may also include a memory 1920. The processor 1910 can call and execute a computer program from the memory 1920 to implement the method performed by the first device or the target second device in the embodiment of the present application. The memory 1920 can be a separate device independent of the processor 1910 or integrated into the processor 1910. In one possible implementation, the chip 1900 may also include an input interface 1930. The processor 1910 can control the input interface 1930 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips. In one possible implementation, the chip 1900 may also include an output interface 1940. The processor 1910 may control the output interface 1940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0399] In one possible implementation, the chip can be applied to the first terminal device, or the first network device, or the second terminal, or the second network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first terminal device, or the first network device, or the second terminal, or the second network device in each method 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 device, a transistor logic device, a discrete hardware component, 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 memory. 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.

[0400] Figure 20 is a schematic block diagram of a communication system 2000 according to an embodiment of the present application. The communication system 2000 includes a first terminal 2030, a first network device 2010, a second terminal 2040, and a second network device 2020. The first terminal 2030 can be used to implement the corresponding functions implemented by the first terminal in the above-mentioned method. The first network device 2010 can be used to implement the corresponding functions implemented by the first network device in the above-mentioned method. The second terminal 2040 can be used to implement the corresponding functions implemented by the second terminal in the above-mentioned method. The second network device 2020 can be used to implement the corresponding functions implemented by the second network device in the above-mentioned method. For the sake of brevity, these steps will not be described in detail here.

[0401] 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)).

[0402] 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: The first terminal sends first information, wherein the first information is used to request allocation of a first context of the first terminal, and the first context of the first terminal is related to at least a portion of a context of a second terminal.

2. The method according to claim 1, wherein: The first context of the first terminal includes at least one of the following: a first part of parameters in the context related to the second terminal; and related parameters of a second part of parameters in the context related to the second terminal.

3. The method according to claim 2, wherein: The context related to the second terminal includes at least one of the following: a context corresponding to the second terminal; a context corresponding to the first service running on the second terminal; Use the context corresponding to the first user of the second terminal; the context corresponding to the first protocol data unit PDU session of the second terminal; and the context corresponding to the first quality of service QoS flow of the second terminal.

4. The method according to any one of claims 1 to 3, wherein: The first information includes a first identifier, wherein the first identifier includes at least one of the following: an identifier of the second terminal, an identifier of the first service, an identifier of the first user, an identifier of the first PDU session, and an identifier of the first QoS flow.

5. The method according to any one of claims 1 to 4, wherein: After the first terminal sends the first information, the method further includes: The first terminal receives second information, where the second information includes at least part of parameters of a first context of the first terminal.

6. The method according to any one of claims 1 to 5, wherein: The first information is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

7. The method according to any one of claims 1 to 6, wherein: The method further comprises: The first terminal sends a first indication message, wherein the first indication message is used to indicate that the first terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the terminal.

8. The method according to claim 7, wherein: The first indication information is also used to indicate at least one of the following: the first terminal requests to execute the function corresponding to the first capability; the first terminal requires to execute the function corresponding to the first capability; the first terminal supports to execute the function corresponding to the first capability; the first terminal agrees to execute the function corresponding to the first capability; the first terminal requests to be allowed to execute the function corresponding to the first capability with one or more other terminals.

9. The method according to claim 7 or 8, wherein: The first indication information includes identifiers of the one or more other terminals, and the one or more other terminals include the second terminal.

10. The method according to any one of claims 7 to 9, wherein: After the first terminal sends the first indication information, the method further includes: The first terminal receives second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to execute a function corresponding to the first capability, and requiring the first terminal to execute a function corresponding to the first capability.

11. The method according to any one of claims 7 to 10, wherein: After the first terminal sends the first indication information, the method further includes: The first terminal receives third information, wherein the third information includes at least part of parameters of a second context of the first terminal, and the second context of the first terminal includes at least part of a context that can be allocated to one or more other terminals.

12. The method according to any one of claims 7 to 11, wherein: The first indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

13. A communication method, comprising: The first network device receives first information, wherein the first information is used to request allocation of a first context of a first terminal, where the first context of the first terminal is related to at least a portion of a context of a second terminal.

14. The method according to claim 13, wherein: The first context of the first terminal includes at least one of the following: a first part of parameters in the context related to the second terminal; and related parameters of a second part of parameters in the context related to the second terminal.

15. The method according to claim 14, wherein: The context related to the second terminal includes at least one of the following: a context corresponding to the second terminal; a context corresponding to the first service running on the second terminal; Use the context corresponding to the first user of the second terminal; the context corresponding to the first protocol data unit PDU session of the second terminal; and the context corresponding to the first quality of service QoS flow of the second terminal.

16. The method according to any one of claims 13 to 15, wherein: The first information includes a first identifier.

17. The method according to any one of claims 13 to 16, wherein: After the first network device receives the first information, the method further includes: The first network device acquires a context related to the second terminal; The first network device generates a first context of the first terminal based on the context related to the second terminal.

18. The method according to claim 17, wherein: The first network device serves the first terminal and the second terminal.

19. The method according to claim 17, wherein: The first network device acquires the context related to the second terminal, including one of the following: The first network device sends fourth information to the second network device, and receives the context related to the second terminal sent by the second network device, wherein the fourth information is used to request to obtain the context related to the second terminal; The first network device sends fifth information to the third network device, and receives the context related to the second terminal sent by the third network device, wherein the fifth information is used to request to obtain the context related to the second terminal.

20. The method according to claim 19, wherein: The fourth information includes the first identifier, and / or the fifth information includes the first identifier.

21. The method according to claim 16 or 20, wherein: The first identifier includes at least one of the following: an identifier of the second terminal, an identifier of the first service, an identifier of the first user, an identifier of the first PDU session, and an identifier of the first QoS flow.

22. The method according to claim 19 or 20, wherein: The first network device serves the first terminal; the second network device serves the second terminal; and the third network device is used to store context related to the second terminal.

23. The method according to any one of claims 13 to 22, wherein: After the first network device receives the first information, the method further includes: The first network device sends second information, wherein the second information includes at least part of parameters of the first context of the first terminal.

24. The method according to any one of claims 13 to 23, wherein: The first information is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

25. The method according to any one of claims 13 to 24, wherein: The method further comprises: The first network device receives first indication information, wherein the first indication information is used to indicate that the first terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the terminal.

26. The method according to claim 25, wherein: The first indication information is also used to indicate at least one of the following: the first terminal requests to execute the function corresponding to the first capability; the first terminal requires to execute the function corresponding to the first capability; the first terminal supports to execute the function corresponding to the first capability; the first terminal agrees to execute the function corresponding to the first capability; the first terminal requests to be allowed to execute the function corresponding to the first capability with one or more other terminals.

27. The method according to claim 25 or 26, wherein: The first indication information includes an identifier of each other terminal in the one or more other terminals, and the one or more other terminals include the second terminal.

28. The method according to any one of claims 25 to 27, wherein: After the first network device receives the first indication information, the method further includes: The first network device sends second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to execute the function corresponding to the first capability, and requiring the first terminal to execute the function corresponding to the first capability.

29. The method according to any one of claims 25 to 28, wherein: After the first network device receives the first indication information, the method further includes: The first network device obtains the contract information of the first terminal from the third network device, wherein the contract information of the first terminal includes including at least part of the subscription information that can be used by one or more other terminals; The first network device generates a second context of the first terminal based on the subscription information of the first terminal, where the second context of the first terminal includes at least a portion of the context that can be allocated to one or more other terminals.

30. The method of claim 29, wherein: The method further includes: the first network device acquiring a policy and charging control PCC rule of the first terminal from a fourth network device, wherein the PCC rule of the first terminal includes at least part of the PCC rules that can be used by one or more other terminals; The first network device generates a second context of the first terminal based on the subscription information of the first terminal, including: the first network device generates the second context of the first terminal based on the subscription information of the first terminal and the PCC rule of the first terminal.

31. The method according to claim 29 or 30, wherein: After generating the second context of the first terminal, the method further includes: The first network device sends third information, wherein the third information includes at least part of parameters of the second context of the first terminal.

32. The method of claim 30, wherein: The fourth network device includes: a policy control function PCF.

33. The method according to any one of claims 25 to 32, wherein: The first indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

34. The method according to any one of claims 19 to 22 and 29, wherein: The third network device includes at least one of the following: a unified data management function UDM and a unified data warehouse function UDR.

35. The method according to any one of claims 19 to 22, wherein: The first network device includes a first access and mobility management function AMF, and the second network device includes a second AMF; Alternatively, the first network device includes a first session management function SMF, and the second network device includes a second SMF.

36. A communication method, comprising: The second terminal sends a third indication message, wherein the third indication message is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the terminal.

37. The method of claim 36, wherein: The third indication information is also used to indicate at least one of the following: the second terminal requests to execute the function corresponding to the first capability; the second terminal requires to execute the function corresponding to the first capability; the second terminal supports executing the function corresponding to the first capability; the second terminal agrees to execute the function corresponding to the first capability; the second terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

38. The method according to claim 36 or 37, wherein: The third indication information includes identifications of the one or more other terminals.

39. The method according to any one of claims 36 to 38, wherein: After the second terminal sends the third indication information, the method further includes: The second terminal receives fourth indication information, where the fourth indication information is used to indicate one of the following: supporting the second terminal to execute the function corresponding to the first capability, and requiring the second terminal to execute the function corresponding to the first capability.

40. The method according to any one of claims 36 to 39, wherein: After the second terminal sends the third indication information, the method further includes: The second terminal receives sixth information, wherein the sixth information includes at least part of parameters of a context related to the second terminal, and the context related to the second terminal includes at least part of a context that can be allocated to one or more other terminals.

41. The method according to any one of claims 36 to 40, wherein: The third indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

42. A communication method, comprising: The second network device receives third indication information, wherein the third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: supporting or allowing at least part of the context-related context of the terminal to be allocated to one or more The capability of the present terminal is to support or allow at least part of the context-related contexts of one or more other terminals to be allocated to the present terminal.

43. The method of claim 42, wherein: The third indication information is also used to indicate at least one of the following: the second terminal requests to execute the function corresponding to the first capability; the second terminal requires to execute the function corresponding to the first capability; the second terminal supports executing the function corresponding to the first capability; the second terminal agrees to execute the function corresponding to the first capability; the second terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

44. The method according to claim 42 or 43, wherein: The third indication information includes an identifier of each other terminal in the one or more other terminals.

45. The method according to any one of claims 42 to 44, wherein: After the second network device receives the third indication information, the method further includes: The second network device sends fourth indication information, wherein the fourth indication information is used to indicate one of the following: supporting the second terminal to execute the function corresponding to the first capability, and requiring the second terminal to execute the function corresponding to the first capability.

46. ​​The method according to any one of claims 42 to 45, wherein: After the second network device receives the third indication information, the method further includes: The second network device obtains the contract information of the second terminal from the third network device, where the contract information of the second terminal includes at least part of the contract information that can be used by one or more other terminals; The second network device generates a context related to the second terminal based on the subscription information of the second terminal, where the context related to the second terminal includes at least a portion of the context that can be allocated to one or more other terminals.

47. The method of claim 46, wherein: The method further includes: the second network device acquires a policy and charging control PCC rule of the second terminal from a fourth network device, wherein the PCC rule of the second terminal includes at least part of the PCC rules that can be used by one or more other terminals; The second network device generates a context related to the second terminal based on the subscription information of the second terminal, including: the second network device generates a context related to the second terminal based on the subscription information of the second terminal and the PCC rule of the second terminal.

48. The method according to claim 46 or 47, wherein: After the second network device receives the third indication information, the method further includes: The second network device sends sixth information, wherein the sixth information includes at least part of parameters of the context related to the second terminal.

49. The method according to any one of claims 42 to 48, wherein: The third indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

50. The method according to any one of claims 42 to 49, wherein: The second network device includes a second access and mobility management function AMF or a second session management function SMF.

51. A first terminal, comprising: The first communication unit is configured to send first information, wherein the first information is used to request allocation of a first context of the first terminal, and the first context of the first terminal is related to at least a portion of a context of a second terminal.

52. The first terminal according to claim 51, wherein: The first context of the first terminal includes at least one of the following: a first part of parameters in the context related to the second terminal; and related parameters of a second part of parameters in the context related to the second terminal.

53. The first terminal according to claim 52, wherein: The context related to the second terminal includes at least one of the following: a context corresponding to the second terminal; a context corresponding to the first service running on the second terminal; Use the context corresponding to the first user of the second terminal; the context corresponding to the first protocol data unit PDU session of the second terminal; and the context corresponding to the first quality of service QoS flow of the second terminal.

54. The first terminal according to any one of claims 51 to 53, wherein: The first information includes a first identifier, wherein the first identifier includes at least one of the following: an identifier of the second terminal, an identifier of the first service, an identifier of the first user, an identifier of the first PDU session, and an identifier of the first QoS flow.

55. The first terminal according to any one of claims 51 to 54, wherein: The first communication unit is configured to receive second information, wherein the second information includes at least part of parameters of a first context of the first terminal.

56. The first terminal according to any one of claims 51 to 55, wherein: The first information is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

57. The first terminal according to any one of claims 51 to 56, wherein: The first communication unit is used to send first indication information, wherein the first indication information is used to indicate that the first terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

58. The first terminal according to claim 57, wherein: The first indication information is also used to indicate at least one of the following: the first terminal requests to execute the function corresponding to the first capability; the first terminal requires to execute the function corresponding to the first capability; the first terminal supports to execute the function corresponding to the first capability; the first terminal agrees to execute the function corresponding to the first capability; the first terminal requests to be allowed to execute the function corresponding to the first capability with one or more other terminals.

59. The first terminal according to claim 57 or 58, wherein: The first indication information includes identifiers of the one or more other terminals, and the one or more other terminals include the second terminal.

60. The first terminal according to any one of claims 57 to 59, wherein: The first communication unit is used to receive second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to execute the function corresponding to the first capability, and requiring the first terminal to execute the function corresponding to the first capability.

61. The first terminal according to any one of claims 57 to 60, wherein: The first communication unit is configured to receive third information, wherein the third information includes at least part of parameters of a second context of the first terminal, and the second context of the first terminal includes at least part of a context that can be allocated to one or more other terminals.

62. The first terminal according to any one of claims 57 to 61, wherein: The first indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

63. A first network device, comprising: The second communication unit is configured to receive first information, wherein the first information is used to request allocation of a first context of a first terminal, and the first context of the first terminal is related to at least a portion of a context of a second terminal.

64. The first network device according to claim 63, wherein: The first context of the first terminal includes at least one of the following: a first part of parameters in the context related to the second terminal; and related parameters of a second part of parameters in the context related to the second terminal.

65. The first network device according to claim 64, wherein: The context related to the second terminal includes at least one of the following: a context corresponding to the second terminal; a context corresponding to the first service running on the second terminal; Use the context corresponding to the first user of the second terminal; the context corresponding to the first protocol data unit PDU session of the second terminal; and the context corresponding to the first quality of service QoS flow of the second terminal.

66. The first network device according to any one of claims 63 to 65, wherein: The first information includes a first identifier.

67. The first network device according to any one of claims 63 to 66, wherein: The first network device also includes a second processing unit: The second processing unit is configured to generate a first context of the first terminal based on the context related to the second terminal; The second communication unit is used to obtain the context related to the second terminal.

68. The first network device according to claim 67, wherein: The first network device serves the first terminal and the second terminal.

69. The first network device according to claim 67, wherein: The second communication unit is used to perform one of the following: sending fourth information to the second network device, receiving the context related to the second terminal sent by the second network device, wherein the fourth information is used to request to obtain the context related to the second terminal; sending fifth information to the third network device, receiving the context related to the second terminal sent by the third network device, wherein the fifth information is used to request to obtain the context related to the second terminal.

70. The first network device according to claim 69, wherein: The fourth information includes the first identifier, and / or the fifth information includes the first identifier.

71. The first network device according to claim 66 or 70, wherein: The first identifier includes at least one of the following: an identifier of the second terminal, an identifier of the first service, an identifier of the first user, an identifier of the first PDU session, and an identifier of the first QoS flow.

72. The first network device according to claim 69 or 70, wherein: The first network device serves the first terminal; the second network device serves the second terminal; and the third network device is used to store context related to the second terminal.

73. The first network device according to any one of claims 63 to 72, wherein: The second communication unit is used to send second information, wherein the second information includes at least part of parameters of the first context of the first terminal.

74. The first network device according to any one of claims 63 to 73, wherein: The first information is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

75. The first network device according to any one of claims 63-74, wherein: The second communication unit is used to receive first indication information, wherein the first indication information is used to indicate that the first terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of the current terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to the current terminal.

76. The first network device according to claim 75, wherein: The first indication information is also used to indicate at least one of the following: the first terminal requests to execute the function corresponding to the first capability; the first terminal requires to execute the function corresponding to the first capability; the first terminal supports to execute the function corresponding to the first capability; the first terminal agrees to execute the function corresponding to the first capability; the first terminal requests to be allowed to execute the function corresponding to the first capability with one or more other terminals.

77. The first network device according to claim 75 or 76, wherein: The first indication information includes an identifier of each other terminal in the one or more other terminals, and the one or more other terminals include the second terminal.

78. The first network device according to any one of claims 75 to 77, wherein: The second communication unit is used to send second indication information, wherein the second indication information is used to indicate one of the following: supporting the first terminal to execute the function corresponding to the first capability, and requiring the first terminal to execute the function corresponding to the first capability.

79. The first network device according to any one of claims 75 to 78, wherein: The second communication unit is configured to obtain the contract information of the first terminal from the third network device, where the contract information of the first terminal includes at least part of the contract information that can be used by one or more other terminals; The second processing unit is configured to generate a second context of the first terminal based on the subscription information of the first terminal, where the second context of the first terminal includes at least a portion of the context that can be allocated to one or more other terminals.

80. The first network device according to claim 79, wherein: The second communication unit is configured to obtain a policy and charging control PCC rule of the first terminal from a fourth network device, where the PCC rule of the first terminal includes at least part of the PCC rules that can be used by one or more other terminals; The second processing unit is configured to generate a second context of the first terminal based on the subscription information of the first terminal and the PCC rule of the first terminal.

81. The first network device according to claim 79 or 80, wherein: The second communication unit is configured to send third information, wherein the third information includes at least part of parameters of the second context of the first terminal.

82. The first network device according to claim 80, wherein: The fourth network device includes: a policy control function PCF.

83. The first network device according to any one of claims 75 to 82, wherein: The first indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

84. The first network device according to any one of claims 69-72 and 79, wherein: The third network device includes at least one of the following: a unified data management function UDM and a unified data warehouse function UDR.

85. The first network device according to any one of claims 69 to 72, wherein: The first network device includes a first access and mobility management function AMF, and the second network device includes a second AMF; or, the first network device includes a first session management function SMF, and the second network device includes a second SMF.

86. A second terminal, comprising: A third communication unit is used to send third indication information, wherein the third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

87. The second terminal according to claim 86, wherein: The third indication information is also used to indicate at least one of the following: the second terminal requests to execute the function corresponding to the first capability; the second terminal requires to execute the function corresponding to the first capability; the second terminal supports executing the function corresponding to the first capability; the second terminal agrees to execute the function corresponding to the first capability; the second terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

88. The second terminal according to claim 86 or 87, wherein: The third indication information includes identifications of the one or more other terminals.

89. The second terminal according to any one of claims 86 to 88, wherein: The third communication unit is used to receive fourth indication information, wherein the fourth indication information is used to indicate one of the following: supporting the second terminal to execute the function corresponding to the first capability, and requiring the second terminal to execute the function corresponding to the first capability.

90. The second terminal according to any one of claims 86 to 89, wherein: The third communication unit is used to receive sixth information, wherein the sixth information includes at least part of the parameters of the context related to the second terminal, and the context related to the second terminal includes at least part of the context that can be allocated to one or more other terminals.

91. The second terminal according to any one of claims 86 to 90, wherein: The third indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

92. A second network device, comprising: A fourth communication unit is used to receive third indication information, wherein the third indication information is used to indicate that the second terminal has a first capability, and the first capability includes at least one of the following: the ability to support or allow at least part of the context-related context of this terminal to be allocated to one or more other terminals, and the ability to support or allow at least part of the context-related context of one or more other terminals to be allocated to this terminal.

93. The second network device according to claim 92, wherein: The third indication information is also used to indicate at least one of the following: the second terminal requests to execute the function corresponding to the first capability; the second terminal requires to execute the function corresponding to the first capability; the second terminal supports executing the function corresponding to the first capability; the second terminal agrees to execute the function corresponding to the first capability; the second terminal requests permission to execute the function corresponding to the first capability with one or more other terminals.

94. The second network device according to claim 92 or 93, wherein: The third indication information includes an identifier of each other terminal in the one or more other terminals.

95. The second network device according to any one of claims 92 to 94, wherein: The fourth communication unit is used to send fourth indication information, wherein the fourth indication information is used to indicate one of the following: supporting the second terminal to execute the function corresponding to the first capability, and requiring the second terminal to execute the function corresponding to the first capability.

96. The second network device according to any one of claims 92-95, wherein: The second network device further includes a fourth processing unit: The fourth processing unit is configured to generate a context related to the second terminal based on the subscription information of the second terminal, where the context related to the second terminal includes at least part of the context that can be allocated to one or more other terminals; The fourth communication unit is used to obtain the contract information of the second terminal from the third network device, and the contract information of the second terminal includes at least part of the contract information that can be used by one or more other terminals.

97. The second network device according to claim 96, wherein: The fourth communication unit is configured to obtain a policy and charging control PCC rule of the second terminal from a fourth network device, where the PCC rule of the second terminal includes at least part of the PCC rules that can be used by one or more other terminals; The fourth processing unit is configured to generate a context related to the second terminal based on the subscription information of the second terminal and the PCC rule of the second terminal.

98. The second network device according to claim 96 or 97, wherein: The fourth communication unit is used to send sixth information, wherein the sixth information includes at least part of parameters of the context related to the second terminal.

99. The second network device according to any one of claims 92 to 98, wherein: The third indication information is carried by one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.

100. The second network device according to any one of claims 92-99, wherein: The second network device includes a second access and mobility management function AMF or a second session management function SMF.

101. A first terminal, comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory, so that the first terminal executes the method as claimed in any one of claims 1 to 12.

102. A first network device, comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory so that the first network device executes the method as described in any one of claims 13 to 35.

103. A second terminal, comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory so that the second terminal executes the method as described in any one of claims 36 to 41.

104. A second network device, comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, the processor being used to call and run the computer program stored in the memory so that the second network device executes the method as described in any one of claims 42 to 50.

105. A chip, comprising: A processor, configured to call and run a computer program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1 to 12, or claims 13 to 35, or claims 36 to 41, or claims 42 to 50.

106. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method as claimed in any one of claims 1 to 12, or claims 13 to 35, or claims 36 to 41, or claims 42 to 50.

107. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 12, or claims 13 to 35, or claims 36 to 41, or claims 42 to 50.

108. A computer program, the computer program causing a computer to perform the method of any one of claims 1 to 12, or claims 13 to 35, or claims 36 to 41, or claims 42 to 50.

Images