Communication method and apparatus

Abstract

A communication method and apparatus, wherein a satellite network is involved. The method comprises: receiving first information from a first terminal device, wherein a function of a first entity comprises providing a first core network service for the first terminal device, the first information is used for requesting the first core network service, and the first core network service is implemented by the first entity; and sending second information to the first terminal device, wherein the second information is used for indicating an execution result of the first core network service. An entity deployed on a satellite can implement a core network service, such that a communication delay caused by the transmission of user context can be reduced, and the transmission of a user context on which the core network service is based can be prevented from errors, thereby improving the quality of services provided by a core network. In addition, the entity is associated with a terminal device. The entity can provide the core network service for the exclusive terminal device.

Description

Communication method and apparatus

[0001] This application claims priority to the Chinese Patent Application No. 202410437915.2, filed on April 11, 2024, and entitled "Communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to satellite networks, and more particularly, to a communication method and apparatus. BACKGROUND

[0003] With the development of information technology, there are more urgent requirements for the efficiency, mobility and diversity of communication, etc. In some important fields, such as space communication, aviation communication, marine communication, etc., non-terrestrial networks (NTN) such as satellite communication play an irreplaceable role. In a satellite communication system, in order to reduce the time delay caused by the round trip of core network signaling between satellite and ground, the core network element can be deployed on the satellite platform, thereby providing core network services for users.

[0004] How to improve the quality of services provided by the core network is a problem to be solved. SUMMARY

[0005] The present application provides a communication method and apparatus, which can improve the quality of services provided by the core network.

[0006] In a first aspect, a communication method is provided. The execution subject of the method provided in the first aspect can be a first entity. In the absence of special description, the first entity in the present application can refer to the first entity itself (for example, an access network device or other device), or a component (for example, a processor, a chip, or a chip system, etc.) in the first entity, or a logic module or software capable of realizing all or part of the functions of the first entity. For ease of description, the first entity is described below as an example.

[0007] Optionally, the first entity is deployed on a first satellite.

[0008] The method comprises: receiving first information from a first terminal device, the functions of the first entity comprising providing a first core network service for the first terminal device, the first information being used to request the first core network service, wherein the first core network service is implemented by the first entity; and sending second information to the first terminal device, the second information being used to indicate an execution result of the first core network service.

[0009] By the above scheme, the entity deployed on the satellite can implement the core network service. On one hand, considering the limited payload capacity of the satellite, the deployment complexity of the on-board core network is reduced by deploying the entity instead of deploying the core network element. On the other hand, the core network service requested by the terminal device can be implemented by the entity, avoiding the cooperation of the core network elements on multiple satellites to complete, thereby avoiding the frequent migration of the user context. The above scheme can not only reduce the communication delay caused by the transmission of the user context, but also avoid errors in the transmission process of the user context on which the core network service is based, thereby improving the quality of the service provided by the core network. In addition, the entity is associated with the terminal device. The entity can provide the core network service for the dedicated terminal device. Compared with the entity providing the core network service for any terminal device, the entity in the above scheme can reduce the delay of providing services for the terminal device because the number of terminal devices associated with the entity in the above scheme is limited. One reason is that the number of requests of the terminal devices processed by the entity in the above scheme is small. In this way, in the case that a terminal device requests a core network service, the entity can immediately provide the core network service for the terminal device. Alternatively, the entity can provide the core network service for the terminal device after processing a small number of requests of other terminal devices.

[0010] In some implementations, the first entity is configured to store the context of the first terminal device.

[0011] By the above scheme, the first entity can store the context of the terminal device. Compared with the scheme of storing the context of the terminal device in other devices, the above scheme can reduce the delay of the first entity obtaining the context of the terminal device, thereby improving the efficiency of executing the core network service. Those skilled in the art can understand that, since the first entity only provides the core network service for the terminal device associated therewith, the first entity can store the context of the terminal device associated therewith in the limited storage space on the satellite.

[0012] In some implementations, the first entity is configured to execute the first core network service according to the context of the first terminal device.

[0013] In some implementations, the first entity is capable of performing at least one of the following operations: maintaining the context of the first terminal device; implementing at least one core network service, the at least one core network service including the first core network service; or scheduling resources for executing the first core network service.

[0014] By the above scheme, the first entity can maintain the context of the terminal device, implement the core network service, or schedule resources for implementing the core network service. The above scheme defines some functions possessed by the first entity, the first entity with the function of maintaining the context of the terminal device can obtain the latest context locally, thereby correctly and efficiently implementing the core network service. The first entity with the function of scheduling resources can quickly schedule resources to execute the core network service, thereby improving the speed of executing the core network service.

[0015] In some implementations, the method further includes receiving third information from a second entity, the third information being used for maintaining at least one of the context of the first terminal device, information of a location of the first entity, information of core network services that the first entity is capable of providing, or information of resources used for executing the core network services.

[0016] By the above scheme, the third information can maintain the context of the first terminal device, the information of the location of the first entity, the information of the core network services that the first entity is capable of providing, or the information of the resources used for executing the core network services. In this way, the second entity can maintain the related functions of the first entity through the third information, thereby enabling the first entity to provide more suitable core network services.

[0017] In some implementations, the third information is used for maintaining a state of the first entity, the state of the first entity including at least one of: a first state, the first entity in the first state being capable of providing all core network services configured by the second entity; a second state, the first entity in the second state not storing the context of the first terminal device; a third state, the first entity in the third state not providing the core network services configured by the second entity; or a fourth state, the first entity in the fourth state being capable of providing part of the core network services configured by the second entity.

[0018] By the above scheme, the third information can be used for maintaining the state of the first entity, thereby balancing the quality of the core network services and the resource overhead. For example, the first entity in the first state is capable of providing all of the configured core network services; the first entity in the first state is capable of improving the core network services of higher quality. For another example, the first entity in the fourth state is more capable of saving the resource overhead than the first entity in the first state. For another example, the first entity in the third state is more capable of saving the resource overhead than the first entity in the fourth state. For another example, the first entity in the second state is more capable of saving the resource overhead than the first entity in the third state. In the case that the first entity has multiple states, the second entity can have multiple choices to balance the quality of the core network services and the resource overhead.

[0019] In some implementations, the second entity is deployed on the first satellite, and / or the second entity is a core network network element.

[0020] Through the above scheme, the second entity can be deployed on the satellite where the first entity is located, thereby managing the first entity more quickly and improving the continuous service capability of the first entity.

[0021] In some implementations, the method further includes sending, to the second entity, fourth information used to request migration of a function of providing the first core network service for the first terminal device.

[0022] Through the above scheme, the first entity can request migration of a function of providing a core network service for a terminal device associated with the first entity, so that a new entity can continue to provide the core network service for the terminal device, thereby improving the continuity of the core network service.

[0023] In some implementations, the method further includes sending, to the second entity, fifth information used to indicate context of the first terminal device and / or entity requirement information.

[0024] In some implementations, the method further includes receiving, from the second entity, sixth information used to indicate a condition of triggering migration.

[0025] Through the above scheme, the second entity can configure a condition of triggering migration through the sixth information, so that the first entity can migrate at an appropriate time, thereby improving the continuity of the core network service.

[0026] In some implementations, the method further includes receiving, from the second entity, seventh information used to indicate that the function of the first entity includes providing the first core network service for N terminal devices, N being a positive integer, and the N terminal devices including the first terminal device.

[0027] Through the above scheme, the first entity can be associated with one or more terminal devices. In the case where the first entity is associated with multiple terminal devices, the first entity can provide core network services for different terminal devices. In this way, one entity can provide core network services for multiple terminal devices, and the overhead of deploying entities can be reduced.

[0028] In a second aspect, a communication method is provided. The execution subject of the method provided in the second aspect can be a first terminal device. In the absence of special description, the first terminal device in the present application can refer to the first terminal device itself, a component (for example, a processor, a chip, or a chip system, etc.) in the first terminal device, or a logic module or software that can realize all or part of the function of the first terminal device. For ease of description, the first terminal device is taken as an example in the following description.

[0029] The method comprises: sending first information to a first entity, a function of the first entity comprising providing a first terminal device with a first core network service, the first entity being deployed on a first satellite, the first information being used for requesting the first core network service, the first core network service being implemented by the first entity; and receiving second information from the first entity, the second information being used for indicating an execution result of the first core network service.

[0030] In some implementations, the method further comprises: receiving eighth information from a second entity, the eighth information being used for indicating that the first entity is used for providing the first terminal device with the first core network service.

[0031] Through the above scheme, the eighth information can inform the first terminal device that the first entity provides the first terminal device with the core network service, so that the first terminal device can request the first entity to provide the corresponding core network service, thereby reducing the time for the first terminal device to find a suitable entity to provide the corresponding core network service and reducing the latency of requesting the core network service.

[0032] In some implementations, the method further comprises: sending ninth information to a second entity, the ninth information being used for requesting an entity used for providing the first core network service to be associated with the first terminal device.

[0033] Through the above scheme, the first terminal device can request the entity used for providing the core network service to be associated, so that the receiving end can perform corresponding operations based on the request.

[0034] In some implementations, the method further comprises: receiving tenth information from the second entity, the tenth information being used for indicating that a third entity is used for providing a second core network service to the first terminal device, the first core network service being different from the second core network service.

[0035] Through the above scheme, the first terminal device can associate the third entity, so that the third entity can also provide the core network service for the first terminal device, thereby further improving the quality of the service provided by the core network. In the case where the first terminal device associates multiple entities used for providing the core network service, different entities can provide different core network services. In this way, a specific entity can provide a specific core network service. On the one hand, an entity can only provide a part of the core network service, thereby reducing the deployment cost of the entity. On the other hand, an entity providing a specific core network service for a specific terminal device can increase the quality of the provided core network service.

[0036] In some implementations, the method further comprises: sending eleventh information to a second entity, the eleventh information being used for requesting the first terminal device to further associate an entity used for providing the second core network service.

[0037] Through the foregoing scheme, the first terminal device can request an entity associated with providing another core network service for the first terminal device, so that the receiving end can perform corresponding operations based on the request.

[0038] In some implementations, the second entity is deployed on the first satellite, and / or the second entity is a core network element.

[0039] The beneficial effects of some implementations in the second aspect can refer to the beneficial effects of some implementations in the first aspect.

[0040] In a third aspect, a communication method is provided. The execution subject of the method provided in the third aspect can be a second entity. In the absence of special description, the second entity in the present application can refer to the second entity (for example, a core network element, an access network device, or other devices) itself, a component (for example, a processor, a chip, or a chip system) in the second entity, or a logic module or software capable of realizing all or part of the functions of the second entity. For ease of description, the second entity is taken as an example in the following description.

[0041] Optionally, the second entity is deployed on the first satellite, and / or the second entity is a core network element.

[0042] The method comprises: determining a first entity, the first entity being deployed on the first satellite, and the functions of the first entity including providing a first core network service for a first terminal device, wherein the first core network service is implemented by the first entity; and sending eighth information to the first terminal device, the eighth information being used to indicate that the first entity is used to provide the first core network service for the first terminal device.

[0043] Through the foregoing scheme, the second entity can associate the first terminal device with the first entity, so that the first entity can provide a core network service for the first terminal device, thereby improving the quality of the service provided by the core network.

[0044] In some implementations, the method further comprises: receiving ninth information from the first terminal device, the ninth information being used to request to associate an entity used to provide the first core network service with the first terminal device.

[0045] In some implementations, the first entity can perform at least one of the following operations: maintaining a context of the first terminal device; implementing at least one core network service, the at least one core network service including the first core network service; or scheduling a resource used to execute the first core network service.

[0046] In some implementations, the method further includes sending, to the first entity, third information, the third information being used for maintaining at least one of a context of the first terminal device, information of a location of the first entity, information of core network services that the first entity is capable of providing, or information of resources used for performing core network services.

[0047] In some implementations, the third information is used for maintaining a state of the first entity, the state of the first entity including at least one of a first state in which the first entity is capable of providing all core network services configured by the second entity, a second state in which the first entity does not store the context of the first terminal device, a third state in which the first entity does not provide core network services configured by the second entity, or a fourth state in which the first entity is capable of providing part of core network services configured by the second entity.

[0048] In some implementations, the method further includes sending, to the first entity, seventh information, the seventh information being used for indicating that a function of the first entity includes providing the first core network service for N terminal devices, N being a positive integer, the N terminal devices including the first terminal device.

[0049] In some implementations, the method further includes sending, to the second terminal device, twelfth information, the twelfth information being used for indicating that the first entity is used for providing the first core network service for the second terminal device.

[0050] Through the above scheme, the twelfth information can inform the second terminal device that the first entity provides core network services for the second terminal device, so that the second terminal device can request the first entity to provide corresponding core network services, thereby reducing the time for the second terminal device to find a suitable entity to provide corresponding core network services, and reducing the latency of requesting core network services.

[0051] In some implementations, the method further includes sending, to the first terminal device, tenth information, the tenth information being used for indicating that a third entity is used for providing a second core network service for the first terminal device, the first core network service being different from the second core network service.

[0052] In some implementations, the method further includes receiving, from the first terminal device, eleventh information, the eleventh information being used for requesting that the first terminal device further associates with an entity used for providing the second core network service.

[0053] In some implementations, the method further includes receiving, from the first entity, fourth information, the fourth information being used for requesting to migrate a function of providing the first core network service for the first terminal device.

