Communication methods, and device

Abstract

The present application relates to communication methods, a device, a computer-readable storage medium, a computer program product and a computer program. A method comprises: on the basis of input information, a first network element generates first part of parameters corresponding to a terminal, the first part of parameters corresponding to the terminal comprising at least one of the followings: first part of context parameters of the terminal, and first part of policies of the terminal; and the first network element sends a reply message to one or multiple nodes, the reply message carrying at least part of content in the first part of parameters corresponding to the terminal, and the one or multiple nodes comprising at least one of the followings: the terminal, an access network device corresponding to the terminal, and one or multiple core network elements.

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] The current 3GPP system requires the definition of each interaction process. Specifically, processes involving the generation of terminal context and / or policies require the collaboration and interaction of multiple nodes to generate the corresponding terminal context and / or policies. This process, therefore, suffers from the inability to flexibly assign terminal context parameters and / or policies to each node.

[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] The first network element generates, based on the input information, a first portion of parameters corresponding to the terminal, wherein the first portion of parameters corresponding to the terminal includes at least one of the following: a first portion of context parameters of the terminal, and a first portion of policies of the terminal;

[0007] The first network element sends a reply message to one or more nodes, wherein the reply message carries at least part of the content of the first part of parameters corresponding to the terminal, and the one or more nodes include at least one of the following: the terminal, the access network device corresponding to the terminal, and one or more core network network elements.

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

[0009] The target node receives a reply message sent by the first network element, wherein the reply message carries at least part of the content of the first part parameters corresponding to the terminal, and the first part parameters corresponding to the terminal include at least one of the following: the first part context parameters of the terminal and the first part policy of the terminal.

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

[0011] A first processing unit is configured to generate a first portion of parameters corresponding to the terminal based on input information, wherein the first portion of parameters corresponding to the terminal includes at least one of the following: a first portion of context parameters of the terminal and a first portion of policies of the terminal;

[0012] A first communication unit is used to send a reply message to one or more nodes, wherein the reply message carries at least part of the content of the first part of parameters corresponding to the terminal, and the one or more nodes include at least one of the following: the terminal, the access network device corresponding to the terminal, and one or more core network elements.

[0013] An embodiment of the present application provides a target node, including:

[0014] The second communication unit is used to receive a reply message sent by the first network element, wherein the reply message carries at least part of the content of the first part parameters corresponding to the terminal, and the first part parameters corresponding to the terminal include at least one of the following: the first part context parameters of the terminal and the first part policy of the terminal.

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

[0016] An embodiment of the present application provides a target node, 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 target node executes the above method.

[0017] The embodiment of the present application provides a chip for implementing the above method.

[0018] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.

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

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

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

[0022] By adopting the solution provided in this embodiment, the first network element can generate at least a partial context and / or at least a partial policy of the terminal based on the input information, and the first network element can send a reply message carrying at least a partial context and / or at least a partial policy of the terminal to each of one or more nodes. In this way, the first network element can more flexibly allocate at least a partial context and / or at least a partial policy of the terminal to each node. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0027] FIG5 is a schematic diagram of a scenario of the training process of a large model according to an embodiment of the present application.

[0028] FIG6 is a schematic diagram of a processing scenario of a large model node according to an embodiment of the present application.

[0029] FIG7 is a schematic diagram of a system structure including a large model node according to an embodiment of the present application.

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

[0031] FIG9 is a schematic diagram of another system composition structure including a large model node according to an embodiment of the present application.

[0032] FIG10 is a schematic block diagram of a first network element according to an embodiment of the present application.

[0033] FIG11 is a schematic block diagram of a target node according to an embodiment of the present application.

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

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

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

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

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

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

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

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

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

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

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

[0045] In the current standard, the network elements in the 5G system interact to generate (and / or use) corresponding contexts, policies, etc. The relevant 5G processes include at least the following parts: registration process, registration update process, PDU session establishment process, PDU session modification process, UE configuration update (UCU, UE Update Configuration) process, service request process, paging process, etc. In the above process, the UE context and policy generated and / or used interactively between the network elements in the 5G system include but are not limited to at least one of the following: UE context parameters (sets) in AMF, UE context parameters (sets) in SMF, and UE policies (Policies); wherein, the parameters included in the UE context parameters (sets) in the AMF include but are not limited to at least one of the following: access frequency parameter set, paging cycle configuration parameter set, mobility restriction parameter set, location parameter set, access management policy association parameter set, network slice configuration parameter set, and configuration parameter set for each PDU session; the UE context parameters (sets) in the SMF include but are not limited to at least one of the following: PDU session attribute parameter set (S-NSSAI (Single Network Slice Selection Assistance information), DNN (Data Network Name), SSC (Session and Service Continuity) Mode, etc.), application server interaction parameter set (IP address, DNAI (DN Access Identifier, Data Network Access Identifier), etc.), description of each data flow in accordance with the binding relationship parameter set, quality of service of each data flow (Quality of Service, QoS) parameter set; the UE policy includes but is not limited to at least one of the following: URSP (UE Route Selection Policy, UE routing policy) rule list (TD+RSD (Route Selection Descriptor)), ANDSP (Access Network Discovery and Selection Policy, access network service discovery and selection policy) rule list (WLANSP (WLAN Selection Policy, WLAN selection policy) etc.), ATSSS (Access Traffic Steering, Switching, Splitting, access traffic steering, conversion, splitting) policy rule list.

[0046] The current 3GPP 5G system is based on the SBA (Service Based Architecture) bus architecture, which is implemented based on the SBI (Service Based Interface) interface (23501). However, each interaction process still needs to be defined (23502). This creates a huge protocol workload, and different interactions are still limited by artificial process constraints, making it impossible for each node to truly achieve flexible interaction. For example, in the processes related to negotiating and generating terminal context and policies, messages sent by the RAN must pass through the AMF to the SMF, and messages sent by the PCF must pass through the SMF to the UPF. The essential purpose of establishing these processes is to negotiate and generate terminal context and policies, but this process requires the coordination and interaction of each node, making it impossible for each node to truly achieve flexible interaction. In addition, each node involved in these processes has limitations, such as being limited by the parameters it can obtain. As a result, the terminal context and policy generated for each node may not be the most suitable or optimal.

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

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

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

[0050] S310. The first network element generates a first portion of parameters corresponding to the terminal based on input information, wherein the first portion of parameters corresponding to the terminal includes at least one of the following: a first portion of context parameters of the terminal and a first portion of policies of the terminal;

[0051] S320. The first network element sends a reply message to one or more nodes, where the reply message carries at least part of the first portion of parameters corresponding to the terminal. The one or more nodes include at least one of the following: the terminal, an access network device corresponding to the terminal, or one or more core network elements. The at least part of the first portion of parameters corresponding to the terminal may include at least one of the following: a first portion of context parameters for the terminal and a first portion of policies for the terminal.

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

[0053] S410. The target node receives a reply message sent by the first network element, wherein the reply message carries at least part of the content of the first part of parameters corresponding to the terminal, and the first part of parameters corresponding to the terminal include at least one of the following: the first part of context parameters of the terminal and the first part of policy of the terminal.

[0054] Here, the first network element may have computing and / or processing capabilities, and the first network element may transmit information with each of the one or more nodes.

[0055] The terminal may be a 3GPP terminal, that is, a terminal that can access a 3GPP network to send and receive data. For example, the terminal may be a mobile phone, a watch, a tablet, etc. This embodiment does not enumerate or limit various possible types of terminals.

[0056] The access network device corresponding to the terminal is the access network device serving the terminal.

[0057] The one or more core network elements may include at least one of the following: one or more core network control plane elements, and one or more core network user plane elements. The one or more core network control plane elements may include at least one of the following: a network element responsible for access and / or mobility management, and a network element responsible for session management. It should be noted that in this embodiment, each network element may alternatively be referred to as a node. For example, a core network control plane element may alternatively be referred to as a core network control plane node, which will not be repeated below.

[0058] In some possible examples, the 3GPP system adopts the division of network elements in the 5G architecture. In such examples, the network element responsible for access and / or mobility management may include an AMF; the network element responsible for session management may include an SMF. The one or more core network user plane network elements may include one or more UPFs.

