Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The method is applied to a first entity. The method comprises: receiving first information from a first terminal device, wherein the first information is used for requesting a first core network service, and the function of the first entity comprises providing the first core network service for the first terminal device; starting a first process on the basis of the first core network service, wherein an identifier ID of the first process is a first ID; and on the basis of the first ID, managing first context, wherein the first context is context generated when the first entity executes the first process. By means of the present application, frequent user context interaction between a plurality of satellites can be avoided, thereby avoiding an error in user context on which a core network service is based, and further improving quality of a service provided by a core network. In addition, signaling overheads caused by user context interaction can also be reduced.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202510034039.3, filed with the State Intellectual Property Office of China on January 8, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to satellite networks, and more specifically, to a communication method and communication device. Background Technology

[0003] With the development of information technology, there is a more urgent need for efficient, mobile, and diverse communication. In some important fields, such as space communication, aviation communication, and maritime communication, non-terrestrial networks (NTNs) such as satellite communication play an irreplaceable role. In satellite communication systems, to reduce the latency caused by core network signaling traveling between satellite and ground, core network elements can be deployed on satellite platforms to provide core network services to users.

[0004] Due to limited satellite payload capacity, it is difficult to deploy complete core network functionality on a single satellite. Therefore, different core network elements may be deployed on different satellites. To fulfill a user's requested core network service, multiple core network elements may need to work together to achieve that service. This necessitates frequent interaction of user context between multiple satellites. However, inter-satellite links can be unstable, and frequent user context transitions can lead to a higher probability of context errors, impacting the quality of services provided by the core network. Furthermore, frequent user context transitions result in significant signaling overhead. Summary of the Invention

[0005] This application provides a communication method and apparatus that can avoid frequent interaction of user context among multiple satellites, thereby preventing errors in the user context upon which core network services are based and improving the quality of services provided by the core network. Furthermore, it can reduce the signaling overhead caused by interacting with user context.

[0006] Firstly, a communication method is provided, which can be applied to the network side, such as a network or a communication module within a network, or a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core) responsible for communication functions within the network. Taking the application of this method to a first entity as an example, the first entity is deployed on a first satellite. In this method, the first entity receives first information from a first terminal device, the first information being used to request a first core network service. The functions of the first entity include providing the first core network service to the first terminal device; initiating a first process based on the first core network service, the identifier ID of the first process being a first ID; and managing a first context based on the first ID, the first context being a context generated by the first entity when executing the first process.

[0007] In this embodiment, a first entity deployed on a single satellite can implement core network services. The core network services requested by the terminal device can be implemented through this first entity, avoiding the need for collaborative completion by core network elements on multiple satellites. This reduces the probability of errors caused by frequent user context migrations, thereby improving the quality of services provided by the core network. Furthermore, since the core network services requested by the terminal device are deployed on a single entity, the context managed by this entity is less than the context managed by multiple core network elements in traditional solutions, thus reducing signaling overhead during user context migrations.

[0008] Furthermore, the first entity can initiate a first process based on the first core network and manage the first context based on the ID of the first process. This allows for effective management and maintenance of the context generated for the first core network service requested by the first terminal device. Specifically, if a failure occurs during the execution of the first process, preventing the first entity from continuing, the first entity can migrate the context generated for the first core network service. This migration, based on the ID of the first process, improves the accuracy of the context migration, preventing failures of the first core network service due to migration errors and facilitating its completion.

[0009] In conjunction with the first aspect, in one possible implementation, the first context includes parameters generated during the execution of the first process by the first entity, and / or parameters generated after the first entity completes the first process.

[0010] In this way, the first entity can manage the parameters generated during the execution of the first process and / or the parameters generated after the first entity completes the first process, thereby improving the reliability of the first entity providing the first core network service to the first terminal device. On the one hand, the first entity's management of the parameters generated during the execution of the first process can prevent the first entity from losing intermediate parameters due to failures during the execution of the first process, which is conducive to the completion of the first process and thus conducive to reliable communication with the first terminal device. On the other hand, the first entity's management of the parameters generated after the first process is completed can improve the reliability of communication with the first terminal device.

[0011] In conjunction with the first aspect, in one possible implementation, the method further includes performing any of the following operations on the first process: process termination, process restart, process execution, or process release.

[0012] In this embodiment, the first entity can perform lifecycle management on the first process according to the current network state, such as performing any operation on the first process, such as process termination, process restart, process running, or process release, thereby improving the flexibility of the first entity in executing the first process and facilitating the first entity's flexible control over the first process.

[0013] In conjunction with the first aspect, in one possible implementation, the method further includes: sending indication information to the first terminal device based on the first ID, the indication information being used to indicate that the first entity has performed any of the following operations: suspending the first process, restarting the first process, running the first process, or releasing the first process.

[0014] In this embodiment, the first entity sends instruction information to the first terminal device, which helps the first terminal device understand the specific operations performed by the first entity on the process of the first core network service. This allows the first terminal device to perform corresponding actions based on the operations indicated by the instruction information, thereby enabling the first terminal device to take flexible actions based on the lifecycle management of the first process by the first entity, and ultimately facilitating the successful execution of the first process.

[0015] In conjunction with the first aspect, in one possible implementation, the first information includes a second ID and / or a first parameter, wherein the second ID is an ID used for the requesting process, and the first parameter is used to indicate the type of service function of the first core network service.

[0016] In conjunction with the first aspect, in one possible implementation, initiating a first process based on a first core network service includes: initiating a first process based on a first core network service and a second ID.

[0017] In this embodiment, since the second ID is used as the ID for requesting the process, when the first entity receives the second ID, it can start the first process based on the first core network service and the second ID, thereby improving the efficiency of the first entity starting the first process. Furthermore, the content included in the first information can be standardized. By defining a standardized information format, it is further beneficial to improve the efficiency of the first entity starting the first process.

[0018] In conjunction with the first aspect, in one possible implementation, the method further includes: sending second information to a first terminal device, the second information including a first ID and / or a second parameter, the second parameter including parameters generated after the first process has been executed.

[0019] This facilitates communication between the first terminal device and the first entity based on the second information, meaning that the first terminal device can transmit relevant information to the first entity based on the second information, thereby ensuring the accuracy of communication.

[0020] In conjunction with the first aspect, in one possible implementation, the first entity includes multiple core network elements, each with different core network service functions. The method further includes: when the first core network service includes multiple core network services, routing the multiple core network services to their corresponding core network elements based on first information. The aforementioned initiation of the first process based on the first core network service includes: multiple core network elements initiating corresponding sub-processes based on their respective core network services, the ID of the sub-process being a first sub-ID, the first process including multiple sub-processes, and the first ID including multiple first sub-IDs.

[0021] In this way, since multiple core network elements can simultaneously launch corresponding sub-processes according to their respective core network services, the time required for the first entity to complete the first core network service requested by the first terminal device can be reduced, thereby improving the efficiency of the first entity in completing the first core network service requested by the first terminal device.

[0022] In conjunction with the first aspect, in one possible implementation, the method further includes: sending third information to a second entity, the third information being used to request the migration of a second context, the second entity having functions including providing a first core network service to a first terminal device; receiving feedback information from the second entity, the feedback information being used to indicate whether the first entity can or cannot migrate the second context to the second entity; and migrating or not migrating the second context to the second entity based on the feedback information.

[0023] In this way, when the first entity is unable or unwilling to provide the first core network service to the first terminal device, and when the first entity successfully migrates the first context, the second entity can provide the first core network service to the first terminal device, thereby improving the reliability of completing the first core network service.

[0024] In conjunction with the first aspect, in one possible implementation, the method further includes: receiving fourth information from the second entity when the first entity migrates the second context to the second entity, the fourth information including information allocated by the second entity for the process of the first core network service corresponding to the second context; and sending the fourth information to the first terminal device.

[0025] In conjunction with the first aspect, in one possible implementation, the fourth information includes at least one of the following: a third ID, an IP address, and a port number.

[0026] In this way, the fourth information sent by the first entity to the first terminal device is beneficial for the first terminal device to communicate with the second entity based on the fourth information, thereby improving the accuracy and reliability of the communication between the first terminal device and the second entity.

[0027] In particular, under normal circumstances, the context migration action occurs before the first process has finished executing. Therefore, when the first entity migrates the second context to the second entity, it is beneficial for the second entity to start the corresponding process for the first core network service corresponding to the second context. Thus, the second entity can execute the corresponding process based on the fourth information and send the fourth information to the first terminal device. This helps to improve the accuracy and reliability of communication between the first terminal device and the second entity.

[0028] In conjunction with the first aspect, in one possible implementation, the first core network service includes at least one of the following: session registration service, session establishment service, session maintenance service, handover service, and location service.

[0029] Secondly, this application provides a communication method that can be applied to the terminal side, such as a terminal or a communication module within a terminal, or a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip or system-in-package chip containing a modem core) responsible for communication functions within the terminal. Taking the application of this method to a first terminal device as an example, in this method, the first terminal device generates first information, which is used to request a first core network service; and sends the first information to a first entity, the function of which includes providing the first core network service to the first terminal device.

[0030] In this embodiment, a first entity deployed on a single satellite can implement core network services. The core network services requested by the terminal device can be implemented through this first entity, avoiding the need for collaborative completion by core network elements on multiple satellites. This reduces the probability of errors caused by frequent user context migrations, thereby improving the quality of services provided by the core network. Furthermore, since the core network services requested by the terminal device are deployed on a single entity, the context managed by this entity is less than the context managed by multiple core network elements in traditional solutions, thus reducing signaling overhead during user context migrations.