[0054] In some implementations, the method further includes receiving fifth information from the first entity, the fifth information being used to indicate the context of the first terminal device and / or entity requirement information.

[0055] In some implementations, the method further includes determining a fourth entity, the fourth entity being deployed on the second satellite, and a function of the fourth entity including providing the first core network service for the first terminal device.

[0056] In some implementations, the method further includes sending sixth information to the first entity, the sixth information being used to indicate a condition triggering the migration.

[0057] The beneficial effects of some implementations of the third aspect can be referred to the beneficial effects of some implementations of the first aspect or the second aspect.

[0058] In the fourth aspect, a communication apparatus is provided, including processing circuitry (or processor) and input and output interface (also referred to as interface circuitry), the input and output interface being configured to input and / or output signals, and the processing circuitry being configured to perform the first aspect and any possible implementation of the first aspect, or the processing circuitry being configured to perform the second aspect and any possible implementation of the second aspect, or the processing circuitry being configured to perform the third aspect and any possible implementation of the third aspect.

[0059] In some implementations, the processing circuitry is configured to communicate with other apparatuses via the interface circuitry, and perform the first aspect and any possible implementation of the first aspect, or the second aspect and any possible implementation of the second aspect, or the third aspect and any possible implementation of the third aspect.

[0060] In the fifth aspect, a communication apparatus is provided. The communication apparatus can include units, modules or means for performing functions of the communication apparatus.

[0061] In some implementations, the communication apparatus can include modules, units or means for performing the methods / operations / steps / actions described in the first aspect and any possible implementation of the first aspect, which can be hardware circuit, software or a combination of hardware circuit and software.

[0062] In some possible implementation manners, the apparatus includes a transceiver and a processing unit. The transceiver is configured to receive first information from a first terminal device, the first entity is configured to provide a first core network service for the first terminal device, and the first information is used to request the first core network service, wherein the first core network service is implemented by the first entity. The transceiver is further configured to send second information to the first terminal device, and the second information is used to indicate an execution result of the first core network service.

[0063] In some implementation manners, the first entity is configured to store a context of the first terminal device.

[0064] In some implementation manners, the first entity is configured to execute the first core network service according to the context of the first terminal device.

[0065] In some implementation manners, the first entity is capable of performing at least one of the following operations: maintaining the context of the first terminal device; implementing at least one core network service, the at least one core network service including the first core network service; or scheduling a resource used to execute the first core network service.

[0066] In some implementation manners, the transceiver is further configured to receive third information from a second entity, the third information being used to maintain at least one of the following: the context of the first terminal device, information about a location of the first entity, information about core network services that the first entity is capable of providing, or information about a resource used to execute a core network service.

[0067] In some implementation manners, the third information is used to maintain a state of the first entity, and the state of the first entity includes at least one of the following: a first state, the first entity in the first state being capable of providing all core network services configured by the second entity; a second state, the first entity in the second state not storing the context of the first terminal device; a third state, the first entity in the third state not providing core network services configured by the second entity; or a fourth state, the first entity in the fourth state being capable of providing part of core network services configured by the second entity.

[0068] In some implementation manners, the second entity is deployed on the first satellite, and / or the second entity is a core network network element.

[0069] In some implementation manners, the transceiver is further configured to send fourth information to the second entity, the fourth information being used to request migration of a function of providing the first core network service for the first terminal device.

[0070] In some implementation manners, the transceiver is further configured to send fifth information to the second entity, the fifth information being used to indicate the context of the first terminal device and / or entity requirement information.

[0071] In some implementations, the transceiving unit is further configured to receive sixth information from the second entity, the sixth information being used to indicate a condition triggering the migration.

[0072] In some implementations, the transceiving unit is further configured to receive seventh information from the second entity, the seventh information being used to indicate that the function of the first entity comprises providing the first core network service for N terminal devices, N being a positive integer, the N terminal devices comprising the first terminal device.

[0073] In some implementations, the communication apparatus can include a module, unit or means corresponding to each of the methods / operations / steps / actions described in the second aspect and any possible implementation of the second aspect, which can be hardware circuit, software or a combination of hardware circuit and software.

[0074] In some possible implementations, the apparatus includes a transceiving unit and a processing unit. The transceiving unit is configured to send first information to a first entity, the function of the first entity comprising providing a first core network service for the first terminal device, the first entity being deployed on a first satellite, the first information being used to request the first core network service, the first core network service being implemented by the first entity; and the transceiving unit is further configured to receive second information from the first entity, the second information being used to indicate an execution result of the first core network service.

[0075] In some implementations, the transceiving unit is further configured to receive eighth information from the second entity, the eighth information being used to indicate that the first entity is used to provide the first core network service for the first terminal device.

[0076] In some implementations, the transceiving unit is further configured to send ninth information to the second entity, the ninth information being used to request that the first terminal device is associated with an entity used to provide the first core network service.

[0077] In some implementations, the transceiving unit is further configured to receive tenth information from the second entity, the tenth information being used to indicate that a third entity is used to provide a second core network service for the first terminal device, the first core network service being different from the second core network service.

[0078] In some implementations, the transceiving unit is further configured to send eleventh information to the second entity, the eleventh information being used to request that the first terminal device is further associated with an entity used to provide the second core network service.

[0079] In some implementations, the second entity is deployed on the first satellite, and / or the second entity is a core network network element.

[0080] In some implementations, the communication apparatus can include a module, unit or means corresponding to each of the methods / operations / steps / actions described in the third aspect and any possible implementation of the third aspect, which can be hardware circuit, software or a combination of hardware circuit and software.

[0081] Optionally, the communication apparatus is deployed at a first satellite, and / or the communication apparatus is a core network network element.

[0082] In some possible implementations, the apparatus includes a processing unit and a transceiver unit. The processing unit is configured to determine a first entity, the first entity being deployed at a first satellite, the first entity being configured to provide a first core network service for a first terminal device, wherein the first core network service is implemented by the first entity. The transceiver unit is configured to send, to the first terminal device, eighth information, the eighth information being used to indicate the first entity for providing the first core network service for the first terminal device.

[0083] In some implementations, the transceiver unit is further configured to receive, from the first terminal device, ninth information, the ninth information being used to request an entity associated with the first terminal device for providing the first core network service.

[0084] In some implementations, the first entity is capable of performing at least one of the following operations: maintaining a context of the first terminal device; implementing at least one core network service, the at least one core network service including the first core network service; or scheduling a resource for performing the first core network service.

[0085] In some implementations, the transceiver unit is further configured to send, to the first entity, third information, the third information being used to at least one of the following: maintaining a context of the first terminal device, information of a location of the first entity, information of core network services that the first entity is capable of providing, or information of a resource for performing a core network service.

[0086] In some implementations, the third information is used to maintain a state of the first entity, the state of the first entity including at least one of the following: a first state, the first entity in the first state being capable of providing all core network services configured by a second entity; a second state, the first entity in the second state not storing a context of the first terminal device; a third state, the first entity in the third state not providing core network services configured by the second entity; or a fourth state, the first entity in the fourth state being capable of providing part of core network services configured by the second entity.

[0087] In some embodiments, the transceiving unit is further configured to send, to the first entity, seventh information indicating that a function of the first entity comprises providing the first core network service for N terminal devices, N being a positive integer, the N terminal devices comprising the first terminal device.

[0088] In some embodiments, the transceiving unit is further configured to send, to the second terminal device, twelfth information indicating that the first entity is configured to provide the first core network service for the second terminal device.

[0089] In some embodiments, the transceiving unit is further configured to send, to the first terminal device, tenth information indicating that a third entity is configured to provide a second core network service for the first terminal device, the first core network service being different from the second core network service.

[0090] In some embodiments, the transceiving unit is further configured to receive, from the first terminal device, eleventh information requesting that the first terminal device is further associated with an entity configured to provide the second core network service.

[0091] In some embodiments, the transceiving unit is further configured to receive, from the first entity, fourth information requesting migration of a function configured to provide the first core network service for the first terminal device.

[0092] In some embodiments, the transceiving unit is further configured to receive, from the first entity, fifth information indicating context of the first terminal device and / or entity requirement information.

[0093] In some embodiments, the processing unit is further configured to determine a fourth entity, the fourth entity being deployed on a second satellite, a function of the fourth entity comprising providing the first core network service for the first terminal device.

[0094] In some embodiments, the transceiving unit is further configured to send, to the first entity, sixth information indicating a condition triggering migration.

[0095] In a sixth aspect, a computer readable storage medium is provided, and the computer readable storage medium has stored thereon a computer program or instructions, which when executed on a computer, cause the first aspect and any possible method of the first aspect to be performed, or cause the second aspect and any possible method of the second aspect to be performed, or cause the third aspect and any possible method of the third aspect to be performed.

[0096] In a seventh aspect, a computer program product is provided, which contains computer programs or instructions, when the computer programs or instructions are run on a computer, cause the first aspect and any possible implementation of the first aspect to be performed (or implemented), or cause the second aspect and any possible implementation of the second aspect to be performed (or implemented), or cause the third aspect and any possible implementation of the third aspect to be performed (or implemented).

[0097] In an eighth aspect, a communication apparatus is provided, which comprises a processor configured to cause any possible implementation of the first aspect to be performed, or cause any possible implementation of the second aspect to be performed, or cause any possible implementation of the third aspect to be performed, by executing computer programs (or computer executable instructions) stored in a memory and / or by a logic circuit.

[0098] In a possible implementation, the apparatus further comprises a memory. In a possible implementation, the processor and the memory are integrated together. In another possible implementation, the memory is located outside the communication apparatus. The processor can comprise one or more processors.

[0099] In a possible implementation, the communication apparatus further comprises a communication interface configured to enable the communication apparatus to communicate with other devices, such as transmitting or receiving data and / or signals. Exemplarily, the communication interface can be a transceiver, a circuit, a bus, a module or other types of communication interface.

[0100] In an implementation, the communication apparatus of the fourth aspect, the fifth aspect or the eighth aspect can be a chip or a chip system.

[0101] In a ninth aspect, a chip is provided, which comprises a processor configured to invoke computer programs or computer instructions in a memory, so as to cause the processor to perform any implementation of the first aspect, or to cause the processor to perform any implementation of the second aspect, or to cause the processor to perform any implementation of the third aspect.

[0102] In some implementations, the processor is coupled with the memory through an interface.

[0103] In a tenth aspect, a communication system is provided, which comprises a first entity configured to perform the first aspect and any possible implementation of the first aspect, a first terminal device configured to perform the second aspect and any possible implementation of the second aspect, and a second entity configured to perform the third aspect and any possible implementation of the third aspect.

[0104] In an eleventh aspect, a communication method is provided, which is applied to a first entity and a second entity. The first entity can be configured to implement the first aspect and any possible implementation of the first aspect. The second entity can be configured to implement the third aspect and any possible implementation of the third aspect.

[0105] The description of the beneficial effects of any of the second aspect to the eleventh aspect can refer to the description of the beneficial effects of the first aspect. The description of the beneficial effects of some implementations of any of the third aspect to the eleventh aspect can refer to the description of the beneficial effects of the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0106] FIG. 1 is a schematic diagram of a network architecture of a communication system.

[0107] FIG. 2 is a schematic diagram of a network architecture of another communication system.

[0108] FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of the present application.

[0109] FIG. 4 is a schematic flowchart of a communication method provided by an embodiment of the present application.

[0110] FIG. 5 is a schematic diagram of a state of a first entity provided by an embodiment of the present application.

[0111] FIG. 6 is a schematic flowchart of another communication method provided by an embodiment of the present application.

[0112] FIG. 7 is a schematic flowchart of still another communication method provided by an embodiment of the present application.

[0113] FIG. 8 is a schematic flowchart of yet another communication method provided by an embodiment of the present application.

[0114] FIG. 9 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.

[0115] FIG. 10 is a schematic block diagram of another communication apparatus provided by an embodiment of the present application. DETAILED DESCRIPTION

[0116] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0117] The present application will present various aspects, embodiments or features around a system which can include a plurality of devices, components, modules, etc. It should be understood and appreciated that each system can include devices, components, modules, etc. other than those illustrated and / or can not include all of the devices, components, modules, etc. discussed in conjunction with the accompanying drawings.

[0118] In the embodiments of the present application, the words such as "exemplarily", "for example" and the like can be used to represent examples, illustrations or descriptions, and to present concepts in a specific manner. Any embodiment or design scheme described as "exemplary" in the present application should not be interpreted as being more preferred or having more advantages than other embodiments or design schemes.

[0119] The service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation to the technical solutions provided by the embodiments of the present application. It can be known by those skilled in the art that, with the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0120] In the present specification, the reference to "one embodiment" or "some embodiments" and the like means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Therefore, the appearances of the phrases "in one embodiment", "in some embodiments", "in other some embodiments", "in yet some embodiments" and the like in various places in the present specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments" unless otherwise specifically stated. The terms "comprising", "containing", "having" and their derivatives mean "including but not limited to", unless otherwise specifically stated.

[0121] The first, second and the like appearing in the embodiments of the present application are only used for description and distinction of the description objects without order and do not represent particular limitation of the number in the embodiments of the present application, and cannot constitute any limitation to the embodiments of the present application.

[0122] It should be understood that, in various embodiments of the present application, the magnitude of the serial number of each process does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0123] It can be understood that, in the present document, the term "and / or" only describes the association relationship of the associated objects, and means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in the present document generally represents an "or" relationship between the front and rear associated objects.