[0059] It should be understood that, in addition to including at least one of the network elements responsible for access and / or mobility management and the network elements responsible for session management, one or more core network control plane network elements may also include at least one of the following: PCF, UDM, UDR, AF, OAM (Operations, Administration and Maintenance), etc. The network elements that may be included in the core network control plane network elements are not limited or enumerated here.

[0060] In some possible examples, the 3GPP system does not follow the division of network elements in the 5G architecture. In such examples, the one or more core network elements can be divided on demand. This example does not limit or exhaustively list the specific division of core network elements, the names of the divided core network elements, or the types of the elements.

[0061] In some possible implementations, the input information may include a request message.

[0062] Before the first network element generates the first part of parameters corresponding to the terminal based on the input information, it also includes: the first network element receives a request message sent by the target node, wherein the target node is one of the following: the terminal, the second network element, and the second network element is one of the one or more core network elements.

[0063] Correspondingly, before the target node receives the reply message sent by the first network element, it also includes: the target node sends a request message to the first network element, wherein the request message is used by the first network element to generate a first part of parameters corresponding to the terminal.

[0064] In one embodiment, the target node is a terminal, and the processing before the terminal receives the reply message sent by the first network element may include: the terminal sending a request message to the first network element. The first network element receiving the request message sent by the target node may include: the first network element receiving the request message sent by the terminal.

[0065] The request message may be a Non-Access Stratum (NAS) message. Exemplarily, the request message may be a request message included in at least one of the following processes: a registration process, a registration update process, a PDU session establishment process, or a PDU session modification process; specifically, the request message may be at least one of the following: a registration request message, a registration update message, a PDU session establishment request message, or a PDU session modification request message.

[0066] Optionally, when the first network element supports the NAS protocol, the terminal sending a request message to the first network element can be: the terminal sending the request message to the first network element through the access network device; correspondingly, the first network element receiving the request message sent by the terminal means that the first network element receives the request message sent by the terminal through the access network device.

[0067] Optionally, when the first network element does not support the NAS protocol, the terminal sending the request message to the first network element may be: the terminal sending the request message to a third network element through an access network device, and the third network element sending (or forwarding) the request message to the first network element; correspondingly, the first network element receiving the request message sent by the terminal means that the first network element receives the request message sent by the terminal through a third network element, and the third network element receives the request message sent by the terminal through the access network device. The third network element is a core network control plane network element that supports the NAS protocol, such as an AMF, etc.

[0068] In one embodiment, the target node is a second network element, and the processing before the second network element receives the reply message sent by the first network element may include: the second network element sends a request message to the first network element. The first network element receiving the request message sent by the target node may include: the first network element receiving the request message sent by the second network element.

[0069] The request message may be sent (or triggered or generated) in at least one of the following processes: a registration process, a registration update process, a PDU session establishment process, and a PDU session modification process.

[0070] The second network element and the third network element may be the same or different, and are not limited here.

[0071] The request message may carry at least one of the following: an identifier of the terminal, scenario information, and user preference information.

[0072] The identification of the terminal may include but is not limited to at least one of the following: the terminal's SUPI (Subscription Permanent Identifier), the terminal's SUCI (Subscription Concealed Identifier), the terminal's PEI (Permanent Equipment Identifier), the terminal's 5G-GUTI (5G Globally Unique Temporary Identifier), the terminal's Internal-Group Identifier (IGI), the terminal's GPSI (Generic Public Subscription Identifier), etc.

[0073] The context information may be used to indicate at least one of the following context types: connection, calculation, data, model, etc. The context information may also be alternatively referred to as context requirements.

[0074] The user preference information may be preference-related information set by the user of the terminal according to actual needs. The user preference information may also be alternatively referred to as user preference settings, or preference information of the user of the terminal, or preference settings of the user of the terminal, or preferred settings of the user of the terminal, etc. Exemplarily, the user preference information may be preferences and / or parameter values ​​related to the first part of parameters corresponding to the terminal set by the user of the terminal. For example, the user preference information may be specific parameter types and / or specific parameter names and / or parameter values ​​contained in the first part of parameters corresponding to the terminal set by the user of the terminal. For another example, the user preference information may be other parameters and / or other parameter values ​​and / or other information set by the user of the terminal that need to be obtained or used when generating the first part of parameters corresponding to the terminal, etc. It should be understood that the above is only an exemplary description of the user preference information, and this embodiment does not limit or exhaustively list the content, setting method, etc. that the user preference information may contain.

[0075] In some possible implementations, the input information may include static or global information. The static or global information may include at least one of the following: the terminal's subscription information, the terminal's PCC (Policy and Charging Control) rule, the network status information, the scenario information, and the user preference information. In other words, the input information may include at least one of the following: the terminal's subscription information, the terminal's Policy and Charging Control (PCC) rule, the network status information, the scenario information, and the user preference information.

[0076] This static or global information may also be referred to as static information, global information, or default information, etc. All possible names for static or global information are not limited or exhaustive here. For the sake of brevity, the following description may use static or global information. Specifically, the static or global information referred to below includes at least one of the terminal's subscription information, the terminal's policy and charging control (PCC) rules, network status information, scenario information, and user preference information. This explanation will not be repeated below.

[0077] Before the first network element generates the first part of parameters corresponding to the terminal based on the input information, it is necessary to obtain static or global information from at least some of the one or more core network elements. Specifically, before the first network element generates the first part of parameters corresponding to the terminal based on the input information, the first network element further includes: obtaining at least one of the following from at least some of the one or more core network elements: subscription information of the terminal, PCC rules of the terminal, the network status information, the scenario information, and the user preference information.

[0078] Optionally, the first network element may obtain static or global information from at least some of the one or more core network elements when receiving a request message sent by the target node.

[0079] Optionally, the first network element may obtain static or global information from at least some of the one or more core network elements when the request message sent by the target node is not received and the first part of the parameters corresponding to the terminal needs to be generated, triggered or determined according to other configurations. Here, the other configurations can be set according to actual conditions and are not limited in this embodiment.

[0080] The parameters and / or content that may be included in the contract information of the terminal may be the same as those specified in the relevant protocol, and this embodiment does not limit this; the parameters and / or content that may be included in the PCC rules of the terminal may be the same as those specified in the relevant protocol, and this embodiment does not limit this.

[0081] The network status information may include at least one of the following: usage of computing resources on the network side, usage of storage resources on the network side, usage of communication resources on the network side, transmission rate on the network side, percentage of the maximum upper limit rate on the network side, network congestion, etc. The network side may refer to at least one of the following: the entire network side, the core network side, any one or more network elements in the network side, etc.

[0082] At least one of the terminal's subscription information, the terminal's PCC rule, the network status information, the scenario information, and the user preference information may be stored in at least some of the one or more core network elements.

[0083] In one embodiment, the 3GPP system follows the division of network elements in the 5G architecture, and at least some of the one or more core network elements may include at least one of the following: UDM, UDR, PCF, OAM, etc.

[0084] At least one of the terminal's contract information, the terminal's PCC rules, the network status information, the scenario information, and the user preference information may be stored in at least one of UDM, UDR, PCF, and OAM. For example, the terminal's contract information may be stored in UDM / UDR; the terminal's PCC rules may be stored in PCF; the network status information, scenario information, and user preference information may be stored in at least one of UDM, UDR, PCF, and OAM. Correspondingly, the first network element may obtain the terminal's contract information from UDM / UDR, obtain the terminal's PCC rules from PCF, and obtain at least one of the network status information, scenario information, and user preference information from at least one of UDM, UDR, PCF, and OAM.

[0085] It should be understood that the above is only an exemplary description of at least some core network network elements and their stored contents. In actual processing, the storage entities of the terminal's contract information, the terminal's PCC rules, the network status information, the scenario information, and the user preference information may include but are not limited to the above-mentioned storage methods. The way in which the first network element obtains at least one of the terminal's contract information, the terminal's PCC rules, the network status information, the scenario information, and the user preference information is not limited to the methods in the above-mentioned examples, but this embodiment does not limit or exhaustively list them.