[0031] In conjunction with the second aspect, in one possible implementation, the method further includes: receiving indication information from a first entity, the indication information being used to instruct the first entity to perform any of the following operations: suspending the first process, restarting the first process, running the first process, or releasing the first process.

[0032] In this embodiment of the application, after receiving the instruction information from the first entity, the first terminal device can understand the specific operation of the process executed by the first entity for the first core network service. The first terminal device can perform corresponding actions according to the operation indicated by the instruction information. In this way, the first terminal device can perform flexible actions based on the life cycle management of the first process by the first entity, which is conducive to the successful execution of the first process.

[0033] In conjunction with the second aspect, in one possible implementation, the first information includes a second ID and / or a first parameter, where the second ID is an ID used for the requesting process, and the first parameter is used to indicate the first core network service requested.

[0034] In this embodiment, since the second ID is used as the ID for requesting the process, it is beneficial for the first entity to start the first process based on the first core network service and the second ID after receiving the second ID, thereby improving the efficiency of the first entity starting the first process. Furthermore, the content included in the first information can be standardized. By defining a standardized information format, it is further beneficial to improve the efficiency of the first entity starting the first process.

[0035] In conjunction with the second aspect, in one possible implementation, the method further includes: receiving second information from a first entity, the second information including a first ID and / or a second parameter, the second parameter including parameters generated after the first process is executed; and communicating with the first entity based on the second information.

[0036] In this way, the first terminal device can communicate with the first entity based on the second information, that is, the first terminal device can transmit relevant information to the first entity based on the second information, thereby ensuring the accuracy of communication.

[0037] In conjunction with the second aspect, in one possible implementation, the method further includes: receiving fourth information from a first entity, the fourth information including information allocated by a second entity for the process of a first core network service corresponding to a second context, the second entity being the target entity to which the first entity migrates the functions of the first core network service; and communicating with the second entity based on the fourth information.

[0038] In conjunction with the second aspect, in one possible implementation, the fourth information includes at least one of the following: a third ID, an IP address, and a port number.

[0039] In this way, after the first terminal device receives the fourth information, it can communicate with the second entity based on the fourth information, thereby improving the accuracy and reliability of the communication between the first terminal device and the second entity.

[0040] In particular, under normal circumstances, the context migration action occurs before the first process has finished executing. Therefore, when the first entity migrates the second context to the second entity, it is beneficial for the second entity to start the corresponding process for the first core network service corresponding to the second context. Thus, the second entity can execute the corresponding process based on the fourth information and send the fourth information to the first terminal device. This can improve the accuracy and reliability of communication between the first terminal device and the second entity.

[0041] In conjunction with the second aspect, in one possible implementation, the first core network service includes at least one of the following: session registration service, session establishment service, session maintenance service, handover service, and location service.

[0042] Thirdly, this application provides a communication device that implements the functions described in the first aspect. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware. The beneficial effects are described in the first aspect and will not be repeated here. In one possible design, the communication device includes: a communication unit for receiving first information from a first terminal device, the first information being used to request a first core network service, the first entity's function including providing the first core network service to the first terminal device; a processing unit for initiating a first process based on the first core network service, the first process's identifier being a first ID; and managing a first context based on the first ID, the first context being a context generated by the first entity when executing the first process. These units can perform the corresponding functions in the method examples of the first aspect, as described in the detailed description in the method examples and will not be repeated here.

[0043] In one possible implementation, the device is a communication device (such as the first entity). When the device is a communication device, the communication unit can be a transceiver, or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0044] In another possible implementation, the device is a chip, chip system, circuit, or communication module for a communication device (such as the first entity). When the device is a chip, chip system, or circuit for a communication device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit may be at least one processor, processing circuit, or logic circuit.

[0045] Fourthly, this application provides a communication device that implements the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware. The beneficial effects are described in the second aspect and will not be repeated here. In one possible design, the communication device includes: a processing unit for generating first information, which requests a first core network service; and a communication unit for sending the first information to a first entity, the first entity's function including providing the first core network service to a first terminal device. These units can perform the corresponding functions in the method examples of the second aspect above, as detailed in the method examples and will not be repeated here.

[0046] In one possible implementation, the device is a communication device (such as a first terminal device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0047] In another possible implementation, the device is a chip, chip system, circuit, or communication module for a communication device (such as a first terminal device). When the device is a chip, chip system, or circuit for a communication device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit may be at least one processor, processing circuit, or logic circuit.

[0048] Fifthly, this application provides a communication device including at least one processor for executing computer programs or instructions to perform the methods described in the first to second aspects or any possible implementations of the first to second aspects. Optionally, the device further includes a memory for storing the computer programs or instructions. Optionally, the device further includes a communication interface coupled to the processor, which can be used to input computer programs or instructions to the processor or to output information from the processor.

[0049] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0050] In another implementation, the device is a chip, chip system or circuit or communication module for communication equipment (such as terminal equipment or network equipment).

[0051] Sixthly, this application provides a processor for executing the methods provided in the first to second aspects or any possible implementation of the first to second aspects.

[0052] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0053] In a seventh aspect, this application provides a computer-readable storage medium storing computer-readable instructions that, when read and executed by a computer, cause the computer to perform the methods described in the first to second aspects or any possible implementation of the first to second aspects.

[0054] Eighthly, this application provides a computer program product that, when read and executed by a computer, causes the computer to perform the methods described in the first to second aspects or any possible implementation of the first to second aspects.

[0055] Ninthly, this application provides a chip, which includes a processor and a communication interface. The processor reads instructions from a memory through the communication interface and executes the method provided in the first to second aspects or any one of the first to second aspects.

[0056] Optionally, as one implementation, the chip also includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions in the memory. When the computer programs or instructions are executed, the processor is used to execute the method provided by the first to second aspects or any one of the first to second aspects described above.

[0057] In a tenth aspect, this application provides a communication system comprising means having a method for implementing any one of the possible implementations of the first to second aspects, or all the possible implementations of the first to second aspects, and various possible design functions. Attached Figure Description

[0058] Figure 1 is a schematic diagram of the network architecture of a communication system.

[0059] Figure 2 is a schematic diagram of the network architecture of another communication system.

[0060] Figure 3 is a schematic diagram of a communication method provided in an embodiment of this application.

[0061] Figure 4 is a schematic diagram of process association provided in an embodiment of this application.

[0062] Figure 5 is a schematic diagram of a process-based protocol stack provided in an embodiment of this application.

[0063] Figure 6 is a schematic diagram of another communication method provided in an embodiment of this application.

[0064] Figure 7 is a schematic diagram of the communication device provided in an embodiment of this application.

[0065] Figure 8 is a schematic diagram of another communication device provided in an embodiment of this application.

[0066] Figure 9 is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0067] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0068] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include devices, components, modules, etc., other than those illustrated, and / or may not include all and all of the devices, components, modules, etc. discussed in conjunction with the accompanying drawings.

[0069] In the embodiments of this application, words such as "exemplarily" and "for example" can be used to indicate examples, illustrations, or descriptions to present concepts in a specific manner. Any embodiment or design described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs.

[0070] The business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0071] References to "one embodiment" or "some embodiments" as used in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in still other embodiments" appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0072] The descriptions of "first," "second," etc., appearing in the embodiments of this application are for illustrative purposes and to distinguish the objects being described, unless otherwise specified. They are not in any particular order and do not indicate any special limitation on the number of objects in the embodiments of this application, nor do they constitute any limitation on the embodiments of this application.

[0073] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. 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 embodiments of this application.

[0074] It is understandable that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0075] The technical solutions of this application embodiment can be applied to various communication systems, including but not limited to: Long Term Evolution (LTE) systems, New Radio (NR) systems, and other fifth-generation (5G) systems. thThis includes various mobile communication systems such as 5G, narrowband Internet of Things (NB-IoT), enhanced machine-type communication (eMTC), enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), satellite communication systems, LTE-machine-to-machine (LTE-M) systems, and systems that evolve from 5G onwards.

[0076] In the embodiments of this application, the term "communication" can also be described as "data transmission," "signal transmission," "information transmission," or simply "transmission." In the embodiments of this application, transmission can include sending or receiving. Exemplarily, transmission can be uplink transmission, such as a terminal device sending a signal to a network device; transmission can also be downlink transmission, such as a network device sending a signal to a terminal device; transmission can also be sidelink transmission, such as a terminal device sending a signal to another terminal device. Exemplarily, "transmission" can be air interface-level transmission, or it can refer to signal transmission at a chip input (I) / output (O) interface, rather than air interface-level transmission.

[0077] Figure 1 is a schematic diagram of a network architecture for a communication system. This network architecture includes at least one network function (NF). For example, at least one NF may include: a network capability opening network element, a network storage function network element, a network data analysis network element, an application function network element, a policy control network element, a unified data storage network element, a unified data management network element, an access and mobility management network element, a session management network element, a binding support function network element, a user plane function network element, and a data network (DN) connecting to the operator's network. Terminal devices can send service data to the data network and receive service data from the data network through access network devices and user plane function network elements. Access network devices can communicate with the network management system.

[0078] Terminal devices can be any device with wireless transceiver capabilities. They can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; on water (such as ships); and in the air (e.g., on airplanes, balloons, and satellites). Terminal devices can communicate with the core network via a radio access network (RAN), exchanging voice and / or data with the RAN. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, mobile internet devices (MIDs), wearable devices, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes. Wireless terminals, drones, drone controllers, etc., in the home (referring to the use of a mobile device). The embodiments of this application do not limit the application scenario. Terminal devices may sometimes be called user equipment (UE), mobile stations, and remote stations, etc. The embodiments of this application do not limit the specific technology, device form, or name used by the terminal device. The terminal device can be a mobile device that supports a satellite-to-ground air interface. The terminal device can access the satellite network through the air interface and initiate services such as making calls and accessing the internet.