[0124] The technical solutions of the embodiments of the present application can be applied to various communication systems, including but not limited to: long term evolution (LTE) system, new radio (NR) system and the like fifth generation (5G) communication system. tha fifth generation, 5G) mobile communication system, a narrow band internet of things (NB-IoT) system, an enhanced machine-type communication (eMTC) system, an enhanced mobile broadband (eMBB) system, an ultra reliable low latency communications (URLLC) system, a satellite communication system, an LTE-machine-to-machine (LTE-M) system, or a system evolved from the 5G, such as a sixth generation (6G) mobile communication system, and the like. th

[0125] In embodiments of the present application, the term "communication" can also be described as "data transmission", "signal transmission", "information transmission" or "transmission" and the like. In embodiments of the present application, transmission can include sending or receiving. Exemplarily, transmission can be uplink transmission, for example, a terminal device can send a signal to a network device; transmission can also be downlink transmission, for example, a network device can send a signal to a terminal device; transmission can also be sidelink transmission, for example, a terminal device can send a signal to another terminal device. Exemplarily, "transmission" can be air interface level transmission, or can refer to signal sending of a chip input (I) / output (O) interface, rather than air interface level transmission.

[0126] FIG. 1 is a schematic diagram of a network architecture of a communication system. The network architecture includes at least one network function (NF). Exemplarily, the at least one NF can include: a network capability exposure 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) connected to an operator network. A terminal device can send service data to a data network and receive service data from the data network through an access network device, a user plane function network element. The access network device can communicate with a network management.

[0127] ​The terminal device can be a device with wireless transceiving function. The terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on water surface (such as ships and the like); and can also be deployed in the air (such as airplanes, balloons and satellites and the like). The terminal device can communicate with a core network through a radio access network (RAN), and exchange voice and / or data with the RAN. The terminal device can be a mobile phone, a Pad, a computer with wireless transceiving function, a mobile internet device (MID), a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a drone, a drone controller and the like. The embodiments of the present application do not limit the application scenarios. The terminal device can also be referred to as user equipment (UE), mobile station and remote station and the like, and the embodiments of the present application do not limit the specific technology, device form and name of the terminal device. The terminal device can be a mobile device supporting a satellite-air interface. The terminal device can access a satellite network through the air interface and initiate a call, access the Internet and the like.

[0128] The access network device can be a device in a network for accessing a terminal device to a wireless network. The access network device can be a node in a radio access network, which can also be referred to as a base station, and can also be referred to as a RAN node (or device). For ease of description, the RAN will be used to refer to the access network device below. The access network device can include an evolved Node B (eNB or e-NodeB, evolutional Node B) in a long term evolution (LTE) system or an LTE-Advanced (LTE-A) system, such as a conventional macro base station eNB and a micro base station eNB in a heterogeneous network scenario, or can also include a next generation Node B (gNB) in a 5G or NR system, or can also include a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a transmission reception point (TRP), a home base station (for example, a home evolved NodeB, or a home Node B, HNB), a base band unit (BBU), a base band pool BBU pool, or a wireless fidelity (WiFi) access point (AP), or can also include a centralized unit (CU) and a distributed unit (DU) in a cloud radio access network (CloudRAN) system, and the embodiments of the present application are not limited. In a separate deployment scenario in which the access network device includes a CU and a DU, the CU supports radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and the like; the DU mainly supports radio link control (RLC), media access control (MAC), and physical layer protocols. The access network device can provide a wireless access service. For example, the access network device can schedule wireless resources for a terminal device to be accessed.For another example, the access network device can provide a reliable wireless transmission protocol and / or a data encryption protocol, etc.

[0129] The network capability exposure network element can expose part of the functions of the network to the application in a controlled manner. In the 5G communication system, the network capability exposure network element can be a network exposure function (NEF). In future communication systems (such as the 6G communication system), the network capability exposure network element can still be the NEF network element, or can also have other names, which are not limited by the present application.

[0130] The network storage function network element is mainly used for registration, discovery, state detection, etc. of network elements, services provided by network elements, or functions of network elements. The network storage function network element can realize automatic management, selection and scalability of network function services, and allows each network function to discover services provided by other network functions. In the 5G communication system, the network storage function network element can be a network repository function (NRF). In future communication systems (such as the 6G communication system), the network storage function network element can still be the NRF network element, or can also have other names, which are not limited by the present application.

[0131] The network data analysis network element can collect data from various NFs, application function network elements (through the network capability exposure function network element), terminal devices, network management, etc., and perform analysis and prediction. The network data analysis network element has data collection, training, analysis, and reasoning functions. Based on the analysis and training of relevant data, the network data analysis network element can provide data analysis results to network functions, application function network elements, terminal devices, or network management systems. The analysis results can assist the network in selecting service quality parameters of services, or assisting the network in performing traffic routing, or assisting the network in selecting background data transmission strategies, etc. Network functions include policy control network elements, session management network elements, user plane function network elements, access and mobility management network elements, etc. In the 5G communication system, the network data analysis network element can be a NWDAF. In future communication systems (such as the 6G communication system), the network data analysis network element can still be the NWDAF network element, or can also have other names, which are not limited by the present application.

[0132] The application function network element can be used to deliver application-side requirements to the network side. For example, the requirements can include quality of service (QoS) requirements or user state event subscriptions, etc. The application function network element can provide service data of various applications to the control plane network element of the operator's communication network, or obtain data information and control information of the network from the control plane network element of the communication network. In the 5G communication system, the application function network element can be an application function (AF), and in future communication systems (such as 6G communication systems), the application function network element can still be an AF network element, or can have other names, which are not limited by the present application. For example, the application function network element can also be referred to as an application server or a service server. In addition, the application function network element can be deployed by the operator network, or can be deployed by a third party.

[0133] The policy control network element can be used to formulate and manage the policies of the entire network (such as a 5G network). The policy control network element can include a policy control function, a charging policy control function, etc. The policy control network element can generate and maintain QoS flow control policies, network slice policies, mobility management policies, charging policies, UE access policies, etc. The policy control network element can dynamically generate and adjust policies according to the business needs and network status of the operator, and issue the policies to related network elements such as the access and mobility management network element, the session management network element, and the user plane function network element, to guide the behavior of these related network elements. In addition, the policy control network element can also receive the quality of service requirements of the application function network element, and convert them into corresponding policies. In the 5G communication system, the policy control network element can be a policy control function (PCF), and in future communication systems (such as 6G communication systems), the policy control network element can still be a PCF network element, or can have other names, which are not limited by the present application.

[0134] The unified data storage network element is mainly used to store structured data information, which includes subscription information, policy information, and network data or service data with standard format definition. In the 5G communication system, the unified data storage network element can be a unified data repository (UDR), and in future communication systems (such as 6G communication systems), the unified data storage network element can still be a UDR network element, or can have other names, which are not limited by the present application.

[0135] The unified data management network element is mainly used for managing and storing user data (or subscription information) of terminal devices. For example, user identity information, authentication information, subscription information, policy information, and the like. The unified data management network element can provide query and update services of user data for other network elements. The unified data management network element can support functions such as authentication, authorization, and key management of users. In addition, the unified data management network element can update and synchronize user data according to policy control of the policy control network element. In the 5G communication system, the unified data management network element can be a unified data management (UDM). In future communication systems (such as 6G communication systems), the unified data management network element can still be a UDM network element, or can also have other names, which are not limited by the present application.

[0136] The access and mobility management network element is mainly used for attachment and tracking area update procedures of terminals in a mobile network. The access and mobility management network element can provide non-access stratum (NAS) messages, complete registration management, connection management, reachability management, allocate a tracking area list (TA list), lawful interception, access authorization, authentication, and mobility management, and transparently route session management (SM) messages to the session management network element. In the 5th generation (5G) communication system, the access and mobility management network element can be an access and mobility management function (AMF). In future communication systems (such as 6G communication systems), the mobility management network element can still be an AMF network element, or can also have other names, which are not limited by the present application.

[0137] The session management network element can be used for session and bearer management in a mobile network, such as session establishment, modification, and release. Specific functions include allocating and managing internet protocol (IP) addresses for UEs, selecting user plane function network elements that provide message forwarding functions, and the like. For example, the session management network element can select a suitable user plane function network element for a UE according to a request of the UE and policy control information of the policy control network element, establish a session with the user plane function network element, generate QoS rules and charging rules, and the like. The session management network element can control data forwarding and processing behavior of the user plane function network element. In the 5G communication system, the session management network element can be a session management function (SMF). In future communication systems (such as 6G communication systems), the session management network element can still be an SMF network element, or can also have other names, which are not limited by the present application.

[0138] Binding support network element, mainly used for session binding, selects policy control function network element for users. In the 5G communication system, the binding support network element can be a BSF. In future communication systems (such as 6G communication systems), the binding support network element can still be a BSF network element, or can also have other names, which are not limited by the present application.

[0139] User plane function network element, which can be used for processing user messages such as forwarding, charging, lawful interception, etc. In addition, the user plane function network element can be used for routing and forwarding of user plane data packets, processing of QoS flows, threshold control, traffic monitoring, verification, detection and reporting of data packets, etc. The user plane function network element can also be used for management of UE IP addresses, management of core network (CN) tunnel information, etc. The user plane function network element can be located in the 5G core network user plane to provide high-speed, efficient and flexible data transmission services for UEs. In addition, the user plane function network element can also perform filtering, traffic shaping, charging, etc. on data packets according to the indication of the control plane, to realize fine management and control of user data flow. The user plane function network element can be connected with the access network device through the N3 interface and connected with the data network through the N6 interface, so as to realize data transmission between the UE and the external data network. The user plane function network element can also be called a protocol data unit (PDU) session anchor (PSA). In the 5G communication system, the user plane function network element can be a user plane function (UPF). In future communication systems (such as 6G communication systems), the user plane function network element can still be a UPF network element, or can also have other names, which are not limited by the present application.

[0140] Network management, mainly used for completing daily network and service analysis, prediction, planning and configuration work, as well as testing and fault management of network and services, etc. OAM can interact with RAN to obtain information such as wireless channel conditions and wireless resource utilization of RAN side. In the 5G communication system, the network management can be an operations administration and management (OAM). In future communication systems (such as 6G communication systems), the network management can still be an OAM network element, or can also have other names, which are not limited by the present application.

[0141] A data network is mainly used to provide data transmission services for terminal devices. The data network can be a private network such as a local area network, a public data network (PDN) network such as the Internet, or a dedicated network deployed by operators such as a configured IP multimedia core network subsystem (IMS) service. The data network can also come from a third party.

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

[0143] 1. N1: the interface between the AMF and the UE, which can be used to transmit QoS control rules and the like to the UE.

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

[0145] 3. N3: the interface between the RAN and the UPF, which is used to transmit uplink or downlink user plane data between the RAN and the UPF.

[0146] 4. N4: the interface between the SMF and the UPF, which can be used to transmit information between the control plane and the user plane, including the delivery of forwarding rules, QoS control rules, traffic statistics rules and the like from the control plane to the user plane, and the reporting of information from the user plane.

[0147] 5. N6: the interface between the UPF and the DN, which is used to transmit uplink or downlink user data streams between the UPF and the DN.

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

[0149] The above network elements or functions can be network elements in a hardware device, software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). Alternatively, the above network elements or functions can be implemented by one device, or by multiple devices together, or can be a functional module within a device, and the embodiments of the present application do not make specific limitations thereto.

[0150] The above naming is only defined for the convenience of distinguishing different functions, and should not constitute any limitation on the present application. The present application does not exclude the possibility of using other names in 5G networks and future other networks. For example, in a 6G network, part or all of the above-mentioned networks can continue to use the terms in 5G, or other names may be used. The interface names between the network elements in FIG. 1 are only an example, and the names of the interfaces in the specific implementation may be other names, which are not limited in the present application. In addition, the names of the messages (or signaling) transmitted between the above-mentioned network elements are also only an example, and do not constitute any limitation on the functions of the messages themselves.

[0151] The above-mentioned "network element" can also be referred to as an entity, device, apparatus or module, etc., which is not particularly limited in the present application. In addition, in order to facilitate understanding and description, the description of "network element" is omitted in part of the description, for example, the PCF network element is simply referred to as PCF, in this case, the "PCF" should be understood as the PCF network element or the PCF entity, and the following description of the same or similar cases is omitted.

[0152] FIG. 2 is a schematic diagram of a network architecture of another communication system 200. The communication system 200 can combine satellite communication technology and cellular communication technology. As shown in FIG. 2, the mobile terminal on the ground can access the network through the air interface. The access network device (for example, base station) can be deployed on the satellite and connected to the core network function on the satellite through a wireless link. There can be a wireless link between satellites, which can be used for signaling interaction and user data transmission between one access network device and other access network devices. The description of the terminal and base station in FIG. 2 can be referred to the foregoing, for example, the description in FIG. 1. Herein, the description is not repeated. Some network elements and interfaces in FIG. 2 are described as follows.

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

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

[0155] The air interface can represent the wireless link between the terminal and the access network device.

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

[0157] The NG interface can be an interface between a base station and a core network. For example, the NG interface can be used for signaling interaction such as non access stratum (NAS) of the core network. For another example, the NG interface can be used for interaction of service data of a user.