[0086] In one embodiment, the 3GPP system does not follow the division of network elements in the 5G architecture. The one or more core network elements can be divided on demand. Each of the terminal's subscription information, the terminal's PCC rules, the network status information, the scenario information, and the user preference information can be stored in at least some of the one or more core network elements according to actual needs. This embodiment does not limit the content that may be stored in different core network elements in at least some of the core network elements. Similarly, the specific manner in which the first network element obtains at least one of the terminal's subscription information, the terminal's PCC rules, the network status information, the scenario information, and the user preference information from at least some of the one or more core network elements is not limited or exhaustive.

[0087] In some possible implementations, the first part of parameters corresponding to the terminal may refer to at least part of dynamic information or at least part of parameters at the terminal granularity.

[0088] It should be noted that the first part of the parameters corresponding to the terminal refers to at least part of the dynamic information or at least part of the parameters at the terminal granularity that the first network element needs to generate this time, or that the first network element generates or obtains after performing processing. Specifically, the at least part of the dynamic information or at least part of the parameters at the terminal granularity may refer to: at least part of the information or at least part of the parameters generated by the first network element for the terminal each time the terminal accesses the network (such as registration), or the terminal initiates network connection establishment (such as initiating session establishment), or a condition changes (such as a terminal location update); when the first network element dynamically generates this at least part of the information or at least part of the parameters for the terminal, it is related to the terminal's location, the real-time status of the network, user preferences, terminal capabilities, services executed by the terminal, etc. Therefore, even if the static or global information is the same, the parameters and / or parameter values ​​generated by the first network element at different times when generating the at least part of the dynamic information or at least part of the parameters at the terminal granularity may be different.

[0089] The first part of the context parameters of the terminal may include at least one of the following: at least part of the context parameters of the terminal used by each core network element in at least part of the one or more core network elements, at least part of the context parameters used by the terminal, and at least part of the context parameters of the terminal used by the access network device.

[0090] The first partial policy of the terminal may include at least a partial policy of the terminal.

[0091] In one embodiment, the first part of parameters corresponding to the terminal may be all parameters corresponding to the terminal. In this embodiment, the input information may not include the second part of parameters corresponding to the terminal.

[0092] Specifically, the first part of the context parameters of the terminal may include at least one of the following: all context parameters of the terminal used by each core network element in at least some of the one or more core network elements, all context parameters used by the terminal, and all context parameters of the terminal used by an access network device. Here, the access network device is an access network device corresponding to the terminal.

[0093] The first part of the terminal policy may include all policies corresponding to the terminal specified in the relevant protocol, wherein the policy includes at least one of the following: UE policy, packet detection rule (PDR) policy, and data flow binding policy.

[0094] In one embodiment, the first partial parameters corresponding to the terminal may be partial parameters corresponding to the terminal. In this embodiment, the input information may include a second partial parameter corresponding to the terminal, wherein the second partial parameter corresponding to the terminal is at least partially different from the first partial parameter corresponding to the terminal.

[0095] The second part of parameters corresponding to the terminal may refer to dynamically generated information or parameters at the terminal granularity. It should be noted that the second part of parameters corresponding to the terminal refers to the information or parameters dynamically generated at the terminal granularity on the network side (such as one or more network elements on the network side other than the first network element) in the current process. Specifically, the dynamically generated information or parameters at the terminal granularity may refer to: each time the terminal accesses the network (such as registration), or the terminal initiates a network connection establishment (such as initiating a session establishment), or a condition changes (such as a terminal location update) The network side (such as one or more network elements on the network side other than the first network element) generates or updates the information or parameters for the terminal; when the network side (such as one or more network elements on the network side other than the first network element) dynamically generates or updates this part of information or parameters for the terminal, it is related to the location of the terminal, the real-time status of the network, user preferences, terminal capabilities, the services executed by the terminal, etc. Therefore, even if the static or global information is the same, when the network side (such as one or more network elements other than the first network element) generates or updates dynamic information or parameters at the terminal granularity at different times, the parameters and / or parameter values ​​may be different.

[0096] That is, among all the parameters corresponding to the terminal, some are parameters that have been generated or configured by one or more network elements other than the first network element on the network side, and these parameters are the second part of the parameters corresponding to the terminal; and among all the parameters corresponding to the terminal, at least some are parameters that are currently generated by the first network element, and these parameters are the first part of the parameters corresponding to the terminal. The second part of the parameters corresponding to the terminal is used as input information for the first network element, so that the first network element outputs the first part of the parameters corresponding to the terminal.

[0097] Optionally, the second part of parameters corresponding to the terminal may be completely different from the first part of parameters corresponding to the terminal.

[0098] Optionally, the second part of the parameters corresponding to the terminal may be partially identical (or partially overlapped) with the first part of the parameters corresponding to the terminal. For example, the second part of the parameters corresponding to the terminal may contain one or more parameter names that are identical to the first part of the parameters corresponding to the terminal, and the parameter values ​​corresponding to the same parameter names in the first and second part of the parameters corresponding to the terminal may be the same or different. In this case, after the first network element generates the first part of the parameters corresponding to the terminal, it uses the first part of the parameters corresponding to the terminal to cover or at least partially cover the second part of the parameters corresponding to the terminal; for example, the parameter values ​​corresponding to the same parameter names in the second part of the parameters corresponding to the terminal as those in the first part of the parameters can be replaced with the parameter values ​​in the first part of the parameters. Accordingly, after the first network element sends the first part of the parameters corresponding to the terminal to one or more nodes respectively, if one or more parameters generated locally by any node are identical to one or more parameter names in the first part of the parameters corresponding to the terminal, the node will also use the parameter values ​​corresponding to the same parameter names in the first part of the parameters corresponding to the terminal to cover or replace the parameter values ​​corresponding to the local parameter names.

[0099] For example, assuming that the second part of the parameters corresponding to the terminal include parameter 1 (the value of parameter a is a1) and parameter 2 (the value of parameter 2 is a2), and the first part of the parameters corresponding to the terminal generated by the first network element includes parameter 1 (the value of parameter a is b1), parameter 3 (the value of parameter 3 is b3), and parameter 4 (the value of parameter 4 is b4). It can be seen that the two parts of the parameters have the same parameter 1, and the value of parameter 1 in the first part of the parameters is different from the value of parameter 1 in the second part of the parameters. In this case, the value of parameter 1 in the second part of the parameters is replaced with the value b1 of parameter 1 in the first part of the parameters.

[0100] Specifically, the first part of the context parameters of the terminal may include at least one of the following: partial context parameters of the terminal used by each core network element in at least some of the one or more core network elements, partial context parameters used by the terminal, and partial context parameters of the terminal used by the access network device.

[0101] The first partial policy of the terminal may include a partial policy of the terminal.

[0102] The second portion of parameters corresponding to the terminal may include at least one of the following: a second portion of context parameters of the terminal and a second portion of policies of the terminal, wherein the second portion of context parameters of the terminal is at least partially different from the first portion of context parameters of the terminal, and the second portion of policies of the terminal is at least partially different from the first portion of policies of the terminal.

[0103] Specifically, the second part of the context parameters of the terminal may include at least one of the following: the context parameters that have been generated or configured in all the context parameters of the terminal used by each core network element in at least part of the one or more core network elements, the context parameters that have been generated or configured in all the context parameters of the terminal, and the context parameters that have been generated or configured in all the context parameters of the terminal used by the access network device.

[0104] The second part of the terminal's policies may include generated or configured policies among all policies corresponding to the terminal.

[0105] Before the first network element generates the first part of parameters corresponding to the terminal based on the input information, it also includes: the first network element obtains the second part of parameters corresponding to the terminal from at least some of the one or more core network elements.

[0106] The first network element obtains the second part of parameters corresponding to the terminal from at least some of the one or more core network elements, which may refer to: the first network element obtains the partial parameters corresponding to the terminal generated by each of at least some of the one or more core network elements; and uses the partial parameters corresponding to the terminal generated by each of at least some of the core network elements as the second part of parameters corresponding to the terminal. It should be noted that the partial parameters corresponding to the terminal generated or configured by different core network elements in at least some of the core network elements may be different. The partial parameters corresponding to the terminal generated or configured by each core network element may include at least some of the parameters in the second part of the context parameters of the terminal and / or at least some of the policies in the second part of the policy of the terminal.