[0079] Access network equipment can be any device in a network used to connect terminal devices to a wireless network. Access network equipment can be a node in a wireless access network, also known as a base station, or a RAN node (or device). For ease of description, RAN will sometimes be used below to refer to access network equipment. Access network equipment may include evolved base stations (NodeBs, eNBs, or e-NodeBs) in long-term evolution (LTE) systems or evolved LTE-Advanced (LTE-A) systems, such as traditional macro base stations (eNBs) and micro base stations (eNBs) in heterogeneous network scenarios. It may also include next-generation node Bs (gNBs) in 5G or NR systems, radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), transmission reception points (TRPs), home base stations (e.g., home evolved NodeBs or home Node Bs (HNBs), base band units (BBUs), base band pools, or wireless fidelity (WiFi) access points (APs). Alternatively, it may include centralized units in cloud radio access network (CloudRAN) systems. The embodiments in this application are not limited to either a Control Unit (CU) or a Distributed Unit (DU). In a scenario where the access network equipment includes a CU and a DU deployed separately, the CU supports protocols such as Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP); the DU mainly supports radio link control (RLC), media / medium access control (MAC), and physical layer protocols. The access network equipment can provide radio access services. For example, the access network equipment can schedule radio resources for the terminal equipment to access the network.For example, access network equipment can provide reliable wireless transmission protocols and / or data encryption protocols.

[0080] Network capability open elements can expose some network functions to applications in a controlled manner. In 5G communication systems, network capability open elements can be network exposure functions (NEF). In future communication systems, network capability open elements may still be NEF elements, or they may have other names; this application is not limited to these.

[0081] Network storage function (NRF) network elements are primarily used for registration, discovery, and status detection of network elements, the services they provide, and their functions. NRF network elements enable automated management, selection, and expansion of network function services, and allow each network function to discover services provided by other network functions. In 5G communication systems, NRF network elements may be network repository functions (NRFs). In future communication systems, NRF network elements may remain NRF network elements or have other names; this application does not limit this.

[0082] Network data analytics elements can collect, analyze, and predict data from various network functions (NFs), application function network elements (via network capability open function network elements), terminal devices, network management systems, etc. These elements possess data collection, training, analysis, and inference capabilities. After training based on relevant data, the network data analytics element can provide data analysis results to network functions, application function network elements, terminal devices, or network management systems. These results can assist the network in selecting service quality parameters for services, performing traffic routing, or selecting background data transmission strategies. Network functions include, for example, policy control network elements, session management network elements, user plane function network elements, and access and mobility management network elements. In 5G communication systems, the network data analytics element can be a network data analytics function (NWDAF). In future communication systems, the network data analytics element may still be an NWDAF element, or it may have other names; this application is not limiting.

[0083] Application function network elements (AF elements) can be used to convey application-side requests to the network side. For example, these requests may include Quality of Service (QoS) requirements or user state event subscriptions. AF elements can provide various application service data to the control plane network elements of the operator's communication network, or obtain network data and control information from the control plane network elements. In 5G communication systems, AF elements can be application functions (AFs). In future communication systems, AF elements may still be AF elements, or they may have other names; this application is not limited to any particular name. For example, AF elements can also be called application servers or service servers. Furthermore, AF elements can be deployed on the operator's network or deployed by a third party.

[0084] Policy control network elements can be used to formulate and manage policies for the entire network (e.g., a 5G network). Policy control network elements can include policy control functions, charging policy control functions, etc. They can generate and maintain QoS flow control policies, network slicing policies, mobility management policies, charging policies, UE access policies, etc. Policy control network elements can dynamically generate and adjust policies based on the operator's service needs and network status, and distribute these policies to relevant network elements such as access and mobility management network elements, session management network elements, and user plane function network elements to guide their behavior. Furthermore, policy control network elements can receive QoS requirements from application function network elements and translate them into corresponding policies. In 5G communication systems, policy control network elements can be policy control functions (PCFs). In future communication systems, policy control network elements may still be PCF network elements, or they may have other names; this application is not limited to these.

[0085] A unified data storage network element is primarily used to store structured data information, including subscription information, policy information, and network data or service data with standardized formats. In 5G communication systems, the unified data storage network element can be a unified data repository (UDR). In future communication systems, the unified data storage network element may still be a UDR network element, or it may have other names; this application is not limiting.

[0086] A unified data management network element is primarily used to manage and store user data (or subscription information) from terminal devices. This includes, for example, user identity information, authentication information, subscription information, and policy information. The unified data management network element can provide user data query and update services to other network elements. It can support user authentication, authorization, and key management functions. Furthermore, the unified data management network element can update and synchronize user data according to the policies of policy control network elements. In 5G communication systems, the unified data management network element can be a unified data management (UDM) element. In future communication systems, the unified data management network element may still be a UDM element, or it may have other names; this application is not limiting.

[0087] Access and mobility management (AML) network elements are primarily used for terminal attachment and tracking area update procedures in mobile networks. AML network elements can provide non-access stratum (NAS) messages, complete registration management, connection management, reachability management, allocate tracking area lists (TA lists), grant access authorization, authenticate, and manage mobility, and transparently route session management (SM) messages to session management network elements. In 5G communication systems, AML network elements can be access and mobility management functions (AMF). In future communication systems, AML network elements may remain AMF network elements or have other names; this application is not limited to these names.

[0088] Session management network elements can be used for session and bearer management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating and managing Internet Protocol (IP) addresses (or Internet Protocol addresses) for the UE, and selecting user plane function network elements that provide packet forwarding capabilities. For example, the session management network element can select a suitable user plane function network element for the UE based on the UE's request and the policy control information of the policy control network element, establish a session with that user plane function network element, and generate QoS rules and charging rules. The session management network element can control the data forwarding and processing behavior of the user plane function network element. In 5G communication systems, the session management network element can be a session management function (SMF). In future communication systems, the session management network element may still be an SMF network element, or it may have other names; this application is not limited to these.

[0089] The binding support network element is mainly used for session binding, allowing users to select policy control function network elements. In 5G communication systems, the binding support network element can be a binding supporting function (BSF). In future communication systems, the binding support network element may still be a BSF network element, or it may have other names; this application does not limit this.

[0090] User plane function network elements (MPF elements) can be used to process user packets, such as forwarding and billing. Furthermore, MPF elements can be used for user plane data packet routing, forwarding, QoS flow processing, threshold control, traffic monitoring, authentication, data packet detection, and reporting. MPF elements can also be used for UE IP address management and core network (CN) tunnel information management. MPF elements can reside in the 5G core network user plane, providing UEs with high-speed, efficient, and flexible data transmission services. In addition, MPF elements can perform data packet filtering, traffic shaping, and billing according to control plane instructions, achieving fine-grained management and control of user data flows. MPF elements can connect to access network equipment via the N3 interface and to the data network via the N6 interface, thereby enabling data transmission between the UE and the external data network. MPF elements can also be referred to as Protocol Data Unit (PDU) session anchors (PSAs). In 5G communication systems, user plane function network elements can be user plane functions (UPF). In future communication systems, user plane function network elements can still be UPF network elements, or they can have other names. This application does not limit this.

[0091] Network management (OAM) is primarily used for daily network and service analysis, forecasting, planning, and configuration, as well as network and service testing and fault management. OAM can interact with RAN to obtain information such as radio channel conditions and radio resource utilization. In 5G communication systems, OAM can be operations administration and management (OAM). In future communication systems, OAM may remain an OAM network element or have other names; this application does not limit this.

[0092] Data networks are primarily used to provide data transmission services for terminal devices. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or dedicated networks jointly deployed by operators, such as configured IP multimedia core network subsystems (IMS) services. Data networks can also originate from third parties.

[0093] In the architecture shown in Figure 1, the interface names and functions between the various network elements are as follows:

[0094] 1. N1: The interface between AMF and UE, which can be used to transmit QoS control rules to UE, etc.

[0095] 2. N2: The interface between AMF and (R)AN, which can be used to transmit radio bearer control information from the core network side to the RAN.

[0096] 3. N3: The interface between RAN and UPF, used to transmit uplink or downlink user plane data between RAN and UPF.

[0097] 4. N4: The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0098] 5. N6: The interface between UPF and DN, used to transmit uplink or downlink user data streams between UPF and DN.

[0099] 6. The service-oriented interfaces Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Nnwdaf, Naf, Nudr, Nudm, and Nbsf are the service-oriented interfaces provided by the NEF, NRF, AMF, PCF, SMF, UDM, NWDAF, AF, UDR, UDM, and BSF network elements, respectively, and are used to call the corresponding service-oriented operations.

[0100] The aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.

[0101] The naming conventions described above are defined solely for the purpose of distinguishing different functions and should not be construed as limiting this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in other future networks, some or all of the aforementioned network terminology may be retained from 5G, or other names may be used. The interface names between the various network elements in Figure 1 are merely examples; in specific implementations, the interface names may be different, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0102] The term "network element" can also be referred to as an entity, device, apparatus, or module, etc., and this application does not specifically limit it. Furthermore, in this application, for ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, the PCF network element is abbreviated as PCF. In this case, "PCF" should be understood as PCF network element or PCF entity. The following omits descriptions of the same or similar cases.