[0158] The service-based architecture (SBA) interface can be a service-based interface between a base station and a satellite function unit. The satellite function unit can be a function or entity deployed on a satellite. For example, the satellite function unit can be used to implement functions such as handover, authentication, or session establishment.

[0159] In a satellite communication system, in order to reduce the time delay caused by the round trip of core network signaling between satellite and ground, the core network element can be deployed on the satellite platform, so as to provide core network services for users. Due to the limited payload capacity of the satellite, it is difficult to deploy a complete core network function on one satellite, so different core network elements can be deployed on different satellites. For example, an AMF is deployed on one satellite, and an SMF is deployed on another satellite. In order to complete a core network service requested by a user (for example, user registration, session establishment), multiple core network elements need to work together to perform corresponding operations to implement the core network service. In this way, multiple satellites need to frequently interact with the context of the user to implement a core network service. The inter-satellite link can be unstable, and frequent migration of the user context can lead to a high probability of context error, thereby reducing the quality of the service provided by the core network. In addition, frequent migration of the user context can lead to a large signaling overhead.

[0160] Therefore, embodiments of the present application provide some communication schemes. Wherein, the entity implementing the core network service is deployed on the satellite, which can avoid frequent interaction of the user context between multiple satellites, thereby avoiding errors in the user context on which the core network service is based, and further improving the quality of the service provided by the core network. In addition, the communication scheme provided by the embodiments of the present application can reduce the signaling overhead caused by the interaction of the user context.

[0161] FIG. 3 is a schematic flowchart of a communication method 300 provided by an embodiment of the present application. The method 300 can improve the quality of the service provided by the core network. The optional operations in the method 300 are indicated by dashed lines in FIG. 3. The method 300 will be described below in conjunction with FIG. 3.

[0162] S310, a first entity receives first information from a first terminal device. Correspondingly, the first terminal device sends the first information to the first entity.

[0163] In the absence of special description, the first entity in the present application can refer to the first entity itself (for example, an access network device or other device), can refer to a component (for example, a processor, a chip, or a chip system, etc.) in the first entity, or can also refer to a logic module or software capable of realizing all or part of the functions of the first entity. For ease of description, the first entity is described below as an example.

[0164] In the absence of special description, the first terminal device in the present application can refer to the first terminal device itself, can refer to a component (for example, a processor, a chip, or a chip system, etc.) in the first terminal device, or can also refer to a logic module or software capable of realizing all or part of the functions of the first terminal device. For ease of description, the first terminal device is described below as an example.

[0165] The present application does not limit the name of the first entity, and the first entity can also be referred to as a user agent (UE agent, UA), a service entity, a service function, a user agent function, a user agent entity, or by other names.

[0166] In some possible implementation manners, the first entity is deployed on a first satellite. For example, the first entity can be deployed in an access network device, a core network device, or other device on the first satellite. Optionally, the first entity is deployed on a satellite where the first access network device is located. The first access network device is an access network device that provides services for the first terminal device.

[0167] Exemplarily, the first satellite can be a low earth orbit (LEO) satellite; in other words, the first entity can be deployed on a LEO satellite. The present application does not limit the name of the first satellite, and the first satellite can also be referred to as an aircraft, a spacecraft, a flying object, or by other names.

[0168] In addition, the present application does not limit the first entity to be deployed only on a satellite. In other possible implementation manners, the first entity is deployed in a ground device. For example, the first entity can be deployed in a ground base station or a core network device.

[0169] Optionally, the first information is used to request the first core network service. In other words, the first information is used to request the first entity to provide the first core network service.

[0170] In this application, the term "sending" can be understood as direct sending. For example, the first terminal device directly sends the first information to the first entity. The term "sending" 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. Wherein, the base station can establish an RRC connection with the first terminal device in advance.

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

[0172] The first core network service can be one or more core network services. Illustratively, the first core network service can include inter-RAN node handover, session creation, session maintenance, paging, registration, or positioning, etc. The name of the first core network service is not limited in this application, and the first core network service can also be called service, function, business, core network function, core network business, network service, network function, network business, or have other names.

[0173] The name of the first information is not limited in this application, and the first information can also be called request, service request, or have other names.

[0174] Optionally, the first core network service is implemented by the first entity. Wherein, the term "implementation" can be understood as that the first entity has completed the implementation of the first core network service, or can be understood as that the first entity has completely executed the function sequence of the first core network service.

[0175] Taking the first core network service as a registration service as an example. The function sequence of the registration service can be: context read function->authentication / authorization function->policy generation function->context write function. According to the order shown in the above function sequence, the operations of each function are executed in turn, which can realize the logical function of registration. Traditional core network elements are difficult to implement the registration service alone. For example, the context read function may need to be executed by the UDM; the authentication / authorization function may need to be executed by the AUSF; the policy generation function may need to be executed by the PCF. That is, the above registration service needs to be executed by multiple core network elements. And these core network elements are often deployed on multiple satellites. Therefore, in the traditional scheme, the above registration service may need to be executed by multiple satellites, that is, multiple satellites need to be implemented.

[0176] The first entity in the embodiments of the present application 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 the embodiments of the present application, the entity deployed on a satellite can implement the registration service, that is, can execute the function sequence of the registration service described above. Therefore, in the embodiments of the present application, the registration service described above can be executed by a satellite, that is, can be implemented by a satellite.

[0177] Optionally, the function of the first entity includes providing the first terminal device with the first core network service. Alternatively, the first entity is configured to provide the first terminal device with the first core network service. Alternatively, the first entity is capable of providing the first terminal device with the first core network service. Alternatively, the first entity has the function of providing the first terminal device with the first core network service. Alternatively, the first entity corresponds to the first terminal device. Alternatively, the first entity is associated with the first terminal device. Alternatively, the first terminal device is a terminal device dedicated to the first entity.

[0178] The function of the first entity includes providing the first terminal device with the first core network service, which can be understood as that the function of the first entity includes providing a specific terminal device with a core network service, or that the first entity can provide a terminal device associated therewith with a dedicated core network service. The terminal device associated with the first entity can be one or more.

[0179] Optionally, the first entity does not provide any terminal device with a core network service. For example, the first entity does not provide a terminal device not associated therewith with a core network service.

[0180] The first entity provides the first terminal device with the first core network service, which can be understood as that the core network service executed by a traditional core network is offloaded to an entity associated with the first terminal device, and the entity provides the first terminal device with a dedicated core network service.

[0181] In some possible implementation manners, the first entity is configured to store a context of the first terminal device. For example, the first entity can include a storage unit (or a memory), which can be configured to store the context of the first terminal device. In the present application, the context of the terminal device can be understood as the context of a user. For example, the context of the first terminal device can be the context of a first user.

[0182] The term "store" can be understood as that the context of the first terminal device is stored in the first entity or the first satellite deployed by the first entity for a relatively long time. Those skilled in the art can understand that the storage is different from the caching. The first entity caches a certain information, which means that the information is temporarily loaded into the first entity. The information will not be kept for a long time. The information is often deleted after being used, thereby releasing the cache occupied by the information.

[0183] Through the above scheme, the first entity can store the context of the terminal device. Compared with the scheme of storing the context of the terminal device into other devices, the above scheme can reduce the time delay of the first entity obtaining the context of the terminal device, thereby improving the efficiency of executing the core network service. Those skilled in the art can understand that, since the first entity only provides the core network service for the terminal device associated with it, the first entity can store the context of the terminal device associated with it in the limited storage space on the satellite.

[0184] It can be understood that, if the entity deployed on the satellite can provide the core network service for any terminal device, the context of the terminal device will not be stored on the satellite. This is because the storage space on the satellite is limited and cannot store the context of all terminal devices. In this case, the context of the terminal device is often stored on a ground device or a geosynchronous earth orbit (GEO) satellite. In this way, the entity deployed on the LEO satellite needs to obtain the context of the terminal device from the ground device or the GEO satellite.

[0185] The present application does not limit that only the first entity can store the context of the first terminal device. The storage unit for storing the context of the first terminal device can also be outside the first entity. For example, the first satellite can include the first entity and a first storage unit. The first storage unit is used to store the context of the first terminal device. The first entity can obtain the context of the first terminal device from the first storage unit.

[0186] In some possible implementation manners, the method 300 further includes: (S320) the first entity executes the first core network service according to the context of the first terminal device. In other words, the first entity implements the first core network service according to the context of the first terminal device.

[0187] For example, the processing unit of the first entity can read the context of the first terminal device from the storage unit of the first entity. The processing unit of the first entity can execute the first core network service according to the context of the first terminal device.

[0188] After the first entity performs the first core network service, the first entity can obtain an execution result of the first core network service. For example, the first core network service is a registration service; the execution result of the first core network service can be that the first terminal device is successfully registered or fails to register. For another example, the first core network service is an information query service; the execution result of the first core network service can include the queried information.

[0189] After the first entity performs the first core network service, the context of the first terminal device changes relative to the context of the first terminal device before the first core network service is performed. The changed context of the first terminal device can be referred to as an updated context of the first terminal device. The first entity can update the context of the first terminal device stored in the storage unit. For example, the first entity can overwrite the original context of the first terminal device with the updated context of the first terminal device.

[0190] In S330, the first entity sends second information to the first terminal device. Correspondingly, the first terminal device receives the second information from the first entity.

[0191] Optionally, the second information is used to indicate the execution result of the first core network service.

[0192] In some possible implementation manners, the second information can be direct indication information, that is, the second information contains information of the execution result of the first core network service. In another possible implementation manner, the second information can be indirect indication information, and the receiving end can determine the execution result of the first core network service according to the second information. For example, the receiving end can pre-acquire a mapping relationship between the execution result of the first core network service and an identifier. The second information can contain the identifier, so that the receiving end can determine the execution result of the first core network service corresponding to the identifier.

[0193] Embodiments of the present application do not limit the name of the second information. For example, the second information can also be referred to as a service response (service response) or have another name.

[0194] Through the above scheme, the entity deployed on a satellite can implement core network services. On the one hand, considering that the payload capacity of the satellite is limited, the deployment of the entity instead of the deployment of the core network element reduces the deployment complexity of the satellite core network. On the other hand, the core network service requested by the terminal device can be implemented through the entity, avoiding the cooperation of core network elements on multiple satellites to complete, thereby avoiding the frequent migration of user contexts. The above scheme can not only reduce the communication delay caused by the transmission of user contexts, but also avoid errors in the transmission process of the user contexts on which the core network services are based, thereby improving the quality of the services provided by the core network.

[0195] In addition, in the foregoing solution, the entity is associated with the terminal device. The entity can provide the core network service for the dedicated terminal device. Compared with the entity providing the core network service for any terminal device, the entity in the foregoing solution can reduce the latency of providing the service for the terminal device, because the number of terminal devices associated with the entity in the foregoing solution is limited. One reason is that the number of requests of the terminal device processed by the entity in the foregoing solution is small. In this way, in the case where a terminal device requests the core network service, the entity can immediately provide the core network service for the terminal device. Alternatively, the entity can provide the core network service for the terminal device after processing a small number of requests of other terminal devices.

[0196] FIG. 4 is a schematic flowchart of a communication method 400 provided by an embodiment of the present application. The method 400 can be combined with the foregoing method 300. The optional operations in the method 400 are indicated by dashed lines in FIG. 4. The method 400 is described below in combination with FIG. 4.

[0197] S410. The first terminal device sends ninth information to the second entity. Correspondingly, the second entity receives the ninth information from the first terminal device.

[0198] Unless otherwise specified, the second entity in the present application can refer to the second entity (for example, a core network element, an access network device, or another device) itself, a component (for example, a processor, a chip, or a chip system) in the second entity, or a logic module or software capable of realizing all or part of the functions of the second entity. For ease of description, the second entity is described below as an example. The specific form of the second entity is described below, and is not described here in detail.

[0199] Optionally, the ninth information is used to request the second entity to associate the first terminal device with the entity for providing the first core network service. In other words, the ninth information is used to request the second entity to associate the first terminal device with the entity for providing the first core network service. In this way, the second entity can associate the first terminal device with the entity for providing the first core network service based on the ninth information. For example, the second entity can associate the first terminal device with the first entity.

[0200] Optionally, the ninth information is further used to indicate entity requirement information. The entity requirement information can be used to indicate the requirement of the entity providing the core network service. As an example, the entity requirement information can indicate the information of the core network service. For example, the entity requirement information can indicate the mobility management. In this way, the receiving end can learn, according to the entity requirement information, that an entity providing the mobility management needs to be associated with the first terminal device. As another example, the entity requirement information can indicate the information of the resource (e.g., software resource or hardware resource). In this way, the receiving end can learn, according to the entity requirement information, how many resources the entity associated with the first terminal device needs to occupy.

[0201] The present application does not limit the entity requirement information to be indicated by the ninth information only, but the entity requirement information can also be indicated by other information. In other words, the second entity can also obtain the entity requirement information through other information in addition to the ninth information.

[0202] Optionally, the ninth information is further used to indicate configuration information. For example, the configuration information can be used to generate the first entity. The present application does not limit the configuration information to be indicated by the ninth information only, but the configuration information can also be indicated by other information. In other words, the second entity can also obtain the configuration information through other information in addition to the ninth information. In some other optional embodiments, the configuration information can be generated by the second entity according to the entity requirement information.

[0203] The present application does not limit the name of the ninth information, for example, the ninth information can also be called a registration request, an association request, or have other names.

[0204] Through the above scheme, the first terminal device can request to associate the entity providing the core network service, so that the receiving end can perform corresponding operations based on the request.