[0107] For example, at least some of the one or more core network elements may include an AMF and an SMF, and the AMF has generated or configured one or more context parameters for the terminal, and the SMF has generated or configured one or more context parameters for the terminal. The first network element may obtain from the AMF the one or more context parameters for the terminal that the AMF has generated or configured, and the first network element may obtain from the SMF the one or more context parameters for the terminal that the SMF has generated or configured; the first network element uses the one or more context parameters for the terminal that the AMF has generated or configured and the one or more context parameters for the terminal that the SMF has generated or configured as the second part of parameters corresponding to the terminal.

[0108] Optionally, when the first network element receives a request message sent by the target node, the first network element obtains the second part of parameters corresponding to the terminal from at least some of the one or more core network elements.

[0109] If the target node is a second network element, the second network element can be one of at least some of the one or more core network elements, and the content carried by the request message sent by the second network element is the same as the above-mentioned embodiment, then the processing of the first network element obtaining the second part of the parameters corresponding to the terminal from at least some of the one or more core network elements is the same as the above-mentioned embodiment and will not be repeated.

[0110] If the target node is a second network element, and the second network element may be one of at least some of the one or more core network elements, the request message sent by the second network element may also carry some parameters corresponding to the terminal that have been generated or configured by the second network element. The some parameters corresponding to the terminal that have been generated or configured by the second network element may include: one or more context parameters of the terminal that have been generated or configured by the second network element, and / or one or more policies of the terminal that have been generated or configured by the second network element. In this case, the first network element may obtain the second partial parameters corresponding to the terminal from at least some of the one or more core network elements, which may be: the first network element may obtain the partial parameters corresponding to the terminal that have been generated by the core network element from each of at least some of the one or more core network elements other than the second network element; and use the partial parameters corresponding to the terminal that have been generated by the second network element and the partial parameters corresponding to the terminal that have been generated by each of at least some of the core network elements as the second partial parameters corresponding to the terminal.

[0111] Optionally, the first network element may obtain the second part of parameters corresponding to the terminal from at least some of the one or more core network elements when the request message sent by the target node is not received and the need to generate the first part of parameters corresponding to the terminal is triggered or determined according to other configurations.

[0112] In summary of the above embodiments, the input information may include at least one of the following: a request message, static or global information, and the second part of parameters corresponding to the terminal. The following is an exemplary description of the possible contents of the input information:

[0113] In one embodiment, the input information may only include a request message.

[0114] Optionally, the input information may include all of the content carried by the request message. For example, if the request message carries the terminal's identifier and scenario information, the input information may include the terminal's identifier and scenario information carried by the request message. For another example, if the request message carries the terminal's identifier, scenario information, and user preference information, the input information may include the terminal's identifier, scenario information, and user preference information carried by the request message. This is not intended to limit or exhaustively list all possible scenarios.

[0115] Optionally, the input information may include part of the content carried by the request message. For example, if the request message carries the terminal's identifier and scenario information, the input information may include the terminal's identifier or scenario information carried by the request message. For another example, if the request message carries the terminal's identifier, scenario information, and user preference information, the input information may include at least one of the terminal's identifier, scenario information, and user preference information carried by the request message. This is not intended to limit or exhaustively list all possible scenarios.

[0116] In one embodiment, the input information may include only static or global information. In this embodiment, regardless of whether the first network element receives a request message sent by the target node, the process of the first network element generating the input information may include: the first network element adding at least one of the following obtained from at least some of the one or more core network elements to the input information: the terminal's subscription information, the terminal's PCC rules, the network status information, the scenario information, and the user preference information.

[0117] In one embodiment, the input information includes a request message, static or global class information.

[0118] Optionally, the request message may only carry the identifier of the terminal. The process of the first network element generating the input information may include: the first network element may add the identifier of the terminal, static or global information to the input information.

[0119] Optionally, the request message may carry scenario information and / or user preference information in addition to the terminal identifier.

[0120] Static or global information may not include scenario information and / or user preference information, that is, the first network element does not need to obtain scenario information and / or user preference information from other network elements, and only needs to obtain at least one of the following from at least some of the one or more core network elements: the subscription information of the terminal, the PCC rules of the terminal, and the network status information. The process of the first network element generating input information may include: the first network element adding the identifier of the terminal carried in the request message to the input information, the first network element adding the scenario information and / or user preference information carried in the request message to the input information, and the first network element adding at least one of the following obtained from at least some of the one or more core network elements to the input information: the subscription information of the terminal, the PCC rules of the terminal, and the network status information.

[0121] Alternatively, the first network element does not use the scenario information and / or user preference information carried in the request message, and only uses the terminal identifier carried in the request message. Further, the process of the first network element generating the input information may include: the first network element adding the terminal identifier carried in the request message to the input information, and the first network element adding at least one of the following obtained from at least some of the one or more core network elements to the input information: the terminal's subscription information, the terminal's PCC rules, the network status information, the scenario information, and the user preference information.

[0122] In one embodiment, the input information may include only the second part of parameters corresponding to the terminal. In this embodiment, the process of the first network element generating the input information may include: the first network element obtaining the second part of parameters corresponding to the terminal from at least some of the one or more core network elements and adding it to the input information.

[0123] In one embodiment, the input information includes static or global class information and a second portion of parameters corresponding to the terminal. In this embodiment, the process of the first network element generating the input information may include: the first network element may add the static or global class information and the second portion of parameters corresponding to the terminal to the input information.

[0124] In one embodiment, the input information includes a request message and a second portion of parameters corresponding to the terminal. In this embodiment, the first network element generating the input information may include: the first network element adding the content carried in the request message and the second portion of parameters corresponding to the terminal obtained from at least some of the one or more core network elements to the input information.

[0125] In one embodiment, the input information includes a request message, static or global class information, and a second part of parameters corresponding to the terminal.

[0126] Optionally, the request message may only carry the terminal identifier. The process of the first network element generating the input information may include: the first network element may add the terminal identifier, static or global class information and the second part of parameters corresponding to the terminal to the input information.

[0127] Optionally, the request message may carry scenario information and / or user preference information in addition to the terminal identifier.

[0128] Static or global information may not include scenario information and / or user preference information. The process of the first network element generating input information may include: the first network element adding the identifier of the terminal carried in the request message to the input information, the first network element adding the scenario information and / or user preference information carried in the request message to the input information, the first network element adding the second part of parameters corresponding to the terminal to the input information, and the first network element adding at least one of the following obtained from at least some of the one or more core network network elements to the input information: the subscription information of the terminal, the PCC rule of the terminal, and the network status information.

[0129] Alternatively, the first network element does not use the scenario information and / or user preference information carried in the request message, and only uses the terminal identifier carried in the request message. Further, the first network element may generate the input information by adding the terminal identifier, static or global class information, and the second part of parameters corresponding to the terminal to the input information.

[0130] In some possible implementations, the first network element generating the first part of parameters corresponding to the terminal based on the input information may include: the first network element generating the first part of parameters corresponding to the terminal based on the input information and local configuration.

[0131] The local configuration may be information or configuration pre-configured or pre-stored locally on the first network element. Preferably, the local configuration may include a large model, wherein the large model may include or be composed of one or more algorithms; that is, the first network element may be a network element in which the large model is deployed. In some possible examples, the first network element may be called an intelligent node or a large model node.

[0132] The first network element generates the first part of parameters corresponding to the terminal based on the input information and the local configuration, which may mean that the first network element inputs the input information into the large model in the local configuration, and obtains the first part of parameters corresponding to the terminal output by the large model. It should be understood that the large model can also be called any one of an artificial intelligence (AI) large model, an AI model, a model, etc., and all possible names of the large model are not limited or exhaustive here. As long as the input of the large model can include input information and the output includes the first part of parameters corresponding to the terminal, it is within the protection scope of this embodiment.

[0133] It should also be understood that, in addition to the above-mentioned large model, the local configuration may also include at least one of other information, other parameters, other algorithms, etc. that are pre-configured or pre-saved locally by the first network element. However, in this embodiment, the other information, other parameters, and other algorithms that are pre-configured or pre-saved by the first network element are not limited or enumerated.