[0103] Figure 2 is a schematic diagram of the network architecture of another communication system 200. Communication system 200 can combine satellite communication technology and cellular communication technology. As shown in Figure 2, ground-based mobile terminals can access the network via an air interface. Access network equipment (e.g., base stations) can be deployed on satellites and connected to the core network functions on the satellites via wireless links. Wireless links can exist between satellites, which can be used to complete signaling interaction and user data transmission between one access network device and other access network devices. The descriptions of the terminals and base stations in Figure 2 can be found in the preceding text, such as the description in Figure 1. They will not be repeated here. Some network elements and interfaces in Figure 2 are described below.

[0104] Optionally, the core network can be a 5G core network (5GC or 5GCN). The core network can be divided into control plane and data plane functional entities. For example, the core network may include network slice selection function (NSSF), authentication server function (AUSF), UDM, NEF, NRF, PCF, AF, AMF, SMF, or UPF, etc. However, this application is not limited to this; the core network in Figure 2 can also be the core network of other communication systems.

[0105] For example, the data network can be the Internet.

[0106] The air interface can refer to the wireless link between the terminal and the access network equipment.

[0107] The Xn interface can be an interface between base stations. For example, the Xn interface can be used for signaling interactions such as handover.

[0108] The NG interface can be the interface between the base station and the core network. For example, the NG interface can be used to exchange non-access stratum (NAS) signaling with the core network. As another example, the NG interface can be used to exchange user service data.

[0109] A service-based architecture (SBA) interface can be a service-oriented interface between a base station and onboard functional units. Onboard functional units can be functions or entities deployed on a satellite. For example, onboard functional units can be used to implement handover functions, authentication functions, or session establishment functions.

[0110] In satellite communication systems, to reduce the latency caused by core network signaling round trips between satellite and ground, core network elements can be deployed on satellite platforms to provide core network services to users. Due to limited satellite payload capacity, it is difficult to deploy complete core network functionality on a single satellite; therefore, different core network elements may be deployed on different satellites. For example, an AMF (Advanced Management Function) might be deployed on one satellite, and an SMF (Self-Managing Function) on another. To fulfill a user-requested core network service (e.g., user registration, session establishment, session release), multiple core network elements need to work together to perform the corresponding operations. This necessitates frequent interaction of user context between multiple satellites. However, inter-satellite links can be unstable, and frequent user context transitions can lead to a higher probability of context errors, impacting the quality of services provided by the core network. Furthermore, frequent user context transitions result in significant signaling overhead.

[0111] Therefore, this application provides a communication method in which entities implementing core network services are deployed on satellites. This avoids frequent interaction of user contexts among multiple satellites, thereby preventing errors in the user context upon which the core network services are based and improving the quality of services provided by the core network. Furthermore, the communication method provided in this application can reduce the signaling overhead caused by interacting with user contexts.

[0112] As shown in Figure 3, a communication method 300 provided in an embodiment of this application is provided. The communication method 300 may include steps 310 to 350.

[0113] 310. Generate the first information, which is used to request the first core network service.

[0114] 320, Send the first message to the first entity.

[0115] In this embodiment, steps 310-320 can be executed by the terminal device, by a module of the terminal device (e.g., a chip, chip system, or processor), or by a logic node, logic module, or software capable of implementing all or part of the terminal device's functions. For ease of description, the terminal device will be used as an example throughout this document.

[0116] The first information in this embodiment of the application is used to request the first core network service, which can be understood as: the first information is used to request the first entity to provide the first core network service.

[0117] Optionally, the first core network service includes at least one of the following: session registration service, session establishment service, session maintenance service, handover service, and location service. This application does not limit the name of the first core network service; it may also be referred to as a service, function, business, core network function, core network business, network service, network function, network business, or any other name.

[0118] This application does not limit the name of the first information, which may also be called request information, request, service request, or other names.

[0119] In this application, the term "send" can be understood as direct sending. For example, the first terminal device directly sends the first information to the first entity. The term "send" can also be understood as indirect sending. For example, the first terminal device sends the first information to the base station, and the base station sends the first information to the first entity. That is, the base station can forward the information sent by the first terminal device to the first entity. The base station can establish an RRC connection with the first terminal device beforehand.

[0120] 330, receiving first information from the first terminal device, the function of the first entity includes providing first core network services to the first terminal device.

[0121] The function of the first entity, including providing the first core network service to the first terminal device, can be understood as the first core network service being implemented by the first entity. The term "implementation" can be understood as the first entity completing the implementation of the first core network service, or as the first entity fully executing the function sequence of the first core network service.

[0122] Taking the registration service as an example of the primary core network service, the function sequence for registration can be: context read function -> authentication / authorization function -> policy generation function -> context write function. By executing each function in the order shown above, the logical functionality of registration can be achieved. Traditional core network elements cannot implement the registration service independently. For example, the context read function may require execution by the UDM; the authentication / authorization function may require execution by the AUSF; and the policy generation function may require execution by the PCF. In other words, the above registration service requires execution by multiple core network elements. These core network elements are often deployed on multiple satellites. Therefore, in traditional solutions, the above registration service may require execution by multiple satellites, i.e., it requires implementation by multiple satellites.

[0123] The first entity in this embodiment can implement the registration service. That is, the first entity can execute the function sequence of the registration service described above. In other words, in this embodiment, an entity deployed on a satellite can implement the registration service, i.e., it can execute the function sequence of the registration service described above. Therefore, in this embodiment, the registration service can be completed by a single satellite, i.e., it can be implemented by a single satellite.

[0124] In this application, the term "receive" can be understood as direct reception. For example, the first entity directly receives first information from the first terminal device. The term "receive" can also be understood as indirect reception. For example, the first entity receives first information from a base station, and the base station receives first information from the first terminal device. That is, the base station can forward information sent by the first terminal device to the first entity. The base station can establish an RRC connection with the first terminal device beforehand.

[0125] 340. Start the first process according to the first core network service. The identifier (identity, ID) of the first process is the first ID.

[0126] 350. The first context is managed based on the first ID. The first context is the context generated by the first entity when executing the first process.

[0127] In this embodiment, steps 330-350 can be executed by the first entity, by a module of the first entity (e.g., a chip, chip system, or processor), or by a logic node, logic module, or software capable of implementing all or part of the functions of the first entity. For ease of description, the first entity will be used as an example below.

[0128] In this embodiment, the first entity initiates a first process based on the first core network service. This first process can be understood as a program execution process specifically for the first core network service. Here, "initiation" can be understood as the first entity receiving the initial context of the first terminal device or loading a cached process. When the first terminal device sends the first information for requesting the first core network service to the first entity for the first time, "initiation" can be understood as the first entity receiving the initial context of the first terminal device. When the first terminal device is not sending the first information for requesting the first core network service to the first entity for the first time, i.e., the first terminal device has sent the first information before, "initiation" can be understood as loading a cached process.

[0129] The aforementioned initial context may include multiple parameters, such as initial security parameters, initial policy parameters, initial transmission parameters, and initial calculation parameters. The term "initial" refers to the first entity. In other words, the first entity acquires the context of the first terminal device for the first time.

[0130] For example, initial security parameters may include at least one of the following: terminal device identification information, key information, or an algorithm associated with authentication or authorization. Initial policy parameters may include at least one of the following: mobility management policy, session policy, or charging policy. Initial transmission parameters may include at least one of the following: transmission path parameters (e.g., IP address, port number, etc.) or routing configuration. Initial computation parameters may include at least one of the following: computing power configuration, model configuration, or dataset configuration. It should be understood that the initial context is not limited to the parameters mentioned above; the initial context may also include other parameters.

[0131] Simultaneously, this first process has a corresponding ID, namely the first ID, which can be the ID assigned by the first entity to the first process. It should be understood that the ID of the first process is different for different first core network services. For example, if the first core network service is session registration service, the first ID is 01; if the first core network service is session establishment service, the first ID is 02; and if the first core network service is session maintenance service, the first ID is 03.

[0132] In this embodiment, the first entity manages the first context based on the first ID. Here, "management" can be understood as caching, maintenance, etc. The term "caching" (store) can be understood as the first context being temporarily loaded into the first entity. The first context is not retained long-term; it is typically deleted after use, thus releasing the cache occupied by the first context. Those skilled in the art will understand that storage is different from caching. When the first entity stores certain information, it means that the information is stored relatively long-term within the first entity or in the first satellite deployed by the first entity.

[0133] The term "maintain" can include at least one of adding, deleting, modifying, or updating. As an example, maintaining the first context may include updating the first context. As another example, maintaining information about the core network services that the first entity can provide may involve creating a new core network service for the first entity or deleting a core network service that the first entity has configured. For example, another entity may configure the first entity to provide new core network services or to provide fewer core network services. As yet another example, maintaining information about the resources used to perform core network services may involve updating the information about the resources used to perform core network services. For example, another entity may reallocate the first entity's software and / or hardware resources. As yet another example, another entity may adjust the first entity's processing parameters (e.g., processing capacity).

[0134] In some possible embodiments, the storage unit for caching the first context may be outside the first entity. For example, the first satellite may include a first entity and a first storage unit. The first storage unit is used to cache the context of the first terminal device. The first entity can obtain the context of the first terminal device from the first storage unit.

[0135] This application does not limit the name of the first entity, which may also be called a user agent (UA), service entity, service function, user agent function, user agent entity, process management unit, or have other names.

[0136] In some possible implementations, the first entity is deployed on a first satellite. For example, the first entity may be deployed in an access network device, core network device, or other device on the first satellite. Optionally, the first entity is deployed on the satellite where the first access network device is located. The first access network device is an access network device that provides services to the first terminal device.