[0205] It can be understood that, as shown in FIG. 4, S410 is an optional operation. In some other possible implementations, the first terminal device can not send the ninth information to the second entity, that is, does not request to associate the entity providing the first core network service for the first terminal device. In the case where S410 is not performed, the second entity can also actively associate the entity providing the first core network service for the first terminal device.

[0206] S420, the second entity determines the first entity. The function of the first entity can include providing the first core network service for the first terminal device. S420 is an optional operation.

[0207] Optionally, S420 includes: in response to the ninth information, the second entity determines the first entity.

[0208] In some possible implementation, S420 comprises: the second entity registers (or creates) the first entity, and the function of the first entity can comprise providing the first core network service for the first terminal device.

[0209] Exemplarily, S420 can comprise S422, S424 and S426. S422, S424 and S426 can describe the process of the second entity newly creating the first entity. Wherein, the present application does not limit the execution order of S422, S424 and S426. For example, S426 can be executed before S422.

[0210] S422, the second entity performs resource allocation for the first entity.

[0211] Exemplarily, the second entity can send request information to a device (for example, an access network device or other device) on the first satellite, and the request information is used to request the device to provide resources for the first entity. Optionally, the request information can carry the size of the resources. In some possible implementation, the resources allocated by the second entity for the first entity can be determined by unilateral decision. For example, the resources allocated by the second entity for the first entity can be determined by the second entity. For another example, the resources allocated by the second entity for the first entity can be determined by the device (for example, an access network device or other device) on the first satellite. In other possible implementation, the resources allocated by the second entity for the first entity can be determined by multi-lateral negotiation. For example, the second entity and the device (for example, an access network device or other device) on the first satellite can negotiate to determine the resources to be allocated.

[0212] Exemplarily, the resources allocated by the second entity for the first entity can be software resources or hardware resources. For example, 100 megabytes (MB) of storage space, which can be used to store the context of the first terminal device. For another example, 10% of the total processing capacity, which is used to execute the core network service (for example, the first core network service).

[0213] Exemplarily, the resources allocated by the second entity for the first entity can be used to execute the core network service (for example, the first core network service).

[0214] Optionally, the first entity comprises a resource unit. The resource unit can be used to schedule the resources allocated by the second entity to implement the core network service.

[0215] S424, the second entity performs function generation for the first entity.

[0216] Exemplarily, the second entity can configure the first entity to implement a functionality of one or more core network services (e.g., a first core network service). In other words, the second entity can configure one or more core network services (may be referred to as “configured core network services” below) that the first entity is capable of implementing. For example, the configured core network services can be inter-RAN node handover, session creation, session maintenance, paging, registration, or positioning, etc.

[0217] To implement the core network service, the first entity can perform one or more core network operations based on a context of the terminal device (e.g., a first terminal device). For example, the core network operations can include mobility management, session management, security management, or computing management, etc. The core network operations can be defined by orchestration based on the core network service, where the core network service can be regarded as a task. In this way, a closed, single execution flow can be created for different tasks to implement the core network service.

[0218] Optionally, the first entity comprises a processing unit. The processing unit can be used to implement the core network service. For example, the processing unit can perform a series of core network operations orchestrated to implement the core network service. For another example, the processing unit can implement the core network service according to resources scheduled by the resource unit.

[0219] S426, the second entity performs context generation for the first entity.

[0220] The second entity can create an initial context of the first terminal device for the first entity. Exemplarily, the initial context of the first terminal device can comprise one or more of the following parameters. The term “initial” is with respect to the first entity. That is, the first entity has obtained the context of the first terminal device for the first time.

[0221] Initial security parameters, the initial security parameters can comprise at least one of identification information of the terminal device, key information, or an algorithm associated with authentication or authorization. The initial security parameters can further comprise other information.

[0222] Initial policy parameters, the initial policy parameters can comprise at least one of mobility management policy, session policy, or charging policy. The initial policy parameters can further comprise other information.

[0223] Initial transmission parameters, the initial transmission parameters can comprise at least one of transmission path parameters (e.g., IP address, port number, etc.), or routing configuration. The initial transmission parameters can further comprise other information.

[0224] Initial computing parameters, the initial computing parameters can comprise at least one of computing power configuration, model configuration, or dataset configuration. The initial computing parameters can further comprise other information.

[0225] The initial context of the terminal device is not limited to the above-mentioned parameters. The initial context of the terminal device can also include other parameters.

[0226] Optionally, the first entity comprises a storage unit. The storage unit can be used to store the context generated by the second entity for the first entity. That is, the processing unit can be separated from the storage unit. Optionally, the processing unit of the first entity can be used to store the context generated by the second entity for the first entity. That is, the processing unit can not be separated from the storage unit.

[0227] In the above-mentioned S426, the context generated by the second entity for the first entity is the context of the first terminal device. Therefore, S426 can also be regarded as the process of associating the first terminal device with the first entity. That is, S422, S424 and S426 can realize the association between the first terminal device and the first entity in the process of establishing the first entity.

[0228] In other possible implementations, S420 can comprise: the second entity associates the first entity with the first terminal device. Illustratively, S420 comprises S428. S428 can describe the process in which the second entity associates the existing first entity with the first terminal device.

[0229] In S428, the second entity sends the first indication information to the first entity. Correspondingly, the first entity receives the first indication information from the second entity.

[0230] Optionally, the first indication information is used to indicate that the first entity is associated with the first terminal device. As an example, the first indication information is used to indicate that the first entity provides the core network service (e.g., the first core network service) for the first terminal device. As another example, the first indication information is used to indicate that the capability of the first entity includes providing the core network service (e.g., the first core network service) for the first terminal device. As still another example, the first indication information is used to indicate that the first terminal device is a terminal device dedicated to the first entity.

[0231] Illustratively, in the case of initial access or cell handover of the first terminal device, in order to enable the first terminal device to quickly recover the core network service, the second entity can associate the existing first entity with the first terminal device.

[0232] In S430, the first terminal device receives the eighth information from the second entity. Correspondingly, the second entity sends the eighth information to the first terminal device.

[0233] Optionally, the eighth information is used to indicate that the first entity is used to provide the first core network service for the first terminal device. Optionally, the eighth information is used to indicate that the first terminal device is associated with the first entity.

[0234] In some possible implementation, the eighth information can be direct indication information, i.e., the eighth information contains information that the first entity is used to provide the first core network service for the first terminal device. In some other possible implementation, the eighth information can be indirect indication information, and the receiving end can determine, according to the eighth information, that the first entity is used to provide the first core network service for the first terminal device. For example, the eighth information is used to indicate the identity of the first entity. In this way, the first terminal device can know that the entity providing the first core network service for it is the first entity.

[0235] The embodiments of the present application do not limit the name of the eighth information. For example, the eighth information can also be called registration confirm, association response, or have other names.

[0236] Through the above scheme, the second entity can associate the first entity for the first terminal device, so that the first entity can provide the core network service for the first terminal device, thereby improving the quality of the service provided by the core network. Through the above scheme, the eighth information can inform the first terminal device that the first entity provides the core network service for the first terminal device, so that the first terminal device can request the first entity to provide the corresponding core network service, thereby reducing the time for the first terminal device to find a suitable entity to provide the corresponding core network service, and reducing the latency of requesting the core network service.

[0237] In some possible implementation, the first entity can perform at least one of the following operations (or in other words, the first entity has at least one of the following functions): maintaining the context of the first terminal device; implementing at least one core network service, the at least one core network service including the first core network service; or scheduling resources for executing the first core network service.

[0238] As an example, maintaining the context of the first terminal device can include maintaining the initial context generated by the second entity for the first entity. As another example, maintaining the context of the first terminal device can include maintaining the context of the first terminal device. For example, after the first entity executes the core network service, the context of the first terminal device will change compared to before the first entity executes the core network service. The first entity can update according to the changed context of the first terminal device, so that the context of the first terminal device in the storage unit of the first entity is always the latest version.

[0239] By way of example, implementing the first core network service can include executing at least one core network operation. Optionally, in addition to being able to implement the first core network service, the first entity can also be able to implement other core network services. In this way, the first entity can implement multiple core network services.

[0240] Optionally, the first entity is capable of scheduling resources (e.g., software resources or hardware resources) allocated by the second entity to perform the at least one core network operation, thereby implementing the core network service.

[0241] By the above solution, the first entity can maintain the context of the terminal device, implement the core network service, or schedule resources for implementing the core network service. The above solution defines some functions that the first entity has. The first entity having the function of maintaining the context of the terminal device can obtain the latest context locally, thereby correctly and efficiently implementing the core network service. The first entity having the function of scheduling resources can quickly schedule resources to perform the core network service, thereby improving the speed of performing the core network service.

[0242] In some possible implementation, the method 400 further includes: (S440) receiving, by the first entity, third information from the second entity. Correspondingly, the second entity sends the third information to the first entity.

[0243] Optionally, the third information is used for at least one of maintaining the context of the first terminal device, information of a location of the first entity, information of core network services that the first entity is capable of providing, or information of resources used for performing the core network services.

[0244] The term “maintaining” can include at least one of adding, deleting, modifying, or updating. As an example, maintaining the context of the first terminal device can include updating the context of the first terminal device. As another example, maintaining the information of core network services that the first entity is capable of providing can be creating a new core network service for the first entity, or deleting a core network service that the first entity has configured. For example, the second entity can configure the first entity with a function of providing a new core network service, or configure the first entity with a function of providing less core network services. As yet another example, maintaining the information of resources used for performing the core network services can be updating the information of resources used for performing the core network services. For example, the second entity can re-allocate software resources and / or hardware resources of the first entity. As another example, the second entity can adjust processing parameters (e.g., processing capability) of the first entity.

[0245] The information of the location of the first entity can be used to indicate the location of the first entity. Exemplarily, the information of the location of the first entity can include at least one of an access location of the first entity in a network topology, a spatial location of the first entity, or a geographical location of the first entity.

[0246] The information of the resource for performing the core network service can also be referred to as load information of the first entity. Optionally, the load information of the first entity can include processing capability possessed by a processing unit of the first entity. Exemplarily, the processing capability can include at least one of a type of processing task (for example, computation-intensive or input-output intensive) supported by the first entity, or processing load of each processing task. Wherein, the processing task can be a task created by the processing unit when the core network operation is specifically performed.

[0247] The present application does not limit the information maintained by the third information, and the third information can also be used to maintain other information, for example, a data structure of a processing task. Through the third information, the second entity can provide life cycle management for the first entity.

[0248] The present application does not limit the name of the third information, and the third information can also be referred to as maintenance information or have other names.

[0249] In some possible implementation manners, the third information can be sent by the second entity according to a request. For example, the second entity can determine to send the third information to the first entity according to a request of a terminal device (for example, the first terminal device or other terminal device). Or, the second entity sends the third information to the first entity in response to the request of the terminal device. For another example, the second entity can determine to send the third information to the first entity according to a request of other network element.

[0250] Through the above scheme, the third information can maintain the context of the first terminal device, the information of the location of the first entity, the information of the core network service that can be provided by the first entity, or the information of the resource for performing the core network service. In this way, the second entity can maintain the related functions of the first entity through the third information, so as to enable the first entity to provide more suitable core network services.

[0251] FIG. 5 is a schematic diagram of a state of the first entity provided by an embodiment of the present application. FIG. 5 is merely an example and does not constitute a limitation on the present application.

[0252] In some possible implementation manners, the third information is used to maintain the state of the first entity, and the state of the first entity includes at least one of the following: a first state, the first entity in the first state can provide all core network services configured by the second entity; a second state, the first entity in the second state does not store the context of the first terminal device; a third state, the first entity in the third state does not provide the core network service configured by the second entity; or a fourth state, the first entity in the fourth state can provide part of the core network services configured by the second entity.

[0253] The first state can also be referred to as an active state or by other names. The first entity in the first state can provide all core network services for the first terminal device. For example, the second entity configures the first entity to provide service #1, service #2 and service #3 for the first terminal device. The first entity in the active state can provide service #1, service #2 and service #3 for the first terminal device.

[0254] The second state can also be referred to as a type A idle state. Optionally, the first entity in the second state does not store a context of the first entity. The context of the first entity can include at least one of a software or hardware resource, a context of the first terminal device stored by the first entity, or a processing chain (e.g., a sequence of functions) implementing a core network service. For example, the first entity in the second state can not store the context of the first terminal device. Optionally, the first entity in the second state can store entity requirement information. The entity requirement information can be described above and will not be repeated here. The entity requirement information can also be referred to as creation configuration or setup information.

[0255] A possible scenario is that, due to the first terminal device being temporarily offline or being turned off, the third information can instruct the first entity in the first state to enter the second state. Optionally, the third information can instruct the first entity in the first state to release the context of the first entity configured by the second entity. Optionally, the third information can instruct the first entity in the first state to retain the entity requirement information.

[0256] It can be understood that, in the case that the first entity in the second state does not store the context of the first terminal device, the first entity does not perform any core network service.

[0257] The third state can also be referred to as a type B idle state or by other names. The first entity in the third state can turn off all configured core network services. Optionally, the first entity in the third state is used to store the context of the first entity. For example, the first entity in the third state is used to store the context of the first terminal device.

[0258] A possible scenario is that, due to the first terminal device being temporarily offline or being turned off, the third information can instruct the first entity in the first state to enter the third state. Optionally, the third information can instruct the first entity in the first state to retain the context of the first entity when entering the third state.