[0134] Relevant explanation of the training of the above-mentioned large model: Similar to the current large model used to train text data, there is a correlation between the parameters in the context and / or strategy of the terminal in the 3GPP system, which can construct a word vector relationship diagram to generate the context and / or strategy of the terminal in different scenarios. Therefore, the context and / or strategy generated by each terminal under the existing mechanism can be combined with the corresponding scenario information, contract information and other data as training text. The large model is trained through a large amount of training text to achieve generalization model learning, and realize true full-scenario on-demand use of the large model to generate part or all of the terminal's context / part or all of the terminal's strategy for different nodes of the 3GPP system.

[0135] Scenarios in which the context and / or policies of the terminal are generated based on the big model and the 3GPP system is globally configured include the following possibilities: in short-term scenarios, the big model can be used to generate individual context parameters of the terminal and / or individual policies of the terminal, such as the parameters currently pre-configured by 3GPP or that need to be completed; in medium-term scenarios, the big model can generate all context parameters of the terminal and / or all policies of the terminal; in long-term scenarios, new (or new types of) context parameters and / or policies can be created, set or defined, thereby redefining functions such as MM (Mobility Management) / CM (Connection Management) / SM (Session Management), and changing the network elements and topology of the 3GPP system.

[0136] In conjunction with Figure 5, an exemplary description of the training process of the large model is given. The training text of the large model may include: scenario requirements (i.e., scenario information in the aforementioned embodiment), the contract information of the terminal, and the context parameters of the terminal. In the training process of the example on the left side of Figure 5, the scenario requirements, the contract information of the terminal, and some context parameters of the terminal in the training text can be used as input information for a training, including at least one of: S-NSSAI, DNN, Session type, etc.; the "masked" on the left side of Figure 5 is the parameter masked or removed from the context parameters of the terminal during training, and the "SSC mode" on the left side of Figure 5 is the prediction result of the large model. The "SSC mode" output by the prediction result of the large model and whether it is the same as the parameter "SSC mode" masked or removed in the training text are used as training targets to train the large model. In the training process of the example on the right side of Figure 5, the scenario requirements in the training text, the contract information of the terminal, and some context parameters of the terminal can be used as input information for one training, including: S-NSSAI, DNN (DNN = Internet), Session type, URSP (including DNN = IMS); the training goal shown on the right side of Figure 5 is to train the large model to be able to recognize whether DNN = Internet is the same as URSP (DNN = IMS). If the output result is "no" as shown on the right side of Figure 5, it means that the large model training is successful.

[0137] In conjunction with Figure 6, the relevant processing of the large model is exemplified. In the scenario illustrated in Figure 6, the large model node (i.e., the first network element) obtains static or global class information from the core network control plane network element (such as at least one of the UDM, PCF, OAM network management, etc.), and / or obtains the second part of parameters corresponding to the terminal from the core network control plane network element (such as at least one of the AMF, SMF, AF, etc.); the large model node can use the static or global class information and / or the second part of parameters corresponding to the terminal as input information to obtain the first part of parameters corresponding to the terminal.

[0138] It should be understood that the above is only an illustrative explanation using the example of input information including static or global class information and / or the second part parameters corresponding to the terminal. In actual processing, the content that the input information may contain is the same as the aforementioned embodiment, for example, it may also include a registration request message from the terminal, etc., which will not be repeated here.

[0139] In some possible implementations, the first network element sending a reply message to one or more nodes may refer to: the first network element sending a reply message corresponding to each of the one or more nodes. The reply message corresponding to each node may carry at least one of the following: at least a portion of the context parameters of the terminal used by the node in the first portion of the context parameters of the terminal, and at least a portion of the terminal policy corresponding to the node in the first portion of the terminal policy.

[0140] The one or more nodes include at least one of the following: the terminal, an access network device corresponding to the terminal, or one or more core network elements. After receiving a corresponding reply message, each of the one or more nodes may perform corresponding functions and behaviors based on at least a portion of the received terminal context parameters and / or at least a portion of the terminal's policies. This embodiment does not limit the subsequent behaviors or functions of each node.

[0141] In one embodiment, the reply message corresponding to the terminal carries at least one of the following: at least part of the context parameters used by the terminal in the first part of the context parameters of the terminal, and at least part of the policy of the terminal in the first part of the policy of the terminal.

[0142] If the first network element supports the NAS protocol, the first network element can directly send a reply message corresponding to the terminal to the terminal; if the first network element does not support the NAS protocol, the first network element can send a reply message to the terminal via a third network element. The relevant description of the third network element is the same as that of the previous embodiment and is not repeated here.

[0143] Optionally, the reply message corresponding to the terminal may further carry a token of the terminal, where the token of the terminal is used to identify the terminal and / or verify the terminal when the terminal executes a related process.

[0144] Specifically, the token of the terminal may be the content that the terminal needs to carry when sending at least one message in other processes. By carrying the token of the terminal in at least one message sent in the other process, the network element involved in the other process (such as any core network element) can identify or verify that the terminal is a terminal that has context parameters and / or UE policies assigned to the first network element, and then the locally stored context parameters and / or UE policies of the terminal can be extracted to perform subsequent processing. The other process may be any process specified in the relevant protocol that requires the use of the context parameters and / or UE policies of the terminal, for example, it may include at least one of the following: service request process, location update process, paging process. This embodiment does not limit or enumerate other processes.

[0145] Optionally, if the terminal is the target node, the terminal sends a request message to the first network element, and the request message may be at least one of the following: a registration request message, a registration update message, a PDU session establishment request message, or a PDU session modification request message; then the corresponding reply message of the terminal may be at least one of the following: a registration reply message, a registration update reply message, a PDU session establishment reply message, or a PDU session modification reply message, and the reply message may also carry at least one of the following: a registration result, a PDU session establishment / modification result, and the like.

[0146] In one embodiment, the reply message corresponding to the access network device corresponding to the terminal carries at least one of the following: at least part of the context parameters of the terminal used by the access network device in the first part of the context parameters of the terminal, and at least part of the policy of the terminal in the first part of the policy of the terminal.

[0147] In one embodiment, the reply message corresponding to each core network device in the one or more core network devices carries at least one of the following: at least part of the context parameters of the terminal used by the core network device in the first part of the context parameters of the terminal, at least part of the policy of the terminal in the first part of the policy of the terminal, and the first part parameters corresponding to the terminal.

[0148] An exemplary description is given of a reply message corresponding to each of the one or more core network devices:

[0149] In one example, assuming that the 3GPP system continues to use the division of network elements in the 5G architecture, one or more core network devices may include: AMF, SMF, PCF, UDM, UDR, AF, UPF, and OAM.

[0150] In this example, the reply message corresponding to AMF can carry at least part of the context parameters of the terminal used by AMF in the first part of the context parameters of the terminal; the reply message corresponding to SMF can carry at least part of the context parameters of the terminal used by SMF in the first part of the context parameters of the terminal; the reply message corresponding to UPF can carry at least part of the context parameters of the terminal used by UPF in the first part of the context parameters of the terminal; the reply message corresponding to AF can carry at least part of the context parameters of the terminal used by AF in the first part of the context parameters of the terminal; the reply message corresponding to PCF can carry at least part of the policy of the terminal in the first part of the policy of the terminal; the reply message corresponding to at least one of UDM, UDR, PCF, and OAM can carry the first part parameters corresponding to the terminal (that is, the first part of the context parameters of the terminal and / or the specific content of the first part of the policy of the terminal).

[0151] Here, the reply message corresponding to at least one of the UDM, UDR, PCF, and OAM may also carry at least one of the following: whether the first network element has received a registration request from the terminal, for which node or nodes at least some of the corresponding terminal context parameters and / or at least some of the terminal's policies (i.e., the relevant number or identifier of each of one or more nodes) are generated. Subsequent processing of the reply message received by at least one of the UDM, UDR, PCF, and OAM may include saving the first part of parameters corresponding to the terminal; further, the saving of the first part of parameters corresponding to the terminal by at least one of the UDM, UDR, PCF, and OAM may be used for other related processes, and other related processes are not limited here.

[0152] It should be noted that if one or more core network devices do not include UPF, after the SMF receives at least part of the context parameters of the terminal used by the SMF in the first part of the context parameters of the terminal, the processing of the SMF may also include: generating at least part of the context parameters of the terminal used by the UPF based on at least part of the context parameters of the terminal used by the SMF, and the SMF sends at least part of the context parameters of the terminal used by the UPF to the UPF.