[0137] For example, the first satellite may be a low Earth orbit (LEO) satellite; in other words, the first entity may be deployed on an LEO satellite. This application does not limit the name of the first satellite, which may also be referred to as an aircraft, spacecraft, or other name.

[0138] Furthermore, this application does not limit the first entity to be deployed only on a satellite. In other possible implementations, the first entity is deployed in ground equipment. For example, the first entity may be deployed in a ground-based base station or core network equipment.

[0139] In this embodiment, a first entity deployed on a single satellite can implement core network services. The core network services requested by the terminal device can be implemented through this first entity, avoiding the need for collaborative completion by core network elements on multiple satellites. This reduces the probability of errors caused by frequent user context migrations, thereby improving the quality of services provided by the core network. Furthermore, since the core network services requested by the terminal device are deployed on a single entity, the context managed by this entity is less than the context managed by multiple core network elements in traditional solutions, thus reducing signaling overhead during user context migrations.

[0140] Furthermore, the first entity can initiate a first process based on the first core network and manage the first context based on the ID of the first process. This allows for effective management and maintenance of the context generated for the first core network service requested by the first terminal device. Specifically, if a failure occurs during the execution of the first process, preventing the first entity from continuing, the first entity can migrate the context generated for the first core network service. This migration, based on the ID of the first process, improves the accuracy of the context migration, preventing failures of the first core network service due to migration errors and facilitating its completion.

[0141] Optionally, in some embodiments, the first context includes parameters generated during the execution of the first process by the first entity, and / or parameters generated after the first entity completes the first process.

[0142] Taking the first core network service as a session registration service as an example, during the process of the first entity starting the first process for the session registration service, multiple functions need to be executed. For example, the function sequence of the session registration service may include: context reading function -> authentication / authorization function -> policy generation function -> context writing function. During the execution of the above functions, intermediate parameters will be generated, such as the parameters generated after executing the context reading function, the parameters generated after executing the authentication / authorization function, etc., and these intermediate parameters belong to the first context in this application embodiment.

[0143] Furthermore, after the first entity completes the execution of the aforementioned function, it generates parameters for use by the first terminal device and the first entity, such as the ID of the first terminal device, the policy of the first terminal device, and the key of the first terminal device. The policy of the first terminal device may include its billing policy, service plan, and carrier, while the key may include encryption methods, encryption tools, and encryption algorithms. Therefore, the parameters generated after the first entity completes the first process also belong to the first context in this application embodiment.

[0144] In some possible embodiments, the parameters generated during the execution of the first process by the first entity can be called the first type of context, and the parameters generated after the first entity completes the first process can be called the second type of context, so the first context includes the first type of context and the second type of context.

[0145] In some other possible embodiments, the parameters generated during the execution of the first process by the first entity can be called the intermediate context, and the parameters generated after the first entity completes the first process can be called the completion context, so the first context includes the intermediate context and the completion context.

[0146] It should be understood that the names included in the first context shown in the above two embodiments are merely illustrative examples, and the first context may also include other possible names, without limitation.

[0147] It should be noted that the first context in this application embodiment is not the same as the initial context mentioned in the above embodiments. The initial context can be understood as the parameter information sent by the first terminal device to the first entity, while the first context can be understood as the parameter information generated when the first entity executes the first process.

[0148] In this embodiment, the first entity can manage the parameters generated during the execution of the first process and / or the parameters generated after the first entity completes the first process, thereby improving the reliability of the first entity providing the first core network service to the first terminal device. On the one hand, the first entity managing the parameters generated during the execution of the first process can prevent the first entity from losing intermediate parameters due to failures during the execution of the first process, which is conducive to the completion of the first process and thus conducive to reliable communication with the first terminal device. On the other hand, the first entity managing the parameters generated after the first process is completed can improve the reliability of communication with the first terminal device.

[0149] Optionally, in some embodiments, the communication method 300 further includes performing any of the following operations on the first process: process termination, process restart, process execution, or process release.

[0150] Process termination includes pausing the execution of functions associated with the first process, and caching the preceding process information during termination. Process restart includes pausing the execution of the first process and then resuming the execution of functions associated with it. Process execution includes providing corresponding services to the first terminal device based on the parameters generated after the first process completes execution. Process release includes releasing the ID of the current first process and releasing the intermediate parameters generated during the execution of the first process.

[0151] Figure 4 shows a schematic diagram of process association provided in an embodiment of this application. Referring to Figure 4, it can be seen that there is a bidirectional arrow between process termination and process restart, indicating that a process can be restarted after termination, and a process can also be terminated after restarting. There is also a bidirectional arrow between process termination and process execution, indicating that a process can be executed after termination, and a process can also be terminated after execution.

[0152] The arrow between process termination and process release is a one-way arrow pointing towards process release, indicating that a terminated process can be released, but a released process cannot be terminated. The arrow between process restart, process release, and process execution is also a one-way arrow pointing towards process execution or process release, indicating that a restarted process can be released or executed, but a released or executed process cannot be restarted. The arrow between process execution and process release is also a one-way arrow pointing towards process release, indicating that a executed process can be released, but a released process cannot be executed.

[0153] It should be noted that when the first entity completes the first process, the first context changes compared to before the execution of the first core network service. The changed first context can be called the updated first context. In other words, the parameters included in the first context have changed before and after the first process runs; that is, the parameters have been updated.

[0154] The following section uses the first core network service as an example to illustrate the various operations performed on the first process.

[0155] As described above, the function sequence of the session registration service can include: context read function -> authentication / authorization function -> policy generation function -> context write function. When the first process terminates at the authentication / authorization function, the first entity can cache the context of the first process, which includes the contents of the executed process instructions and data in the relevant registers and stack.

[0156] When the first entity needs to continue executing the first process, it can perform a process restart operation, so that the first entity can continue to execute from the authentication / authorization function until all functions of the session registration service are completed.

[0157] Once the first process finishes execution, the first entity can run the process, providing services to the first terminal device based on the parameters generated after the first process completes. As mentioned above, the parameters generated after the first process completes include the first terminal device's ID, policy, and key. Taking the key as an example, the first entity can encrypt relevant information of the first terminal device based on the encryption method, encryption tool, and encryption algorithm included in the key.

[0158] In some embodiments, the first entity may perform a first process release, that is, the first entity may release the ID of the first process and the parameters generated when executing the first process, such as the intermediate parameters mentioned above, and the parameters generated after the process ends for use by the first terminal device and the first entity.

[0159] In this embodiment, the first entity can perform lifecycle management on the first process according to the current network state, such as performing any operation on the first process, such as process termination, process restart, process running, or process release, thereby improving the flexibility of the first entity in executing the first process and facilitating the first entity's flexible control over the first process.

[0160] When the first entity performs one or more of the above operations during the execution of the first process, optionally, in some embodiments, the communication method 300 further includes: the first entity sending indication information to the first terminal device according to the first ID, the indication information being used to indicate that the first entity has performed any of the following operations: suspending the first process, restarting the first process, running the first process, or releasing the first process. Accordingly, the first terminal device receives the indication information.

[0161] In some embodiments, the term "abort" may be replaced with "suspend". Furthermore, while the first entity is running the first process, the process parameters may be updated; therefore, running the first process here can also be understood as updating the first process.

[0162] In this embodiment of the application, when the first core network service includes a core network service, such as a session registration service with an ID of "01", the first entity can perform any of the above-mentioned operations on the process corresponding to the session registration service, such as terminating the process corresponding to the session registration service. After the first entity terminates the process corresponding to the session registration service, it can send an indication message to the first terminal device based on the ID "01". This indication message is used to instruct the first entity to perform a termination operation on the process with ID "01".

[0163] In cases where the first core network service includes multiple core network services, such as a session registration service and a session establishment service, where the ID of the session registration service is "01" and the ID of the session establishment service is "02", the first entity can perform any of the aforementioned operations on the process corresponding to the session registration service, and / or on the process corresponding to the session establishment service, such as terminating the process corresponding to the session registration service, and / or terminating the process corresponding to the session establishment service. After terminating the process corresponding to the session registration service, the first entity can send an indication message to the first terminal device based on the ID "01", which instructs the first entity to perform a termination operation on the process with ID "01". Alternatively, after terminating the process corresponding to the session establishment service, the first entity can send an indication message to the first terminal device based on the ID "02", which instructs the first entity to perform a termination operation on the process with ID "02". Alternatively, after the first entity terminates the process corresponding to the session registration service and the session establishment service, it can send an instruction message to the first terminal device based on the ID "01" and ID "02". The instruction message is used to instruct the first entity to perform a termination operation for the process with ID "01" and for the process with ID "02".

[0164] In response to the operation indicated by the instruction information, the first terminal device can also perform different actions. For example, when the instruction information indicates to stop the operation, the first terminal device can save the relevant information; when the instruction information indicates to restart the operation, the first terminal device can continue to communicate normally with the first entity; when the instruction information indicates to run the operation, the first terminal device can also communicate normally with the first entity; when the instruction information indicates to release the process, the first terminal device can also release the relevant information.

[0165] It should be noted that the information stored by the first terminal device differs depending on the first core network service and the indication message indicating operation termination. For example, if the first core network service includes session establishment and the indication message indicates session establishment service termination, the information stored by the first terminal device may include the IP address and port number of the pipe used for this session establishment service. As another example, if the first core network service includes session registration and the indication message indicates session registration service termination, the information stored by the first terminal device may include information about successfully registered sessions.