[0259] The fourth state can also be referred to as a type C dormant state or has other names. The first entity in the fourth state can shut down part of the configured core network service. For example, the first entity in the fourth state can only retain the function of providing a paging service. Optionally, the first entity in the fourth state is used to store the context of the first entity. For example, the first entity in the fourth state is used to store the context of the first terminal device.

[0260] A possible scenario is that the third information can indicate the first entity in the first state to enter the fourth state due to the first terminal device entering the dormant state or the inactive state, or the communication demand changes. Optionally, the third information can indicate the first entity in the first state to retain the context of the configured first entity when entering the fourth state. Optionally, the third information can indicate the first entity in the first state to retain the predefined part of the function (such as the paging function) when entering the fourth state.

[0261] The above describes possible implementations of the first entity in the first state entering the second state, the third state, and the fourth state. Those skilled in the art can understand that the description of the first entity in the second state, the third state, and the fourth state entering the first state is opposite to the above, and details are not repeated.

[0262] Optionally, the third information is used to release the first entity. For example, the third information can indicate to release the first entity in the first state, the second state, the third state, or the fourth state. Optionally, the released first entity does not store the context of the first entity. For example, the released first entity does not store the context of the first terminal device. Optionally, the released first entity does not store the entity demand information.

[0263] Through the above scheme, the third information can be used to maintain the state of the first entity, so that the quality of the core network service and the resource overhead can be balanced. For example, the first entity in the first state can provide all of the configured core network services; the first entity in the first state can improve the core network service of higher quality. For another example, the first entity in the fourth state can save more resource overhead than the first entity in the first state. For another example, the first entity in the third state can save more resource overhead than the first entity in the fourth state. For another example, the first entity in the second state can save more resource overhead than the first entity in the third state. In the case that the first entity has multiple states, the second entity can have multiple choices to balance the quality of the core network service and the resource overhead.

[0264] FIG. 6 is a schematic flowchart of another communication method 600 provided by the embodiments of the present application. The method 600 can be combined with the method 300 or the method 400. The optional operations in the method 600 are represented by dashed lines in FIG. 6. The method 600 is described below in combination with FIG. 6.

[0265] S610, the first terminal device sends eleventh information to the second entity. Correspondingly, the second entity receives the eleventh information from the first terminal device. The first terminal device is associated with the first entity.

[0266] Optionally, the eleventh information is used to request the first terminal device to further associate with an entity for providing the second core network service. Alternatively, the eleventh information is used to request the second entity to further associate, for the first terminal device, an entity for providing the second core network service. In this way, the second entity can associate, for the first terminal device, an entity for providing the second core network service based on the eleventh information. For example, the second entity can associate the first terminal device with a third entity. For another example, the second entity can configure the function of the first entity associated with the first terminal device, so that the first entity has the function of providing the second core network service.

[0267] Optionally, the second core network service is different from the first core network service. For example, the first core network service can be a paging service; and the second core network service can be a registration service.

[0268] Optionally, the eleventh information is further used to indicate entity requirement information. The entity requirement information can be used to indicate the requirement of the entity for providing the core network service.

[0269] The present application does not limit that the entity requirement information can only be indicated by the eleventh information. The entity requirement information can also be indicated by other information. In other words, the second entity can also obtain the entity requirement information through other information in addition to the eleventh information.

[0270] The present application does not limit the name of the eleventh information. For example, the eleventh information can also be called a registration request, an association request, or have other names.

[0271] Through the above scheme, the first terminal device can request to associate an entity for providing another core network service, so that the receiving end can perform corresponding operations based on the request.

[0272] In addition, S610 is an optional operation. In other possible implementation manners, the first terminal device can not send the eleventh information to the second entity, that is, it does not request to associate, for the first terminal device, an entity for providing the second core network service. In the case where S610 is not performed, the second entity can also actively associate, for the first terminal device, an entity for providing the second core network service.

[0273] S620, the second entity determines the third entity. The third entity is configured to provide the second core network service for the first terminal device. In other words, the third entity can provide the second core network service for the first terminal device.

[0274] In some possible implementation, S620 comprises: in response to the eleventh information, the second entity determines the third entity.

[0275] In some possible implementation, S620 comprises: the second entity registers (or creates) the third entity, which can provide the second core network service for the first terminal device. The description of the second entity registering (or creating) the third entity can be referred to the description of creating the first entity, for example, the description of S420, S422, S424, S426. Herein, the description is not repeated.

[0276] In some possible implementation, S620 comprises: the second entity registers (or creates) the third entity, which can provide the second core network service for the first terminal device. The description of the second entity registering (or creating) the third entity can be referred to the description of creating the first entity, for example, the description of S420, S422, S424, S426. Herein, the description is not repeated.

[0277] S630, the first terminal device receives the tenth information from the second entity. Correspondingly, the second entity sends the tenth information to the first terminal device. The first terminal device is associated with the first entity.

[0278] Optionally, the tenth information is used to indicate that the third entity is configured to provide the second core network service for the first terminal device. Optionally, the tenth information is used to indicate that the first terminal device is further associated with the third entity.

[0279] In some possible implementation, the tenth information can be direct indication information, i.e., the tenth information contains the information that the third entity is configured to provide the second core network service for the first terminal device. In another possible implementation, the tenth information can be indirect indication information, and the receiving end can determine that the third entity is configured to provide the second core network service for the first terminal device according to the tenth information. For example, the tenth information is used to indicate the identity of the third entity. In this way, the first terminal device can know that the entity providing the second core network service for it is the third entity.

[0280] The embodiments of the present application do not limit the name of the tenth information. For example, the tenth information can also be called registration confirmation, association response or have other names.

[0281] The first terminal device can simultaneously associate the first entity and the third entity. That is, the first terminal device can simultaneously associate multiple entities. In this way, the multiple entities can provide the same or different core network services for the first terminal device. The application does not limit the execution order of the third entity providing the second core network service for the first terminal device and the first entity providing the first core network service for the first terminal device.

[0282] Through the above scheme, the first terminal device can associate the third entity, so that the third entity can also provide core network services for the first terminal device, thereby further improving the quality of the services provided by the core network. In the case where the first terminal device associates multiple entities for providing core network services, different entities can provide different core network services. In this way, a specific entity can provide a specific core network service. On the one hand, an entity can only provide a part of the core network services, thereby reducing the deployment cost of the entity. On the other hand, an entity providing a specific core network service for a specific terminal device can increase the quality of the provided core network services.

[0283] FIG. 7 is a schematic flowchart of another communication method 700 provided by an embodiment of the application. The method 700 can be combined with the aforementioned method 300, method 400, or method 600. The optional operations in the method 700 are indicated by dashed lines in FIG. 7. The method 700 is described below in conjunction with FIG. 7.

[0284] S710, the second terminal device sends second indication information to the second entity. Correspondingly, the second entity receives the second indication information from the second terminal device.

[0285] Optionally, the second indication information is used to request the second terminal device to associate an entity for providing the first core network service. Alternatively, the second indication information is used to request the second entity to associate an entity for providing the first core network service for the second terminal device. In this way, the second entity can associate an entity for providing the first core network service for the second terminal device based on the second indication information. For example, the second entity can associate the second terminal device with the first entity. For another example, the second entity can associate the second terminal device with other entities capable of providing the first core network service.

[0286] Optionally, the second indication information is also used to indicate entity requirement information. The entity requirement information can be used to indicate the requirements of the entity for providing the core network service.

[0287] The application does not limit that the entity requirement information can only be indicated by the second indication information. The entity requirement information can also be indicated by other information. In other words, the second entity can also obtain the entity requirement information through other information in addition to the second indication information.

[0288] The embodiments of the present application do not limit the name of the second indication information. For example, the second indication information can also be referred to as a registration request, an association request, or have other names.

[0289] S720, the first entity receives the seventh information from the second entity. Correspondingly, the second entity sends the seventh information to the first entity.

[0290] The seventh information is used to indicate that the function of the first entity includes providing the first core network service for N terminal devices, and N is a positive integer. In other words, the seventh information can indicate that the function of the first entity includes providing the first core network service for multiple terminal devices. In other words, the seventh information can indicate that the first entity is associated with multiple terminal devices at the same time.

[0291] Optionally, the N terminal devices include the first terminal device. Optionally, the N terminal devices also include the second terminal device.

[0292] In some possible implementation manners, the seventh information can include the first indication information. That is, the seventh information is also used to indicate that the first entity is associated with the first terminal device. In some possible implementation manners, the seventh information can include third indication information, where the third indication information is used to indicate that the first entity is associated with the second terminal device.

[0293] Optionally, when N is greater than or equal to 2, the state of the first entity for the first terminal device is different from the state of the first entity for the second terminal device. For example, the state of the first entity for the first terminal device can be a first state, that is, all of the configured core network services can be provided; the state of the first entity for the second terminal device can be a second state, that is, none of the configured core network services is provided, and the part of the context of the first entity related to the second terminal device is not stored.

[0294] Optionally, N is less than or equal to a preset threshold. That is, the number of terminal devices associated with the first entity is limited. For example, the preset can be 1, 2, or 10, etc.

[0295] Through the above scheme, the first entity can be associated with one or more terminal devices. In the case where the first entity is associated with multiple terminal devices, the first entity can provide core network services for different terminal devices. In this way, one entity can provide core network services for multiple terminal devices, and the deployment cost of the entity can be reduced.

[0296] S730, the second entity sends the twelfth information to the second terminal device. Correspondingly, the second terminal device receives the twelfth information from the second entity.

[0297] Optionally, the twelfth information is used to indicate that the first entity is used to provide the first core network service for the second terminal device. Optionally, the twelfth information is used to indicate that the second terminal device is associated with the first entity. Alternatively, the twelfth information is used to indicate that the first entity is also associated with the second terminal device.

[0298] The first entity can be associated with the first terminal device and the second terminal device simultaneously. That is, the first entity can be associated with multiple terminal devices simultaneously. In other words, multiple terminal devices can share one entity. In this way, the entity can provide the same or different core network services for multiple terminal devices. The application does not limit the execution order of the first entity providing the first core network service for the first terminal device and the first entity providing the first core network service for the second terminal device shown in FIG. 7.

[0299] In some possible implementation manners, the twelfth information can be direct indication information, that is, the twelfth information contains the information that the first entity is used to provide the first core network service for the second terminal device. In other possible implementation manners, the twelfth information can be indirect indication information, and the receiving end can determine that the first entity is used to provide the first core network service for the second terminal device according to the twelfth information. For example, the twelfth information is used to indicate the identity of the first entity. In this way, the second terminal device can know that the entity providing the first core network service for it is the first entity.

[0300] The application does not limit the name of the twelfth information. For example, the twelfth information can also be called a registration confirmation, an association response, or have other names.

[0301] Through the above scheme, the twelfth information can inform the second terminal device that the first entity provides the core network service for the second terminal device, so that the second terminal device can request the first entity to provide the corresponding core network service, thereby reducing the time for the second terminal device to find a suitable entity to provide the corresponding core network service and reducing the latency of requesting the core network service.

[0302] FIG. 8 is a schematic flowchart of another communication method 800 provided by an embodiment of the application. The method 800 can be combined with the foregoing method 300, method 400, method 600, or method 700. The optional operations in the method 800 are indicated by dashed lines in FIG. 8. The method 800 is described below in combination with FIG. 8.

[0303] S802, the first entity receives sixth information from the second entity. Correspondingly, the second entity sends the sixth information to the first entity.

[0304] Optionally, the sixth information is used to indicate a condition triggering the migration.

[0305] In this application, transfer can be replaced by handover.

[0306] Optionally, the condition for triggering the transfer can be determined according to the assistance information. The assistance information can be submitted by the terminal device in a registration process. For example, the assistance information can include a delay requirement, a service type, or the like. Optionally, the method 800 includes determining, by the second entity, the condition for triggering the transfer.

[0307] The condition for triggering the transfer can be used to trigger the transfer. For example, in the case where the condition for triggering the transfer is met, the related entity can determine to transfer some functions to another entity. For example, the condition for triggering the transfer can include that a cell handover occurs to a first terminal device associated with the first entity, or a state of a node (for example, an access network device on a first satellite or other device) deployed by the first entity is updated (for example, the node is disabled, available resources change, an external interface is updated, or the like).

[0308] In some possible implementation manners, the sixth information can be direct indication information, that is, the sixth information contains the condition for triggering the transfer. In other possible implementation manners, the sixth information can be indirect indication information, and the receiving end can determine the condition for triggering the transfer according to the sixth information. For example, the receiving end can pre-acquire a mapping relationship between the condition for triggering the transfer and an identifier. The sixth information can contain the identifier, so that the receiving end can determine the condition for triggering the transfer corresponding to the identifier.

[0309] The name of the condition for triggering the transfer is not limited in this application. The condition for triggering the transfer can also be referred to as a transfer condition, a condition, an entity transfer condition, a function transfer condition, a service transfer condition, or other names.

[0310] The name of the sixth information is not limited in this application. The sixth information can also be referred to as a transfer configuration or other names.

[0311] Through the above scheme, the second entity can configure the condition for triggering the transfer through the sixth information, so that the first entity can perform the transfer at a suitable opportunity, thereby improving the continuity of core network services.