[0153] In one example, assuming that the 3GPP system does not follow the division of network elements in the 5G architecture, one or more core network devices can be divided on demand.

[0154] The reply message corresponding to each core network device in the one or more core network devices may carry at least one of the following: at least part of the context parameters of the terminal used by the core network device in the first part of the context parameters of the terminal, and at least part of the policy of the terminal in the first part of the policy of the terminal.

[0155] Among them, the types of at least some of the context parameters of the terminal used by different core network devices may be different. For example, the first part of the context parameters of the terminal are divided into three types, namely, the first type of at least some of the context parameters of the terminal, the second type of at least some of the context parameters of the terminal, and the third type of at least some of the context parameters of the terminal. Accordingly, the first network element can divide all the core network devices associated with itself into three core network devices as needed, wherein the reply message corresponding to core network device 1 can carry the first type of at least some of the context parameters of the terminal used by the core network device 1, the reply message corresponding to core network device 2 can carry the second type of at least some of the context parameters of the terminal used by the core network device 2, and the reply message corresponding to core network device 3 can carry the third type of at least some of the context parameters of the terminal used by the core network device 3.

[0156] In some embodiments, when the reply message corresponding to each core network device carries at least part of the context parameters of the terminal used by the core network device in the first part of the context parameters of the terminal and / or at least part of the policy of the terminal corresponding to the core network device in the first part of the policy of the terminal, the processing of the core network device may also include: the core network device supplements all the context parameters of the terminal used by the core network device and / or all the policies of the terminal.

[0157] The core network device's process of supplementing the complete context parameters of the terminal and / or the complete policies of the terminal used by the core network device may include at least one of the following: the core network device generates the remaining upper and lower parameters other than the partial context parameters of the terminal used by the core network device, and merges the partial context parameters of the terminal used by the core network device and the remaining upper and lower parameters to obtain the complete context parameters of the terminal used by the core network device; the core network device generates the remaining partial policies other than the partial policies of the terminal, and merges the partial policies of the terminal with the remaining partial policies to obtain the complete policies of the terminal. The core network device may use an existing mechanism to generate the remaining parameters other than the partial context parameters of the terminal used by the core network device, which is not limited herein; the core network device may use an existing mechanism to generate the remaining partial policies other than the partial policies of the terminal, which is not limited herein.

[0158] Optionally, the first network element may not send a reply message to the terminal, but after the core network device obtains all the context parameters of the terminal and / or all the policies of the terminal used by the core network device, the core network device sends all the context parameters used by the terminal and / or all the policies of the terminal to the terminal.

[0159] The message used by the core network device to send all context parameters used by the terminal and / or all policies of the terminal to the terminal may be a message specified in a related protocol and is not limited here.

[0160] For example, assuming that the core network device is an AMF, the first network element generates partial context parameters of the terminal used by the AMF, and sends the partial context parameters of the terminal used by the AMF in the first partial context parameters of the terminal through a reply message corresponding to the AMF. After the AMF generates the remaining partial context parameters, it merges the partial context parameters of the terminal used by the AMF with the remaining partial context parameters to obtain the full context parameters of the terminal used by the AMF; the AMF generates the full context parameters used by the terminal, and the AMF sends the full context parameters used by the terminal to the terminal.

[0161] Optionally, the first network element may not send a reply message to the access network device. Instead, after the core network device obtains all context parameters of the terminal and / or all policies of the terminal used by the core network device, the core network device sends all context parameters of the terminal used by the access network device and / or all policies of the terminal to the access network device. The message used by the core network device to send all context parameters of the terminal used by the access network device and / or all policies of the terminal to the access network device may be a message specified in a relevant protocol and is not limited here.

[0162] Optionally, the first network element may send a reply message to the terminal, the reply message carrying the partial context parameters used by the terminal in the first partial context parameters of the terminal and / or the partial policy of the terminal in the first partial policy of the terminal. And / or, the first network element may send a reply message to the access network device, the reply message carrying the partial context parameters of the terminal used by the access network device in the first partial context parameters of the terminal and / or the partial policy of the terminal corresponding to the access network device in the first partial policy of the terminal.

[0163] In this case, after obtaining all the context parameters of the terminal used by the core network device, the core network device may also send all the context parameters used by the terminal and / or all the policies of the terminal to the terminal, and / or send all the context parameters of the terminal used by the access network device and / or all the policies of the terminal to the access network device. Accordingly, the terminal may, upon receiving all the context parameters of the terminal and / or all the policies of the terminal, delete some of the context parameters used by the terminal and / or some of the policies of the terminal, and replace them with all the context parameters of the terminal and / or all the policies of the terminal; and / or the access network device may, upon receiving all the context parameters of the terminal used by itself and / or all the policies of the terminal, delete some of the context parameters of the terminal used by the access network device and / or some of the policies of the terminal, and replace them with all the context parameters of the terminal and / or all the policies of the terminal used by the access network device.

[0164] The first network element (or intelligent node, or large model node) involved in the aforementioned embodiment can have a "God's perspective" through the Overlay AI architecture shown in Figure 6, and directly interact with the nodes used, thereby generating the context parameters and / or terminal strategies that are most suitable for each node's terminal, thereby achieving the goal of system optimization.

[0165] The introduction of the first network element (also known as the intelligent node or large model node) will change the design of the existing architecture process, enabling intelligent replacement and optimization. Specific considerations include:

[0166] First, the service defined by the SBA mechanism in the 5G architecture can be used to connect to the large model node and support interaction with the large model. In this way, the SBI can be reused to define new functional services, and the existing process can still be used in the initial stage of adding the first network element on the core network side. For example, as shown in Figure 7, a "large model node" is added on the basis of the 5G architecture shown in Figure 2. There is a newly defined interface between the large model node and the core network elements (AMF, SMF, PCF, AUSF, UDM, AF, etc. as shown in Figure 7), and there is a newly defined interface between the large model node and the RAN and UE (i.e., terminal).

[0167] Second, the interaction between the terminal and the first network element uses the NAS protocol; for example, the terminal and the first network element can directly interact using the NAS protocol, or the AMF can serve as a forwarding node between the terminal and the first network element.

[0168] Third, the first network element can replace the terminal context and / or policy generated by various network elements in the 5G system architecture during different processes. For example, during the initial registration process and PDU session establishment process, the first network element no longer needs to interact with each other, but instead uniformly generates and configures the terminal context and / or policy.

[0169] Fourth, some 5G network elements such as NSSF and NSACF functions can be replaced by the first network element (such as determining allowed NSSAI, Configured NSSAI and other functions).

[0170] Fifth, 3GPP processes that do not involve the context and / or policy update (or generation) of the terminal are still executed using existing processes, such as location update, Service Request (service request), Paging (paging), etc.

[0171] Sixth, the behavior and function of each core network element is executed based on the context and / or policy of the terminal configured by the first network element, and the behavior and function of each core network element is still completed by each core network element itself.

[0172] In conjunction with FIG8 , taking the first network element as a large model node, the terminal as a UE, and the access network device as an AN as an example, an exemplary description of the communication method provided in an embodiment of the present application is given, specifically including:

[0173] Step 801: The registration request node (i.e., the target node in the aforementioned embodiment, UE in this example) sends a request message to the large model node. The request message is a NAS message, which can carry UE identification, scene content (i.e., scene information in the aforementioned embodiment), user preference settings (i.e., user preference information) and other information.

[0174] Step 802: The large model node interacts with some NFs (such as the core network control plane network elements (UDM, PCF, OAM network management) shown in Figure 7) to obtain at least one of the subscription information, PCC rules, network status information, etc.

[0175] Step 803: The large model node generates UE context parameters and / or UE policies for use by other nodes based on the UE's request message and at least one of the acquired subscription information, PCC policy, and network status information. Here, the number of the other nodes may be one or more, i.e., the one or more nodes in the aforementioned embodiment. The one or more nodes may include at least one of the following: UE, AN, SMF, UPF, SMF, PCF, OAM, etc.