[0166] In this embodiment of the application, after receiving the instruction information from the first entity, the first terminal device can understand the specific operation of the process executed by the first entity for the first core network service. The first terminal device can perform corresponding actions according to the operation indicated by the instruction information. In this way, the first terminal device can perform flexible actions based on the life cycle management of the first process by the first entity, which is conducive to the successful execution of the first process.

[0167] The following will explain the contents of the first information and the contents of the first entity starting the first process.

[0168] Optionally, in some embodiments, the first information includes a second ID and / or a first parameter, wherein the second ID is an ID used for the request process, and the first parameter is used to indicate the type of service function of the first core network service.

[0169] Optionally, in some embodiments, step 340 above includes: initiating a first process based on the first core network service and the second ID.

[0170] In this embodiment, the first information sent by the first terminal device to the first entity may further include a second ID, which is dedicated to the request process; for example, the second ID may be set to 0. The first information may also include a first parameter, which indicates the type of service function of the first core network service, such as session registration service or session establishment service. When the second ID in the first information received by the first entity is 0, and the first core network service is a session registration service, the first entity may start a first process for the session registration service.

[0171] The first piece of information can be in tabular form, as shown in Table 1.

[0172] Table 1

[0173] Optionally, in some embodiments, the first information may further include the number of bits used to send the first information, as shown in Table 2.

[0174] Table 2

[0175] It should be noted that when the first core network service includes multiple core network services, the content included in the first information can be shown as shown in Table 3 or Table 4, without restriction.

[0176] Table 3

[0177] Table 4

[0178] Tables 3 and 4 show two formats of the content included in the first information when the first core network service includes two core network services. Table 3 shows that the second ID "0" is located in the frame header, and the types of the two service functions are arranged sequentially with ID "0" next to each other. This format can also be called the "one-line" format. Table 4 shows that the second ID is located in the frame header, and the types of the two service functions are arranged sequentially with ID "0" next to each other. This format can also be called the "non-one-line" format.

[0179] It should also be noted that when the first terminal device includes multiple terminal devices, the first entity can start the corresponding first process for each of these multiple terminal devices.

[0180] Taking three terminal devices as an example, assuming that these three terminal devices are terminal device 1, terminal device 2, and terminal device 3 respectively, and that the second ID included in the first information sent by these three terminal devices is 0, then when the first entity receives the first information from these three terminal devices, it can start the first process for each terminal device.

[0181] If the first parameters of the first information of these three terminal devices indicate the same type of service function of the first core network service, for example, all of them are session registration services, then the first entity can start a process for the session registration service for these three terminal devices.

[0182] If the first parameters included in the first information of these three terminal devices indicate different service functions of the first core network service, for example, if the first parameters included in the first information sent by terminal device 1 indicate that the service function type of the first core network service is session registration service, the first parameters included in the first information sent by terminal device 2 indicate that the service function type of the first core network service is session establishment service, and the first parameters included in the first information sent by terminal device 3 indicate that the service function type of the first core network service is session release service, then the first entity can start a process for session registration service for terminal device 1, a process for session establishment service for terminal device 2, and a process for session release service for terminal device 3.

[0183] In this embodiment, since the second ID is used as the ID for requesting the process, when the first entity receives the second ID, it can start the first process based on the first core network service and the second ID, thereby improving the efficiency of the first entity starting the first process. Furthermore, the content included in the first information can be standardized. By defining a standardized information format, it is further beneficial to improve the efficiency of the first entity starting the first process.

[0184] After the first entity finishes executing the first process, optionally, in some embodiments, the communication method 300 further includes: the first entity sending second information to the first terminal device, the second information including a first ID and / or second parameters, the second parameters including parameters generated after the first process is completed. Accordingly, the first terminal device receives the second information and communicates with the first entity based on the second information.

[0185] The following description uses the first terminal device to include both one terminal device and multiple terminal devices.

[0186] (1) The first terminal device includes a terminal device

[0187] When the first terminal device includes a terminal device, after the first entity receives the first information from the first terminal device, it can initiate a first process for the first core network service requested by the first information. If the first core network service requested by the terminal device is a session registration service, the ID of the first process can be, for example, "01". The first entity can send the ID "01" of the first process to the first terminal device. Simultaneously, after the first entity completes the execution of the first process, it can send the parameters generated after the first process is completed to the first terminal device, such as the ID of the first terminal device, the policy of the first terminal device, and the key of the first terminal device mentioned above. Therefore, the first terminal device can communicate with the first entity based on the received second information.

[0188] (2) The first terminal device includes multiple terminal devices.

[0189] Taking a first terminal device comprising three terminal devices as an example, assuming these three terminal devices are terminal device 1, terminal device 2, and terminal device 3, after receiving the first information from these three terminal devices, the first entity can initiate a first process for the first core network service requested by the first information. If all three terminal devices are used to request session registration services, the ID of the first process can be, for example, "01", so the first entity can send the ID "01" of the first process to these three terminal devices. Simultaneously, after the first entity completes the execution of the first process, it can send the parameters generated after the first process is completed to the corresponding terminal devices, such as sending the ID, policy, and key of terminal device 1 to terminal device 1; sending the ID, policy, and key of terminal device 2 to terminal device 2; and sending the ID, policy, and key of terminal device 3 to terminal device 3. Therefore, these three terminal devices can communicate with the first entity based on the second information they each receive, ensuring the accuracy of the communication.

[0190] If these three terminal devices are used to request session registration service, session establishment service, and session release service respectively, the IDs of the first process can be, for example, "01", "02", and "03" respectively. Thus, the first entity can send the first process ID "01" to terminal device 1, the first process ID "02" to terminal device 2, and the first process ID "03" to terminal device 3. Simultaneously, after the first entity completes the execution of the first process, it can send the parameters generated after the first process execution to the corresponding terminal devices, such as sending the terminal device 1 ID, terminal device 1 policy, and terminal device 1 key to terminal device 1; sending the terminal device 2 ID, terminal device 2 policy, and terminal device 2 key to terminal device 2; and sending the terminal device 3 ID, terminal device 3 policy, and terminal device 3 key to terminal device 3. Therefore, these three terminal devices can communicate with the first entity based on the second information they receive, ensuring the accuracy of the communication.

[0191] Furthermore, in some embodiments, the second information may also include a third parameter, which is related to the type of service function. For example, when the first core network service includes session establishment service, the third parameter may include session type, such as Ethernet protocol session, Internet Protocol version 4 (IPv4), IPv6, etc.; when the first core network service includes session release service, the third parameter may include release reason, such as link interruption, communication termination, etc.

[0192] The parameters for the interaction between the first entity and the first terminal device can be in tabular form, as shown in Table 5.

[0193] Table 5

[0194] In some possible cases, the first entity may include multiple core network elements, and different core network elements may have different core network service functions. In this case, the communication method 300 may further include: when the first core network service includes multiple core network services, the first entity routes the multiple core network services to the corresponding core network elements according to the first information. The above step 340 includes: multiple core network elements start corresponding sub-processes according to the corresponding core network services, the ID of the sub-process is the first sub-ID, the first process includes multiple sub-processes, and the first ID includes multiple first sub-IDs.

[0195] In this embodiment of the application, assuming that the first core network service includes multiple core network services, after the first entity receives the first information, it can route these multiple core network services to the corresponding core network elements. Each core network element starts a corresponding sub-process, and each of these multiple sub-processes corresponds to a sub-ID. These multiple sub-IDs together form the first ID in this embodiment of the application.

[0196] Figure 5 illustrates a process-based protocol stack according to an embodiment of this application. In Figure 5, a first terminal device includes process 1 and process 2, and a first entity includes core network element A and core network element B. Process 1 of the first terminal device corresponds to core network element A of the first entity, and process 2 of the first terminal device corresponds to core network element B of the first entity. That is, core network element A can provide the first terminal device with the core network service corresponding to process 1, and core network element B can provide the first terminal device with the core network service corresponding to process 2. Therefore, when the first terminal device sends a first information request requesting a service from core network element A or core network element B, the first entity can route the first information to the corresponding core network element, which then executes the corresponding process.

[0197] Assuming core network element A provides a session registration service and core network element B provides a session establishment service, taking the first core network service including both session registration and session establishment services as an example, when the first entity receives the first information, it can route these two core network services to their corresponding core network elements. Specifically, it routes the session registration service to the session registration element (i.e., core network element A) and the session establishment service to the session establishment element (i.e., core network element B). The session registration element starts a sub-process for the session registration service, and the session establishment element starts a sub-process for the session establishment service. Furthermore, the session registration element can assign a sub-ID, such as "01a", to the sub-process for the session registration service, and the session establishment element can assign a sub-ID, such as "01b", to the sub-process for the session establishment service.

[0198] Furthermore, Figure 5 illustrates that the first terminal device and the RAN can communicate via the access network (AN) protocol. Both the RAN and the first entity shown in Figure 5 include Layer 1 (L1), Layer 2, IP, Stream Control Transmission Protocol (SCTP), and Next Generation Application Protocol (NGAP). L1 is the physical layer, L2 is the data link layer, and IP, SCTP, and NGAP are three different protocols. IP is the most basic communication protocol used in network operations. SCTP is used for message transmission, with each message having an independent identifier and allowing selective retransmission. NGAP is used to transmit signaling and control information in the core network. The first entity also includes a service-based interface (SBI), through which information can be transmitted.

[0199] In this embodiment of the application, when the first entity includes multiple core network elements, when the first core network service received by the first entity includes multiple core network services, the first entity can route the multiple core network services to the corresponding core network elements respectively, and the corresponding core network elements can start the corresponding sub-processes. In this process, the multiple core network elements can start the corresponding sub-processes at the same time, thereby reducing the time for the first entity to complete the first core network service requested by the first terminal device, thereby improving the efficiency of the first entity in completing the first core network service requested by the first terminal device.