[0312] The above S802 is an optional operation. In other possible implementation manners, S802 can not be performed. For example, the condition for triggering the transfer can be predefined, and the second entity does not need to send it to the first entity. For another example, without any condition for triggering the transfer, the first entity can determine whether to perform the transfer by itself.

[0313] S804, the first entity determines to migrate the function of providing the first core network service for the first terminal device.

[0314] Optionally, the first entity can monitor whether the condition triggering the migration is satisfied. In the case that the condition triggering the migration is satisfied, the first entity can perform S804.

[0315] S810, the first entity sends fourth information to the second entity. Correspondingly, the second entity receives the fourth information from the first entity.

[0316] Optionally, the fourth information is used for requesting to migrate the function of providing the first core network service for the first terminal device.

[0317] In the above description, the term "migration" can be replaced by "switching". The term "migration" can be understood as that the first entity (which can be referred to as a source entity) is not associated with the first terminal device, and another entity (which can be referred to as a target entity) is associated with the first terminal device. The above-mentioned another entity can be a newly created entity, or can be an existing entity. After being associated with the first terminal device, the above-mentioned another entity can perform similar functions to the first entity previously associated with the first terminal device. For example, the first core network service is implemented.

[0318] Optionally, S810 comprises: in the case that the condition triggering the migration is satisfied, the first entity sends the fourth information to the second entity.

[0319] The name of the fourth information is not limited in the present application, and the fourth information can also be referred to as a migration request or have other names.

[0320] Through the above scheme, the first entity can request to migrate the function of providing the core network service for the terminal device associated therewith, so that the new entity can continue to provide the core network service for the terminal device, and the continuity of the core network service is improved.

[0321] S812, the first entity sends fifth information to the second entity. Correspondingly, the second entity receives the fifth information from the first entity.

[0322] Optionally, the fifth information is used for indicating the context of the first terminal device and / or entity requirement information. Optionally, the fifth information comprises the context of the first terminal device and / or entity requirement information.

[0323] Optionally, the fifth information and the fourth information can be carried in the same message. However, the present application is not limited thereto, and the fourth information and the fifth information can also be carried in different messages. Optionally, the fourth information is also used for indicating the context of the first terminal device and / or entity requirement information.

[0324] Optionally, S812 comprises: in case the condition triggering the migration is met, the first entity sending fifth information to the second entity.

[0325] As an example, the fifth information sent by the first entity in the second state can be used to indicate the entity requirement information. As mentioned before, the first entity in the second state can not store the context of the first terminal device, but only keep the entity requirement information. In this way, the fifth information sent by the first entity in the second state can be used to indicate the entity requirement information, but not the context of the first terminal device. The second entity can store the context of the first terminal device, so that the second entity can perform the subsequent migration according to the entity requirement information indicated by the fifth information and the context of the first terminal device stored by the second entity itself.

[0326] In some possible implementation, the first entity in the second state can send the fifth information out of the migration procedure. For example, the first entity in the second state can send the fifth information at other time.

[0327] As another example, the fifth information sent by the first entity in the first state, the third state or the fourth state can be used to indicate the context of the first terminal device. Optionally, the fifth information sent by the first entity in the first state, the third state or the fourth state can also be used to indicate the entity requirement information.

[0328] The name of the fifth information is not limited in the present application, and the fifth information can also be referred to as a transfer request or have other names.

[0329] S820, the second entity determines a fourth entity, the fourth entity is deployed on the second satellite, and the function of the fourth entity comprises providing the first core network service for the first terminal device. In other words, the fourth entity is associated with the first terminal device.

[0330] The fourth entity can also be referred to as a target entity. Correspondingly, the first entity can be referred to as a source entity.

[0331] In some possible implementation, S820 comprises: in response to the fourth information, the second entity determines the fourth entity. However, the present application is not limited thereto, and S820 can also be performed by the second entity actively without based on any request. In some possible implementation, S820 comprises: the second entity determines the fourth entity according to the fifth information. Optionally, S820 comprises: the second entity determines the fourth entity according to the context of the first terminal device.

[0332] In some possible implementation, S820 comprises: the second entity registers (or creates) a fourth entity, and a function of the fourth entity can comprise providing the first terminal device with the first core network service. The related description of the second entity registering (or creating) the fourth entity can be referred to the related description of creating the first entity, for example, the related description of S420, S422, S424, S426. Details are not described herein.

[0333] In some other possible implementation, S820 comprises: the second entity associates the fourth entity with the first terminal device. For example, the second entity can send a setup request to the fourth entity, and the setup request is used to request to associate the fourth entity with the first terminal device. The fourth entity can send a setup response to the second entity, and the setup response is used to indicate that the fourth entity has been associated with the first terminal device. Wherein, the setup request can carry the context of the first terminal device.

[0334] The other description of the second entity associating the fourth entity with the first terminal device can be referred to the related description of the second entity associating the first entity with the first terminal device, for example, the related description of S420, S428. Details are not described herein.

[0335] In some other possible implementation, the first entity can send the fifth information to the fourth entity. In some other possible implementation, the first terminal device can send the fifth information to the fourth entity.

[0336] S830, the second entity sends fourth indication information to the first entity. Correspondingly, the first entity receives the fourth indication information from the second entity.

[0337] Optionally, the fourth indication information is used to indicate that the function of providing the first terminal device with the first core network service is completed. Optionally, the fourth indication information is used to indicate that the fourth entity provides the first terminal device with the first core network service. Optionally, the fourth indication information is used to indicate that the first entity does not provide the first terminal device with the first core network service.

[0338] The name of the fourth indication information is not limited in the present application, and the fourth indication information can also be called transfer response or have other names.

[0339] S840, the first entity sends fifth indication information to the first terminal device. Correspondingly, the first terminal device receives the fifth indication information from the first entity.

[0340] Optionally, the fifth indication information is used to indicate that the migration of the function providing the first core network service for the first terminal device is completed. Optionally, the fifth indication information is used to indicate that the first entity does not provide the first core network service for the first terminal device. Optionally, the fifth information is used to indicate that the fourth entity provides the first core network service for the first terminal device.

[0341] Optionally, the first terminal device can send a service request to the fourth entity, and the service request can be used to request the first core network service. The fourth entity can provide the first core network service for the first terminal device.

[0342] The name of the fifth indication information is not limited in the present application, and the fifth indication information can also be referred to as a migration indication or have other names.

[0343] S850, the fourth entity sends sixth indication information to the first entity. Correspondingly, the first entity receives the sixth indication information from the fourth entity.

[0344] Optionally, the sixth indication information is used to indicate that the first entity is released. Optionally, the sixth indication information is used to indicate that the first entity does not provide the core network service for the first terminal device.

[0345] The name of the sixth indication information is not limited in the present application, and the sixth indication information can also be referred to as a release indication or have other names.

[0346] In some possible implementation manners, the first terminal device can send the sixth indication information to the first entity. In some possible implementation manners, the second entity can send the sixth indication information to the first entity.

[0347] Optionally, the first entity is released. For example, the first entity can be released according to the sixth indication information. For another example, the first entity can be released according to the fourth indication information.

[0348] Optionally, the second entity is a core network element. As an example, the second entity can be a core network element deployed on a satellite. For example, the second entity can be a core network element deployed on a LEO satellite (for example, the first satellite or other LEO satellites). As another example, the second entity can be a core network element deployed on the ground.

[0349] Optionally, the second entity is a management function entity, i.e., the second entity can not be a core network element. The management function entity can perform a management function of the core network element on the first entity. For example, the management function entity can create the first entity; maintain the first entity; migrate the first entity; or release the first entity. For another example, the management function entity can create a context of the first entity; maintain the context of the first entity; migrate the context of the first entity; or release the context of the first entity.

[0350] Optionally, the management function of the management function entity is indicated by the core network element. For example, the core network element can authorize the management function entity to register, migrate or release the first entity. For another example, the core network element can configure the management function entity with the function of registering, migrating or releasing the first entity.

[0351] Optionally, the second entity is a management function entity deployed on a satellite. For example, the second entity can be deployed on the first satellite. For another example, the second entity can be deployed on another satellite.

[0352] Optionally, the management function of the management function entity is associated with a location. For example, the core network element indicates that the management function entity has the management function under certain location conditions. The management function entity can manage the first entity without intervention of the core network element within a set of access points or a geographical area configured by the core network element.

[0353] Through the above scheme, the second entity can be deployed on the satellite where the first entity is located, so as to more quickly manage the first entity and improve the continuous service capability of the first entity.

[0354] The following describes a device embodiment corresponding to the method embodiment of the present application. The following only briefly describes the device, and the specific implementation steps and details of the scheme can be referred to the foregoing method embodiment.

[0355] To implement the functions in the method provided in the present application, the communication device can include hardware structures and / or software modules to implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a certain function in the above functions is implemented in the form of hardware structure, software module, or hardware structure plus software module depends on the specific application of the technical solution and the design constraint conditions.

[0356] FIG. 9 is a schematic block diagram of a communication device 1000 according to an embodiment of the present application. The communication device 1000 includes a processor 1010 and a communication interface 1020. Optionally, the processor 1010 and the communication interface 1020 can be connected to each other through a bus. The communication device 1000 can be the first entity, the first terminal device, or the second entity.

[0357] Optionally, the communication apparatus 1000 can further include a memory 1040. The memory 1040 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), a cache, an erasable programmable read only memory (EPROM), a synchronous dynamic random access memory (SDRAM), a hard disk drive (HDD), a solid-state drive (SSD), or a compact disc read-only memory (CD-ROM). The memory 1040 is used to store relevant instructions and / or data. The memory 1040 can be integrated with the processor 1010 or separately arranged.

[0358] Exemplarily, in the case that the communication apparatus 1000 is a first entity, the memory 1040 can be used to store a context of a first terminal device.

[0359] The processor 1010 can be one or more central processing units (CPUs). In the case that the processor 1010 is a CPU, the CPU can be a single-core CPU or a multi-core CPU. The processor 1010 can be a signal processor, a chip, or other integrated circuits that can implement the method of the present application, or a part of the foregoing processor, chip, or integrated circuit for processing functions. In addition, the communication interface 1020 can also be an input / output interface for input or output of signals or data, or an input / output circuit.

[0360] Exemplarily, in the case that the communication apparatus 1000 is a first entity, the processor 1010 is configured to perform the following operations: receiving first information from a first terminal device, a function of the first entity includes providing a first core network service for the first terminal device, the first information is used to request the first core network service, wherein the first core network service is implemented by the first entity; and sending second information to the first terminal device, the second information is used to indicate an execution result of the first core network service.

[0361] Exemplarily, the communication apparatus 1000 is a first terminal device, and the processor 1010 is configured to perform the following operations: sending first information to a first entity, the first entity being deployed on a first satellite and having a function of providing a first core network service for the first terminal device, the first information being used to request the first core network service, and the first core network service being implemented by the first entity; and receiving second information from the first entity, the second information being used to indicate an execution result of the first core network service.

[0362] Exemplarily, the communication apparatus 1000 is a second entity, and the processor 1010 is configured to perform the following operations: determining a first entity, the first entity being deployed on a first satellite and having a function of providing a first core network service for a first terminal device, wherein the first core network service is implemented by the first entity; and sending eighth information to the first terminal device, the eighth information being used to indicate that the first entity is used to provide the first core network service for the first terminal device.

[0363] The above description is only exemplary. The communication apparatus 1000 is responsible for performing the method or steps related to the first entity, the first terminal device or the second entity in the foregoing method embodiments.

[0364] In a possible implementation, the communication interface 1020 can be a transceiver. The transceiver can include a transmitter and a receiver, the transmitter being configured to perform the sending operation, and the receiver being configured to perform the receiving operation. For example, the processor 1010 is configured to control the transceiver to receive and / or send signals.

[0365] In a possible implementation, the communication interface 1020 can also be a communication circuit, a pin, an input / output interface, a bus, etc.

[0366] The communication apparatus 1000 can include a transmitter but not a receiver. Alternatively, the communication apparatus 1000 can include a receiver but not a transmitter. Whether the communication apparatus 1000 includes the sending action and the receiving action in the above-described scheme can be determined according to the implementation.

[0367] The above description is only exemplary. The specific content can be referred to the content shown in the foregoing method embodiments. The implementation of each operation in FIG. 9 can also correspond to the description of the corresponding method embodiments shown in FIGS. 3 to 8.

[0368] For example, the communication apparatus 1000 can be configured to perform the scheme shown in FIGS. 3 to 8.

[0369] Exemplarily, the communication apparatus 1000 is a first entity, and the communication interface 1020 can be configured to receive the first information and send the second information.

[0370] Exemplarily, the communication apparatus 1000 is a first terminal device, and the communication interface 1020 can be configured to transmit the first information and receive the second information.

[0371] Exemplarily, the communication apparatus 1000 is a second entity, and the communication interface 1020 can be configured to transmit the eighth information.

[0372] For other implementation manners, refer to the detailed description of the embodiments shown in the foregoing FIG. 3 to FIG. 8, which will not be repeated here. It should be understood that the specific process of each component performing the corresponding process has been described in detail in the foregoing method embodiments, and will not be repeated here for the sake of brevity.

[0373] FIG. 10 is a schematic block diagram of another communication apparatus 1100 according to an embodiment of the present application. The communication apparatus 1100 can be a first entity, a first terminal device, or a second entity, or can be a chip or a module in the first entity, the first terminal device, or the second entity, and is configured to implement the method according to the embodiments shown in FIG. 3 to FIG. 8. For details, refer to the related description in the foregoing method embodiments.