[0176] It should be pointed out that the UE context parameters and / or UE policies used by other nodes may be the UE context parameters and / or UE policies used for a certain (or certain) node. For example, the UE context parameters may include: AM context, SM context; or, the UE context parameters and / or UE policies used by any other node may be part of the UE context parameters and / or part of the UE policies used by the node, and the remaining UE context parameters and / or the remaining UE policies may still be generated according to the existing mechanism or locally by the node.

[0177] Step 804: The large model node sends the UE context parameters and / or UE policies used by the AN to the AN.

[0178] Step 805: The large model node sends the UE context parameters and / or UE policies used by the core network control plane network elements such as AMF, SMF, AF, etc. to the corresponding nodes respectively.

[0179] Step 806: The large model node sends the processing results (such as whether the UE's registration request is received, for which nodes the UE's context parameters and / or UE's policies are generated, and the specific contents of the UE's context parameters and / or UE's policies) to at least one of the UDM, PCF, and OAM network management for storage.

[0180] The large model node can execute step 807a or 807b: Step 807a: If the large model node directly derives the UE context parameters and / or UE policies for the UPF, it is sent directly to the UPF; Step 807b: If other core network control plane network elements (SMF as shown in Figure 7) derive the UE context parameters and / or UE policies (or related configuration parameters) used by the core network user plane network elements (such as UPF) based on the obtained UE context parameters and / or UE policies, it is sent by the SMF to the UPF.

[0181] Step 808: The UE receives a NAS reply message, which may include the registration result, the UE token, context parameters and / or policies used by the UE (such as URSP policies). The reply message may be sent directly to the UE by the large model node via a NAS message. The UE token may be used for subsequent interactions with other core network elements (such as executing service request procedures and location update procedures).

[0182] It should be pointed out that the execution order of the above steps 804 to 808 can be arbitrary, that is, as long as the actual processing includes the relevant processing content in the above steps 804 to 808, it is within the protection scope of this embodiment and the execution order of steps 704 to 708 is not limited.

[0183] Each network element illustrated in FIG8 performs subsequent corresponding functions and behaviors according to the UE context parameters and / or UE policies configured by the large model node, which is not limited here.

[0184] In conjunction with Figure 9, taking the first network element as a large model node, the terminal as a UE, and the access network device as an AN as an example, another architecture applicable to the communication method provided in the embodiment of the present application is exemplified: in the scenario illustrated in Figure 9, the one or more core network nodes (or network elements) can be divided according to actual needs. When the 3GPP system provides not only communication (connection) services but also computing, data, and model-related services, more new context parameters need to be defined to describe the connection, computing, data, and model (QoAIS (Quality of AI Service, intelligent service quality) four elements) related functions that each node needs to provide. In this scenario, the node (or network element) division of the network designed based on the 5G architecture may no longer be applicable. The first network element (intelligent node or large model node) can freely allocate the context and / or policy corresponding to the four elements of QoAIS to each node (such as one or more core network control plane nodes (or network elements) and core network user plane nodes (or network elements) illustrated in 9) on demand. That is, the context and / or policy content contained in each node (or network element) can be flexibly allocated. At least one of the one or more core network control plane nodes (or network elements) illustrated in FIG8 can still interact with the AF, and the core network user plane node (or network element) can still interact with the DN; In addition, in the scenario illustrated in FIG9, the UE and the large model node can interact through NAS messages, and the UE and the RAN can interact through AS messages.

[0185] In the scenario illustrated in Figure 9, the process of allocating context parameters and / or policies of the UE is similar to the process in the example corresponding to Figure 7 above. The main difference is that the context allocated to the large model node includes the context corresponding to the four elements of QoAIS, and the core network control plane node and the core network user plane node are also divided as needed, so they are not repeated here.

[0186] By adopting the above solution, the first network element can generate at least a portion of the terminal's context and / or at least a portion of the policy based on the input information, and the first network element can send a reply message carrying at least a portion of the terminal's context and / or at least a portion of the policy to each of one or more nodes. In this way, the first network element can more flexibly allocate at least a portion of the terminal's context and / or at least a portion of the policy corresponding to each node. In addition, because the first network element can interact with multiple nodes to obtain relevant parameters, the relevant parameters that the first network element can obtain are no longer limited, thus ensuring that the terminal's context and policy that are more suitable for each node are ultimately generated.

[0187] FIG10 is a schematic diagram of the composition structure of a first network element according to an embodiment of the present application, including:

[0188] The first processing unit 1001 is configured to generate a first portion of parameters corresponding to a terminal based on input information, wherein the first portion of parameters corresponding to the terminal includes at least one of the following: a first portion of context parameters of the terminal and a first portion of policies of the terminal;

[0189] The first communication unit 1002 is used to send a reply message to one or more nodes, wherein the reply message carries at least part of the content of the first part of parameters corresponding to the terminal, and the one or more nodes include at least one of the following: the terminal, the access network device corresponding to the terminal, and one or more core network elements.

[0190] The input information includes a request message.

[0191] The first communication unit is used to receive a request message sent by a target node, wherein the target node is one of the following: the terminal, a second network element, and the second network element is one of the one or more core network elements.

[0192] The request message carries at least one of the following: identification of the terminal, scenario information, and user preference information.

[0193] The input information includes at least one of the following: subscription information of the terminal, policy and charging control (PCC) rules of the terminal, network status information, scenario information, and user preference information.

[0194] The first communication unit is used to obtain at least one of the following from at least some of the one or more core network elements: the subscription information of the terminal, the PCC rule of the terminal, the network status information, the scenario information, and the user preference information.

[0195] The input information includes: a second portion of parameters corresponding to the terminal, wherein the second portion of parameters corresponding to the terminal is at least partially different from the first portion of parameters corresponding to the terminal.

[0196] The first communication unit is used to obtain the second part of parameters corresponding to the terminal from at least some of the one or more core network elements.

[0197] The second part of parameters corresponding to the terminal includes at least one of the following: the second part of context parameters of the terminal and the second part of policies of the terminal.

[0198] The policy includes at least one of the following: UE policy, data packet detection rule PDR policy, and data flow binding policy.

[0199] The one or more core network network elements include at least one of the following: one or more core network control plane network elements, and one or more core network user plane network elements.

[0200] The one or more core network control plane network elements include at least one of the following: a network element responsible for access and / or mobility management, and a network element responsible for session management.

[0201] FIG11 is a schematic diagram of the structure of a target node according to an embodiment of the present application, including:

[0202] The second communication unit 1101 is used to receive a reply message sent by the first network element, wherein the reply message carries at least part of the content of the first part parameters corresponding to the terminal, and the first part parameters corresponding to the terminal include at least one of the following: the first part context parameters of the terminal and the first part policy of the terminal.

[0203] The second communication unit is used to send a request message to the first network element, wherein the request message is used by the first network element to generate a first part of parameters corresponding to the terminal.

[0204] The request message carries at least one of the following: identification of the terminal, scenario information, and user preference information.

[0205] The policy includes at least one of the following: UE policy, data packet detection rule PDR policy, and data flow binding policy.

[0206] The target node is one of the following: the terminal, a second network element, and the second network element is one of one or more core network elements.

[0207] The one or more core network network elements include at least one of the following: one or more core network control plane network elements, and one or more core network user plane network elements.

[0208] The one or more core network control plane network elements include at least one of the following: a network element responsible for access and / or mobility management, and a network element responsible for session management.

[0209] The device of the embodiment of the present application can realize the corresponding functions of each device in the aforementioned authentication method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the first network element or each module (sub-module, unit or component, etc.) in the target node 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 network element or each module (sub-module, unit or component, etc.) in the target node of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

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

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

[0212] Figure 13 is a schematic structural diagram of a chip 1300 according to an embodiment of the present application. The chip 1300 includes a processor 1310, 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 1300 may also include a memory 1320. The processor 1310 can call and execute a computer program from the memory 1320 to implement the method performed by the first network element or the target node in the embodiment of the present application. The memory 1320 may be a separate device independent of the processor 1310 or integrated into the processor 1310. In one possible implementation, the chip 1300 may also include an input interface 1330. The processor 1310 may control the input interface 1330 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips. In one possible implementation, the chip 1300 may also include an output interface 1340. The processor 1310 may control the output interface 1340 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

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

[0214] Figure 14 is a schematic block diagram of a communication system 1400 according to an embodiment of the present application. The communication system 1400 includes a first network element 1401 and a target node 1402. The first network element 1401 can be used to implement the corresponding functions implemented by the first network element in the above-described method. The target node 1402 can be used to implement the corresponding functions implemented by the target node in the above-described method. For the sake of brevity, these details are not further described here.

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

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

Claims

1. A communication method, comprising: A first network element generates first partial parameters corresponding to a terminal based on input information, where the first partial parameters corresponding to the terminal include at least one of the following: first partial context parameters of the terminal, first partial policies of the terminal; The first network element sends a reply message to one or more nodes, where the reply message carries at least some of the first partial parameters corresponding to the terminal, and the one or more nodes include at least one of the following: the terminal, an access network device corresponding to the terminal, one or more core network elements.

2. The method according to claim 1, wherein, The input information includes a request message.

3. The method according to claim 2, wherein, Before the first network element generates first partial parameters corresponding to a terminal based on input information, it further includes: The first network element receives a request message sent by a target node, where the target node is one of the following: the terminal, a second network element, and the second network element is one of the one or more core network elements.

4. The method according to claim 2 or 3, wherein, The request message carries at least one of the following: an identifier of the terminal, scenario information, user preference information.

5. The method according to any one of claims 1-4, wherein, The input information includes at least one of the following: subscription information of the terminal, policy and charging control (PCC) rules of the terminal, network status information, scenario information, user preference information.

6. The method according to claim 5, wherein, Before the first network element generates first partial parameters corresponding to a terminal based on input information, it further includes: The first network element obtains at least one of the following from at least some of the one or more core network elements: subscription information of the terminal, PCC rules of the terminal, network status information, scenario information, user preference information.

7. The method according to any one of claims 1-6, wherein, The input information includes: second partial parameters corresponding to the terminal, where the second partial parameters corresponding to the terminal are at least partially different from the first partial parameters corresponding to the terminal.

8. The method according to claim 7, wherein, Before the first network element generates first partial parameters corresponding to a terminal based on input information, it further includes: The first network element obtains the second partial parameters corresponding to the terminal from at least some of the one or more core network elements.

9. The method according to claim 7 or 8, wherein, The second partial parameters corresponding to the terminal include at least one of the following: second partial context parameters of the terminal, second partial policies of the terminal.

10. The method according to any one of claims 1-9, wherein, The policies include at least one of the following: UE policy, packet detection rule (PDR) policy, data flow binding policy.

11. The method according to any one of claims 1-10, wherein, The one or more core network elements include at least one of the following: one or more core network control plane elements, one or more core network user plane elements.

12. The method according to claim 11, wherein, The one or more core network control plane elements include at least one of the following: an element responsible for access and / or mobility management, an element responsible for session management.

13. A communication method, including: The target node receives a reply message sent by the first network element, wherein the reply message carries at least part of the content of the first part of the parameters corresponding to the terminal, and the first part of the parameters corresponding to the terminal includes at least one of the following: the first part of the context parameters of the terminal, the first part of the policies of the terminal.

14. The method according to claim 13, wherein, Before the target node receives the reply message sent by the first network element, it further includes: The target node sends a request message to the first network element, wherein the request message is used for the first network element to generate the first part of the parameters corresponding to the terminal.

15. The method according to claim 14, wherein, The request message carries at least one of the following: the identifier of the terminal, scenario information, user preference information.

16. The method according to any one of claims 13-15, wherein, The policy includes at least one of the following: UE policy, packet detection rule (PDR) policy, data flow binding policy.

17. The method according to any one of claims 13-16, wherein, The target node is one of the following: the terminal, a second network element, and the second network element is one of the one or more core network elements.

18. The method according to claim 17, wherein, The one or more core network elements include at least one of the following: one or more core network control plane elements, one or more core network user plane elements.

19. The method according to claim 18, wherein, The one or more core network control plane elements include at least one of the following: an element responsible for access and / or mobility management, an element responsible for session management.

20. A first network element, including: A first processing unit, configured to generate the first part of the parameters corresponding to the terminal based on input information, wherein the first part of the parameters corresponding to the terminal includes at least one of the following: the first part of the context parameters of the terminal, the first part of the policies of the terminal; A first communication unit, configured to send a reply message to one or more nodes, wherein the reply message carries at least part of the content of the first part of the parameters corresponding to the terminal, and the one or more nodes include at least one of the following: the terminal, the access network device corresponding to the terminal, one or more core network elements.

21. The first network element according to claim 20, wherein, The input information includes a request message.

22. The first network element according to claim 21, wherein, The first communication unit is configured to receive a request message sent by a target node, wherein the target node is one of the following: the terminal, a second network element, and the second network element is one of the one or more core network elements.

23. The first network element according to claim 21 or 22, wherein, the request message carries at least one of the following: the identifier of the terminal, scenario information, user preference information.

24. The first network element according to any one of claims 20-23, wherein, the input information includes at least one of the following: the subscription information of the terminal, the policy and charging control (PCC) rules of the terminal, network status information, scenario information, user preference information.

25. The first network element according to claim 24, wherein, the first communication unit is configured to obtain at least one of the following from at least some of the one or more core network elements: the subscription information of the terminal, the PCC rules of the terminal, the network status information, the scenario information, the user preference information.

26. The first network element according to any one of claims 20-25, wherein, the input information includes: the second part of the parameters corresponding to the terminal, wherein the second part of the parameters corresponding to the terminal is at least partially different from the first part of the parameters corresponding to the terminal.

27. The first network element according to claim 26, wherein, the first communication unit is configured to obtain the second part of the parameters corresponding to the terminal from at least some of the one or more core network elements.

28. The first network element according to claim 26 or 27, wherein, the second part of the parameters corresponding to the terminal includes at least one of the following: the second part of the context parameters of the terminal, the second part of the policies of the terminal.

29. The first network element according to any one of claims 20-28, wherein, the policies include at least one of the following: UE policies, packet detection rule (PDR) policies, data flow binding policies.

30. The first network element according to any one of claims 20-29, wherein, the one or more core network elements include at least one of the following: one or more core network control plane elements, one or more core network user plane elements.

31. The first network element according to claim 30, wherein, the one or more core network control plane elements include at least one of the following: an element responsible for access and / or mobility management, an element responsible for session management.

32. A target node, comprising: a second communication unit, configured to receive a reply message sent by the first network element, wherein the reply message carries at least some of the first part of the parameters corresponding to the terminal, and the first part of the parameters corresponding to the terminal includes at least one of the following: the first part of the context parameters of the terminal, the first part of the policies of the terminal.

33. The target node according to claim 32, wherein, the second communication unit is configured to send a request message to the first network element, wherein the request message is used for the first network element to generate the first part of the parameters corresponding to the terminal.

34. The target node according to claim 33, wherein, the request message carries at least one of the following: the identifier of the terminal, scenario information, user preference information.

35. The target node according to any one of claims 32-34, wherein, The strategy includes at least one of the following: UE strategy, Packet Detection Rule (PDR) strategy, data flow binding strategy.

36. The target node according to any one of claims 32 - 35, wherein, the target node is one of the following: the terminal, a second network element, and the second network element is one of one or more core network elements.

37. The target node according to claim 36, wherein, the one or more core network elements include at least one of the following: one or more core network control plane elements, one or more core network user plane elements.

38. The target node according to claim 37, wherein, the one or more core network control plane elements include at least one of the following: an element responsible for access and / or mobility management, an element responsible for session management.

39. A first network element, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and run the computer program stored in the memory, so that the first network element executes the method according to any one of claims 1 to 12.

40. A target node, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and run the computer program stored in the memory, so that the target node executes the method according to any one of claims 13 to 19.

41. A chip, comprising: a processor, which is used to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 12, or claims 13 to 19.

42. A computer-readable storage medium, which is used to store a computer program. When the computer program is run by a device, the device executes the method according to any one of claims 1 to 12, or claims 13 to 19.

43. A computer program product, which includes computer program instructions. The computer program instructions cause a computer to execute the method according to any one of claims 1 to 12, or claims 13 to 19.

44. A computer program, the computer program causes a computer to execute the method according to any one of claims 1 to 12, or claims 13 to 19.

Images