[0200] As shown in Figure 6, optionally, in some embodiments, the communication method 300 further includes steps 360 to 390.

[0201] 360. A third message is sent to the second entity, which requests the migration of a second context. The second context is a partial context of the first context. The function of the second entity includes providing first core network services to the first terminal device. Accordingly, the second entity receives the third message.

[0202] The function of the second entity, including the provision of the first core network service by the second first terminal device, can be understood as the first core network service being implemented by the second entity. The term "implementation" can be understood as the second entity completing the implementation of the first core network service, or as the second entity fully executing the function sequence of the first core network service.

[0203] It should be understood that although the above text indicates that the function of the first entity includes providing the first core service for the first terminal device, it does not mean that the function of the second entity is completely consistent with the function of the first entity.

[0204] For example, the first entity may provide first core network services to a first terminal device and second core network services to a second terminal device, in addition to providing first core network services to the first terminal device; the second entity may provide third core network services to a third terminal device in addition to providing first core network services to the first terminal device; and the second and third core network services are different. In this case, the functions of the second entity are not completely consistent with those of the first entity, or in other words, the functions of the second entity are partially consistent with those of the first entity.

[0205] This application does not limit the name of the third information, which may also be called request information, request, service request or other names.

[0206] 370. Send feedback information to the first entity, which indicates whether the first entity can or cannot migrate the second context to the second entity.

[0207] This application does not limit the name of the feedback information, which may also be called a response message or other specific names.

[0208] 380, Receive feedback information from the second entity.

[0209] 390. Based on the feedback information, migrate to the second entity or do not migrate the second context.

[0210] Steps 360, 380, and 390 can be executed by the first entity, by a module of the first entity (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first entity. For ease of description, the first entity will be used as an example throughout this document.

[0211] Step 370 can be performed by the second entity. It can also be performed by a module of the second entity (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that implements all or part of the functions of the second entity. For ease of description, the second entity will be used as the example below.

[0212] In this context, the term "migration" can be replaced with "switching." "Migration" can be understood as follows: a first entity (which can be called the source entity) is not associated with a first terminal device; a second entity (which can be called the target entity) is associated with the first terminal device. The second entity can be a newly created entity or an existing entity. After being associated with the first terminal device, the second entity can perform functions similar to those of the first entity previously associated with the first terminal device. For example, it can implement first core network services.

[0213] In this embodiment of the application, under certain possible circumstances, when the first entity is unable or cannot continue to provide the first core network service to the first terminal device, the first entity may send third information to the second entity to request the migration of the second context. Generally, the context migration action occurs before the first process has finished executing. Therefore, the requested second context may be a portion of the first context, such as intermediate parameters generated by the first entity during the execution of the first process.

[0214] After the second entity receives the third information, if the second entity has a large storage space and can accept the second context sent by the first entity, or if the second entity currently stores less content and has remaining storage space to store the second context, such as if the second entity currently executes fewer processes corresponding to other core network services, then the second entity can send feedback information to the first entity to instruct the first entity to migrate the second context to the second entity. After the first entity receives the feedback information, it can migrate the second context to the second entity.

[0215] After receiving the third information, if the second entity has limited storage space and cannot accept the second context sent by the first entity, or if the second entity currently stores a large amount of content and has no remaining storage space to store the second context (e.g., the second entity is currently executing many other core network services corresponding to processes), then the second entity can send feedback information to the first entity instructing the first entity not to migrate the second context to the second entity. Upon receiving this feedback information, the first entity will not migrate the second context to the second entity. In this case, the first entity can continue to send the third information to other entities (such as the third entity) so that the first entity can successfully migrate the second context to other entities.

[0216] The second entity in this embodiment is similar to the first entity. The second entity may also be referred to as a user agent, service entity, service function, user agent function, user agent entity, or other names. The second entity and the first entity may be deployed on the same satellite or on different satellites; there is no limitation on this.

[0217] In this embodiment, the first entity can send third information to the second entity to request the migration of the second context. The second entity can send feedback information to the first entity based on its own storage space. This feedback information is used to indicate whether the first entity can or cannot migrate the second context to the second entity. The first entity migrates or does not migrate the second context based on the feedback information. In this way, when the first entity is unable or cannot continue to provide the first core network service to the first terminal device, and when the first entity successfully migrates the second context, the second entity can continue to provide the first core network service to the first terminal device, thereby improving the continuity and reliability of the first core network service.

[0218] Furthermore, in some possible implementations, the second entity may also send another feedback message to the first entity, which indicates that the second context migration is complete. Optionally, this other feedback message is used to instruct the second entity to provide the first core network service to the first terminal device. Optionally, this other feedback message is used to instruct the first entity not to provide the first core network service to the first terminal device.

[0219] Optionally, the first entity may also send the other feedback information to the first terminal device.

[0220] In the above embodiments, when the first entity migrates the second context to the second entity, the communication method 300 may further include: the second entity sending fourth information to the first entity, the fourth information including information allocated by the second entity for the process of the first core network service corresponding to the second context. Accordingly, the first entity receives the fourth information from the second entity and sends the fourth information to the first terminal device, thereby the first terminal device receives the fourth information and communicates with the second entity based on the fourth information.

[0221] Optionally, in some embodiments, the fourth information includes at least one of the following: a third ID, an IP address, and a port number.

[0222] In this embodiment, after the first entity migrates the second context to the second entity, the second entity, upon receiving the second context, can manage it, start a corresponding process for the first core network service corresponding to the second context, and assign corresponding fourth information, such as a third ID, IP address, and port number, to the process. This fourth information is then sent to the first entity, which in turn sends it to the first terminal device. Thus, the first terminal device can communicate with the second entity based on the fourth information, improving the accuracy and reliability of communication between the first terminal device and the second entity. Specifically, generally, the context migration occurs before the first process has finished executing. Therefore, after the first entity migrates the second context to the second entity, the second entity can start a corresponding process for the first core network service corresponding to the second context. The second entity can execute the corresponding process based on the fourth information and send this fourth information to the first terminal device, further improving the accuracy and reliability of communication between the first terminal device and the second entity.

[0223] The third ID assigned by the second entity to the process initiated for the first core network service may be the same as or different from the first ID mentioned above, and there is no restriction.

[0224] For example, suppose the first core network service includes a session establishment service, and the first ID assigned by the first entity to the session establishment service is "01". When the first context of the first process started for the session establishment service is transferred to the second entity, the third ID assigned by the second entity to the session establishment service may be "01" or "02".

[0225] Furthermore, the IP address and port number assigned to the process launched by the second entity for the first core network service may be the same as or different from the IP address and port number assigned to the first process launched by the first entity for the first core network service, and there is no restriction.

[0226] In some embodiments, after the second entity initiates a corresponding process for the first core network service and allocates the corresponding fourth information to the process, it can also send the fourth information directly to the first terminal device. In other words, the fourth information can be sent directly to the first terminal device by the second entity without being forwarded by the first entity.

[0227] It should be noted that the values ​​shown in the above embodiments are merely illustrative examples and may be other values, and should not be construed as limiting this application.

[0228] It should be understood that the sequence number of each process does not imply the order of execution. 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 embodiments of this application.

[0229] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0230] It should also be understood that in some of the above embodiments, the examples are mainly based on devices in existing network architectures (such as network devices, terminal devices, etc.). It should be understood that the specific form of the device is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0231] It is understood that, in the above-described method embodiments, the methods and operations implemented by devices (such as network devices (i.e., the first entity) or terminal devices) can also be implemented by components of the devices (such as chips or circuits).

[0232] The communication method provided in the embodiments of this application has been described in detail above with reference to Figures 3 to 6. The above communication method is mainly described from the perspective of interaction between terminal devices and network devices. It is understood that, in order to achieve the above functions, the terminal devices and network devices include corresponding hardware structures and / or software modules for performing each function.

[0233] Those skilled in the art will recognize that, based on the units and algorithm steps described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0234] The communication device provided in this application will be described in detail below with reference to Figures 7 and 8. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for content not described in detail, please refer to the method embodiment above. For the sake of brevity, some content will not be repeated.

[0235] Figure 7 illustrates a possible exemplary block diagram of the communication device involved in the embodiments of this application. As shown in Figure 7, the communication device 700 may include modules or units for implementing the method embodiments described above. In one possible implementation, the communication device 700 includes a communication unit 710. Optionally, the communication device 700 may further include a processing unit 720 for processing relevant information. Optionally, the communication device 700 may further include a storage unit 730 for storing device program code and / or data.

[0236] The communication device 700 can be a network-side device in the above embodiments, such as a network or a communication module in a network, or a circuit or chip in a network responsible for communication functions. The device 700 can be used to perform the actions performed by the first entity in the above method 300 embodiments.

[0237] When the communication device 700 is used to execute the actions performed by the first entity in the above-described method 300 embodiment, the communication unit 710 is used to: receive first information from the first terminal device, the first information being used to request a first core network service, the function of the first entity including providing the first core network service to the first terminal device. The processing unit 720 is used to: initiate a first process according to the first core network service, the identifier ID of the first process being a first ID; and manage a first context according to the first ID, the first context being the context generated by the first entity when executing the first process.

[0238] For a more detailed description of the communication unit 710 and the processing unit 720, please refer to the relevant descriptions in the embodiments of the method 300 above, which will not be repeated here.