[0374] The communication apparatus 1100 includes a transceiver unit 1110. The transceiver unit 1110 is exemplarily described as follows.

[0375] The transceiver unit 1110 can include a transmitting unit and a receiving unit. The transmitting unit is configured to perform the transmitting action of the communication apparatus, and the receiving unit is configured to perform the receiving action of the communication apparatus. For the sake of brevity, the transmitting unit and the receiving unit are combined into one transceiver unit in the embodiments of the present application. This is uniformly described here, and will not be repeated hereinafter. The transceiver unit 1110 can implement the corresponding communication function. The transceiver unit 1110 can also be referred to as a communication interface or a communication module.

[0376] The communication apparatus 1100 can include a transmitting unit and not include a receiving unit. Alternatively, the communication apparatus 1100 can include a receiving unit and not include a transmitting unit. Specifically, whether the transmitting unit and the receiving unit are included in the communication apparatus 1100 depends on whether the transmitting action and the receiving action are included in the above-mentioned scheme performed by the communication apparatus 1100.

[0377] Exemplarily, the transceiver unit 1110 is configured to receive the first information, etc.

[0378] Optionally, the communication apparatus 1100 can further include a processing unit 1120, which is configured to perform the processing, coordination, etc. involved in the communication apparatus 1100.

[0379] Exemplarily, the transceiver unit 1110 is configured to transmit the first information, etc.

[0380] Optionally, the communication apparatus 1100 can further include a processing unit 1120, which is configured to perform the processing, coordination, etc. involved in the communication apparatus 1100.

[0381] Exemplarily, the transceiver 1110 is configured to transmit the eighth information, etc.

[0382] Optionally, the communication apparatus 1100 further includes a processing unit 1120, which is configured to perform the content related to processing, coordination, etc. of the communication apparatus 1100. Exemplarily, the processing unit 1120 is configured to determine the first entity, etc.

[0383] The above description is only exemplary. The communication apparatus 1100 will be responsible for performing the related method or steps in the foregoing method embodiments.

[0384] Optionally, the communication apparatus 1100 further includes a storage unit 1130, which is configured to store programs or codes for performing the foregoing methods. Alternatively, the storage unit 1130 can be configured to store instructions and / or data, and the processing unit 1120 can read the instructions and / or data in the storage unit 1130, so that the communication apparatus 1100 implements the foregoing method embodiments. For example, the communication apparatus 1100 can be configured to perform the schemes shown in FIG. 3 to FIG. 8.

[0385] Exemplarily, the transceiver 1110 can be configured to receive the first information, and transmit the second information.

[0386] Exemplarily, the transceiver 1110 can be configured to transmit the first information, and receive the second information.

[0387] Exemplarily, the processing unit 1120 can be configured to determine the first entity, and the transceiver 1110 can be configured to transmit the eighth information.

[0388] For other implementation manners, refer to the detailed description of the embodiments shown in the foregoing FIG. 3 to FIG. 8, which will not be repeated here. It should be understood that the specific process of each component performing the above corresponding process has been described in detail in the foregoing method embodiments, and will not be repeated here for the sake of brevity.

[0389] When the communication apparatus 1000 in FIG. 9 is a chip, the communication interface 1020 can be a transceiver, an input / output circuit or a communication interface of the chip. The processor 1010 can be an integrated processor on the chip, or a microprocessor, or an integrated circuit. The transmitting operation of the first entity, the first terminal device or the second entity in the foregoing method embodiments can be understood as the output of the chip, and the receiving operation of the first entity, the first terminal device or the second entity in the foregoing method embodiments can be understood as the input of the chip.

[0390] When the communication apparatus 1100 in FIG. 10 is a chip, the transceiver unit 1110 can be a transceiver, an input / output circuit or a communication interface of the chip. The processing unit 1120 can be an integrated processor, or a microprocessor, or an integrated circuit integrated on the chip. The transmitting operation of the first entity, the first terminal device or the second entity in the method embodiments can be understood as the output of the chip, and the receiving operation of the first entity, the first terminal device or the second entity in the method embodiments can be understood as the input of the chip.

[0391] The application further provides a chip comprising a processor, configured to invoke and run instructions stored in a memory, so that a communication apparatus in which the chip is installed performs the method in any of the examples.

[0392] The application further provides another chip comprising an input interface, an output interface and a processor, which are connected through internal connection paths. The processor is configured to execute code in a memory, and when the code is executed, the processor is configured to perform the method in any of the examples. Optionally, the chip further comprises a memory configured to store a computer program or code.

[0393] The application further provides a processor configured to be coupled with a memory, and configured to perform the method and the function of the communication apparatus in any of the embodiments, or configured to perform the method and the function of the first entity, the first terminal device or the second entity in any of the embodiments.

[0394] In another embodiment of the application, a computer program product containing a computer program or instructions is provided, and when the computer program product is run on a computer, the method of the foregoing embodiments is implemented.

[0395] The application further provides a computer program, and when the computer program is run on a computer, the method of the foregoing embodiments is implemented.

[0396] In another embodiment of the application, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program, and when the computer program is executed by a computer, the method of the foregoing embodiments is implemented.

[0397] The application further provides a communication system comprising a first entity, a first terminal device and a second entity. The first entity, the first terminal device and the second entity are respectively configured to perform the method performed by the first entity, the first terminal device and the second entity in the foregoing embodiments.

[0398] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed 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 the present application.

[0399] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0400] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0401] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

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

[0403] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

Claims

1. A communication method, characterized in that: The method is applied to a first entity, where the first entity is deployed on a first satellite, and includes: receiving first information from a first terminal device, where a function of the first entity includes providing a first core network service for the first terminal device, and the first information is used to request the first core network service, wherein the first core network service is implemented by the first entity; Send second information to the first terminal device, where the second information is used to indicate the execution result of the first core network service.

2. The method according to claim 1, characterized in that The first entity is used to store the context of the first terminal device.

3. The method according to claim 1 or 2, characterized in that The method further comprises: Receive seventh information from the second entity, where the seventh information is used to indicate that the function of the first entity includes providing the first core network service to N terminal devices, where N is a positive integer and the N terminal devices include the first terminal device.

4. The method according to any one of claims 1 to 3, characterized in that The first entity is used to execute the first core network service according to the context of the first terminal device.

5. The method according to any one of claims 1 to 4, characterized in that The first entity is capable of performing at least one of the following operations: maintaining a context of the first terminal device; implementing at least one core network service, the at least one core network service including the first core network service; or, Scheduling resources for executing the first core network service.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Receive third information from the second entity, where the third information is used to maintain at least one of the context of the first terminal device, information about the location of the first entity, information about core network services that the first entity can provide, or information about resources used to execute core network services.

7. The method according to claim 6, characterized in that The third information is used to maintain the state of the first entity, where the state of the first entity includes at least one of the following: a first state, wherein the first entity in the first state is capable of providing all core network services configured by the second entity; a second state, in which the first entity does not store the context of the first terminal device; a third state, in which the first entity does not provide the core network service configured by the second entity; or, A fourth state: the first entity in the fourth state can provide part of the core network services configured by the second entity.

8. The method according to claim 6 or 7, characterized in that The second entity is deployed on the first satellite, and / or the second entity is a core network element.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: Send fourth information to the second entity, where the fourth information is used to request migration of the function of providing the first core network service to the first terminal device.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: Send fifth information to the second entity, where the fifth information is used to indicate the context and / or entity requirement information of the first terminal device.

11. The method according to claim 9 or 10, characterized in that The method further comprises: Sixth information is received from the second entity, where the sixth information is used to indicate a condition for triggering migration.

12. A communication method, characterized in that: The method is applied to a first terminal device, and includes: Sending first information to a first entity, where a function of the first entity includes providing a first core network service for the first terminal device, the first entity is deployed on a first satellite, the first information is used to request the first core network service, and the first core network service is implemented by the first entity; Receive second information from the first entity, where the second information is used to indicate an execution result of the first core network service.

13. The method according to claim 12, characterized in that The method further comprises: Receive eighth information from the second entity, where the eighth information is used to instruct the first entity to provide the first core network service for the first terminal device.

14. The method according to claim 13, characterized in that The method further comprises: Ninth information is sent to the second entity, where the ninth information is used to request association with the entity for providing the first core network service for the first terminal device.

15. The method according to any one of claims 12 to 14, characterized in that The method further comprises: Receive tenth information from the second entity, where the tenth information is used to instruct the third entity to provide a second core network service for the first terminal device, where the first core network service is different from the second core network service.

16. The method according to claim 15, characterized in that The method further comprises: An eleventh message is sent to the second entity, where the eleventh message is used to request that the first terminal device also be associated with an entity used to provide the second core network service.

17. The method according to any one of claims 13 to 16, characterized in that The second entity is deployed on the first satellite, and / or the second entity is a core network element.

18. A communication method, characterized in that: The method is applied to a second entity, where the second entity is deployed on a first satellite, and / or the second entity is a core network element. The method includes: Determining a first entity, where the first entity is deployed on the first satellite, and a function of the first entity includes providing a first core network service for a first terminal device, wherein the first core network service is implemented by the first entity; Send eighth information to the first terminal device, where the eighth information is used to instruct the first entity to provide the first core network service for the first terminal device.

19. The method according to claim 18, characterized in that The method further comprises: Receive ninth information from the first terminal device, where the ninth information is used to request association with the first terminal device with an entity for providing the first core network service.

20. The method according to claim 18 or 19, characterized in that The first entity is capable of performing at least one of the following operations: maintaining a context of the first terminal device; implementing at least one core network service, the at least one core network service including the first core network service; or, Scheduling resources for executing the first core network service.

21. The method according to any one of claims 18 to 20, characterized in that The method further comprises: Send third information to the first entity, where the third information is used to maintain at least one of the context of the first terminal device, information about the location of the first entity, information about the core network services that the first entity can provide, or information about resources used to execute core network services.

22. The method according to claim 21, characterized in that The third information is used to maintain the state of the first entity, where the state of the first entity includes at least one of the following: a first state, wherein the first entity in the first state is capable of providing all core network services configured by the second entity; a second state, in which the first entity does not store the context of the first terminal device; a third state, in which the first entity does not provide the core network service configured by the second entity; or, A fourth state: the first entity in the fourth state can provide part of the core network services configured by the second entity.

23. The method according to any one of claims 18 to 22, characterized in that The method further comprises: Seventh information is sent to the first entity, where the seventh information is used to indicate that the function of the first entity includes providing the first core network service to N terminal devices, where N is a positive integer and the N terminal devices include the first terminal device.

24. The method according to any one of claims 18 to 23, characterized in that The method further comprises: Twelfth information is sent to the second terminal device, where the twelfth information is used to instruct the first entity to provide the first core network service for the second terminal device.

25. The method according to any one of claims 18 to 24, characterized in that The method further comprises: A tenth information is sent to the first terminal device, where the tenth information is used to instruct a third entity to provide a second core network service for the first terminal device, where the first core network service is different from the second core network service.

26. The method according to claim 25, characterized in that The method further comprises: Receive eleventh information from the first terminal device, where the eleventh information is used to request the first terminal device to also associate with an entity used to provide the second core network service.

27. The method according to any one of claims 18 to 26, characterized in that The method further comprises: Receive fourth information from the first entity, where the fourth information is used to request migration of the function of providing the first core network service to the first terminal device.

28. The method according to any one of claims 18 to 27, characterized in that The method further comprises: Fifth information is received from the first entity, where the fifth information is used to indicate context and / or entity requirement information of the first terminal device.

29. The method according to claim 27 or 28, characterized in that The method further comprises: A fourth entity is determined, where the fourth entity is deployed on the second satellite, and a function of the fourth entity includes providing the first core network service for the first terminal device.

30. The method according to any one of claims 27 to 29, characterized in that The method further comprises: Sending sixth information to the first entity, where the sixth information is used to indicate a condition for triggering migration.

31. A communication device, characterized in that: The method comprises at least one module or at least one unit, wherein the at least one module or the at least one unit is used to perform the method according to any one of claims 1 to 11, or the at least one module or the at least one unit is used to perform the method according to any one of claims 12 to 17, or the at least one module or the at least one unit is used to perform the method according to any one of claims 18 to 30.

32. A communication device, characterized in that: include: A processor configured to, by executing a computer program or instruction, cause the method according to any one of claims 1 to 11 to be performed, or cause the method according to any one of claims 12 to 17 to be performed, or cause the method according to any one of claims 18 to 30 to be performed.

33. The communication device according to claim 32, wherein: The communication device further comprises a memory configured to store the computer program or the instructions.

34. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or instructions. When the computer program or the instructions are run on a computer, the method according to any one of claims 1 to 11 is executed, or the method according to any one of claims 12 to 17 is executed, or the method according to any one of claims 18 to 30 is executed.

35. A computer program product, characterized in that The method comprises a computer program or an instruction. When the computer program or the instruction is executed, the method according to any one of claims 1 to 11 is implemented, or the method according to any one of claims 12 to 17 is implemented, or the method according to any one of claims 18 to 30 is implemented.

36. A chip, characterized in that: include: A processor configured to, by executing a computer program or instruction, cause the method according to any one of claims 1 to 11 to be performed, or cause the method according to any one of claims 12 to 17 to be performed, or cause the method according to any one of claims 18 to 30 to be performed.

Images