[0239] The communication device 700 can be a terminal-side device as described in the above embodiments, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal responsible for communication functions. The device 700 can be used to perform the actions performed by the terminal device in the above method 300 embodiments.

[0240] When the communication device 700 performs the actions performed by the terminal device in the above-described method 300 embodiment, the processing unit 720 is configured to: generate first information, which is used to request a first core network service. The communication unit 710 is configured to: send the first information to a first entity, the first entity's function including providing the first core network service to the first terminal device.

[0241] For a more detailed description of the communication unit 710 and the processing unit 720, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.

[0242] It is understood that the division of units in the above-described device is merely a logical functional division. Each function can correspond to a functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into a single physical entity, or they can be distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0243] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units, one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0244] In one example, storage unit 730 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0245] Referring to Figure 8, which is a schematic diagram of another communication device 800 provided in an embodiment of this application, the device 800 includes a processor 810 coupled to a memory 820. The memory 820 is used to store computer programs or instructions and / or data. The processor 810 is used to execute the computer programs or instructions stored in the memory 820, or to read the data stored in the memory 820, to perform the methods in the embodiments described above.

[0246] Optionally, there may be one or more processors 810.

[0247] Optionally, the memory 820 may be one or more.

[0248] Alternatively, the memory 820 can be integrated with the processor 810, or it can be set separately.

[0249] Optionally, as shown in FIG8, the device 800 further includes a transceiver 830 for receiving and / or transmitting signals. For example, the processor 810 is used to control the transceiver 830 to receive and / or transmit signals.

[0250] As an example, processor 810 may have the functions of processing unit 720 shown in FIG. 7, memory 820 may have the functions of storage unit 730 shown in FIG. 7, and transceiver 830 may have the functions of communication unit 710 shown in FIG. 7.

[0251] As one option, the device 800 is used to implement the operations performed by the communication device in the various method embodiments described above.

[0252] For example, processor 810 is used to execute computer programs or instructions stored in memory 820 to implement the relevant operations of terminal devices or network devices in the various method embodiments described above.

[0253] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit, or it can be other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0254] The processor may include communication and processing circuitry. This communication and processing circuitry may include one or more hardware components that provide a physical structure that performs various processes related to wireless communication (e.g., signal reception and / or signal transmission). The communication and processing circuitry may include one or more transmit / receive chains. For example, the processor may receive higher-layer signaling (such as RRC signaling) or physical-layer signaling (such as downlink control information, DCI) transmitted by a base station. The functions implemented by the communication and processing circuitry may also be processed on a computer-readable medium.

[0255] The processor can also process the received signaling, such as through demodulation and decoding, to obtain the carried configuration / indication information, such as the aperiodic CLI measurement reporting configuration and the DCI that triggers aperiodic CLI measurement reporting carried in higher-layer signaling. The processor can perform measurements according to the aperiodic CLI measurement reporting configuration, obtain the measurement results, and generate a corresponding measurement report. The processor can also generate a PUCCH carrying the measurement report and send it to the base station via the air interface.

[0256] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), EPROM, electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes various forms such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0257] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0258] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0259] Referring to Figure 9, Figure 9 is a schematic diagram of a chip system 900 provided in this embodiment of the application. The chip system 900 (or may also be called a processing system) includes logic circuitry 910 and an input / output interface 920.

[0260] The logic circuit 910 can be a processing circuit in the chip system 900. The logic circuit 910 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 900 to implement the methods and functions of the embodiments of this application. The input / output interface 920 can be an input / output circuit in the chip system 900, outputting processed information from the chip system 900, or inputting data or signaling information to be processed into the chip system 900 for processing.

[0261] Optionally, the logic circuit 910 may be implemented by one or more processors, including the one or more processors or the processing portion of the one or more processors.

[0262] Optionally, the input / output interface 920 may include transceiver circuitry, a transceiver, input / output circuitry, or a communication interface.

[0263] As one approach, the chip system 900 is used to implement the operations performed by the communication device (such as a terminal device, or the first entity) in the various method embodiments described above.

[0264] For example, logic circuit 910 is used to implement processing-related operations performed by a communication device (such as a terminal device, or the first entity) in the above method embodiments; input / output interface 920 is used to implement sending and / or receiving-related operations performed by a communication device (such as a terminal device, or the first entity) in the above method embodiments.

[0265] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a communication device (such as a terminal device or a first entity) in the above-described method embodiments.

[0266] For example, when the computer program is executed by a computer, it enables the computer to implement the methods performed by the communication device (such as a terminal device, or the first entity) in the various embodiments of the above methods.

[0267] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods described above, performed by a communication device (such as a terminal device or a first entity).

[0268] This application also provides a communication system, which includes the terminal device and the first entity described in the above embodiments.

[0269] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0270] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0271] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. 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 integrates one or more available media. The available medium can be magnetic media (e.g., floppy disk, hard disk, magnetic tape), optical media (e.g., digital video disc (DVD)), or semiconductor media (e.g., solid-state disk (SSD)). For example, the aforementioned available media include, but are not limited to, various media capable of storing program code such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, The method is applied to a first entity, which is deployed on a first satellite, and the method includes: The first entity receives first information from a first terminal device, the first information being used to request a first core network service, and the function of the first entity includes providing the first core network service to the first terminal device. The first process is started according to the first core network service, and the identifier ID of the first process is the first ID; The first context is managed based on the first ID, and the first context is the context generated by the first entity when executing the first process.

2. The method according to claim 1, characterized in that, The first context includes parameters generated during the execution of the first process by the first entity, and / or parameters generated after the first entity completes the first process.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Perform any of the following operations on the first process: Process termination, process restart, process execution, process release.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Based on the first ID, an indication message is sent to the first terminal device, the indication message being used to instruct the first entity to perform any of the following operations: Terminate the first process, restart the first process, run the first process, or release the first process.

5. The method according to any one of claims 1 to 4, characterized in that, The first information includes a second ID and / or a first parameter, wherein the second ID is an ID used for the request process, and the first parameter is used to indicate the type of service function of the first core network service.

6. The method according to claim 5, characterized in that, The step of initiating the first process based on the first core network service includes: The first process is started based on the first core network service and the second ID.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Send second information to the first terminal device. The second information includes the first ID and / or a second parameter, the second parameter including parameters generated after the first process is completed.

8. The method according to any one of claims 1 to 7, characterized in that, The first entity includes multiple core network elements, each with different core network service functions. The method further includes: When the first core network service includes multiple core network services, the multiple core network services are routed to the corresponding core network elements according to the first information; The step of initiating the first process based on the first core network service includes: Multiple core network elements initiate corresponding sub-processes according to their respective core network services. The ID of each sub-process is a first sub-ID. The first process includes multiple sub-processes, and the first ID includes multiple first sub-IDs.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Send a third message to the second entity, the third message being used to request the migration of a second context, the second context being a partial context of the first context, the function of the second entity including providing the first core network service to the first terminal device; Receive feedback information from the second entity, the feedback information being used to indicate whether the first entity can or cannot migrate the second context to the second entity; Based on the feedback information, the second context may be migrated to the second entity or not.

10. The method according to claim 9, characterized in that, The method further includes: In the case where the first entity migrates the second context to the second entity, fourth information is received from the second entity, the fourth information including information allocated by the second entity for the process of the first core network service corresponding to the second context; The fourth information is sent to the first terminal device.

11. The method according to claim 10, characterized in that, The fourth information includes at least one of the following: Third ID, Internet Protocol IP address, port number.

12. The method according to any one of claims 1 to 11, characterized in that, The first core network service includes at least one of the following: Session registration service, session establishment service, session maintenance service, switching service, and location service.

13. A communication method, characterized in that, The method is applied to a first terminal device, and the method includes: Generate first information, which is used to request the first core network service; The first information is sent to a first entity, the first entity having the function of providing a first core network service to the first terminal device.

14. The method according to claim 13, characterized in that, The method further includes: Receive indication information from the first entity, the indication information being used to instruct the first entity to perform any of the following operations: Terminate the first process, restart the first process, run the first process, or release the first process.

15. The method according to claim 13 or 14, characterized in that, The first information includes a second ID and / or a first parameter, wherein the second ID is an ID used for the requesting process, and the first parameter is used to indicate the first core network service requested.

16. The method according to any one of claims 13 to 15, characterized in that, The method further includes: Receive second information from the first entity, the second information including a first ID and / or a second parameter, the second parameter including parameters generated after the first process is executed; Communicate with the first entity based on the second information.

17. The method according to any one of claims 13 to 16, characterized in that, The method further includes: Receive fourth information from the first entity, the fourth information including information allocated by the second entity for the process of the first core network service corresponding to the second context, the second entity being the target entity to which the first entity migrates the function of the first core network service; Communicate with the second entity based on the fourth information.

18. The method according to claim 17, characterized in that, The fourth information includes at least one of the following: Third ID, Internet Protocol IP address, port number.

19. The method according to any one of claims 13 to 18, characterized in that, The first core network service includes at least one of the following: Session registration service, session establishment service, session maintenance service, switching service, and location service.

20. A communication device, characterized in that, Includes modules or units for performing the method as described in any one of claims 1 to 12 or 13 to 19.

21. A communication device, characterized in that, Includes a transceiver for executing a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1 to 12 or 13 to 19.

22. The apparatus according to claim 21, characterized in that, The device further includes a memory for storing the computer program or the instructions.

23. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a computer, implement the method as described in any one of claims 1 to 12 or 13 to 19.

24. A computer program product, characterized in that, When the computer reads and executes the computer program product, it causes the computer to perform the method as described in any one of claims 1 to 12 or 13 to 19.

Images