Network access method, communication device, and storage medium

Abstract

Embodiments of the present disclosure provide a network access method, a communication device, and a storage medium. The network access method executed by a first device comprises: receiving a first message sent by a second network function, wherein the first message is a message in a first network attachment process executed by a user equipment (UE), the first network uses a first access and supports a storage and forwarding function, and the first access is satellite access; and sending a second message to the second network function, the second message comprising first information, and the first information being used for indicating that the UE has been attached to a second network, or the first information being used for indicating that the UE is refused to be attached to the first network.

Description

Network access method, communication device and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and particularly relates to a network access method, a communication device and a storage medium. BACKGROUND

[0002] A communication network includes a terrestrial network (TN) and a non-terrestrial network (NTN). All network functions of the TN are located on the ground. In the NTN network, part of the network functions can be deployed on a satellite, for example, a base station or a mobile management entity (MME) is deployed on a satellite.

[0003] SUMMARY

[0004] The present disclosure provides a network access method, a communication device and a storage medium.

[0005] According to a first aspect of the present disclosure, a network access method is provided, which is performed by a first network function, and the method comprises: receiving a first message sent by a second network function, the first message being a message in a first network attachment process performed by a UE, the first network using a first access and supporting a store-and-forward function; the first access is a satellite access; sending a second message to the second network function, the second message containing first information; the first information is used to indicate that the UE has attached to a second network, or the first information is used to indicate that the UE is rejected to attach to the first network.

[0006] According to a second aspect of the present disclosure, a network access method is provided, which is performed by a second network function, and the method comprises: sending a first message to a first network function, the first message being a message in a first network attachment process performed by a user equipment (UE), the first network using a first access and supporting a store-and-forward function; the first access is a satellite access; receiving a second message sent by the first network function, the second message containing first information; the first information is used to indicate that the UE has attached to a second network, or the first information is used to indicate that the UE is rejected to attach to the first network.

[0007] According to a third aspect of embodiments of the present disclosure, a network access method is provided, wherein the method is performed by a third network function of a first network, and the method comprises: receiving a third message sent by a second network function, the third message being used to indicate that a user equipment (UE) has attached to a second network or to indicate that the UE is rejected to attach to the first network; the first network uses a first access and supports a store-and-forward function; the first access is a satellite access; and deleting attachment information of the UE in the first network.

[0008] According to a fourth aspect of embodiments of the present disclosure, a first network function is provided, and the first network function comprises:

[0009] a receiving module configured to receive a first message sent by a second network function, the first message being a message in a first network attachment process performed by a user equipment (UE), the first network using a first access and supporting a store-and-forward function; the first access being a satellite access;

[0010] a sending module configured to send a second message to the second network function, the second message containing first information; the first information being used to indicate that the UE has attached to a second network, or the first information being used to indicate that the UE is rejected to attach to the first network.

[0011] According to a fifth aspect of embodiments of the present disclosure, a second network function is provided, and the second network function comprises:

[0012] a sending module configured to send a first message to a first network function, the first message being a message in a first network attachment process performed by a user equipment (UE), the first network using a first access and supporting a store-and-forward function; the first access being a satellite access;

[0013] a receiving module configured to receive a second message sent by the first network function, the second message containing first information; the first information being used to indicate that the UE has attached to a second network, or the first information being used to indicate that the UE is rejected to attach to the first network.

[0014] According to a sixth aspect of embodiments of the present disclosure, a third network function is provided, and the third network function comprises:

[0015] a receiving module configured to receive a third message sent by a second network function, the third message being used to indicate that a user equipment (UE) has attached to a second network or to indicate that the UE is rejected to attach to a first network; the first network using a first access and supporting a store-and-forward function; the first access being a satellite access;

[0016] a processing module configured to delete attachment information of the UE in the first network.

[0017] According to a seventh aspect of the embodiments of the present disclosure, a communication system is provided, wherein the communication system comprises a first network function, a second network function, and a third network function;

[0018] The first network function is configured to perform the network access method according to any of the technical solutions of the first aspect;

[0019] The second network function is configured to perform the network access method according to any of the technical solutions of the second aspect;

[0020] The third network function is configured to perform the network access method according to any of the technical solutions of the third aspect.

[0021] According to an eighth aspect of the embodiments of the present disclosure, a communication device is provided, wherein the communication device comprises one or more processors; and the processor is configured to invoke instructions to cause the communication device to perform the network access method according to any of the technical solutions of the first aspect to the third aspect.

[0022] According to a ninth aspect of the embodiments of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device is caused to perform the network access method according to any of the technical solutions of the first aspect to the third aspect.

[0023] According to a tenth aspect of the embodiments of the present disclosure, a program product is provided, wherein the program product comprises a computer program, and when the computer program is executed on a communication device, the communication device is caused to implement the network access method according to any of the technical solutions of the first aspect to the third aspect.

[0024] The technical solution provided by the embodiments of the present disclosure is that, when it is determined that the UE has completed the attachment to the second network, the first network function rejects the attachment of the UE to the first network, thereby solving the problem of access exception caused by the network performing the store-and-forward function when the UE accesses the satellite network.

[0025] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and are not limiting on the embodiments of the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0026] The accompanying drawings, which are incorporated into and form part of the specification, illustrate the embodiments consistent with the present disclosure and, together with the specification, serve to explain the principles of the embodiments of the present disclosure.

[0027] FIG. 1A is a schematic diagram of an architecture of a communication system according to an exemplary embodiment;

[0028] FIG. 1B is a schematic diagram of an architecture of a communication system according to an exemplary embodiment;

[0029] FIG. 1C is a schematic diagram of an architecture of a communication system, according to an example embodiment;

[0030] FIG. 1D is a schematic diagram of an access procedure of a UE, according to an example embodiment;

[0031] FIG. 2A is a schematic diagram of interactions of a network access method, according to an example embodiment;

[0032] FIG. 2B is a schematic diagram of interactions of a network access method, according to an example embodiment;

[0033] FIG. 3A is a schematic diagram of a flow of a network access method, according to an example embodiment;

[0034] FIG. 3B is a schematic diagram of a flow of a network access method, according to an example embodiment;

[0035] FIG. 4A is a schematic diagram of a flow of a network access method, according to an example embodiment;

[0036] FIG. 4B is a schematic diagram of a flow of a network access method, according to an example embodiment;

[0037] FIG. 5 is a schematic diagram of a flow of a network access method, according to an example embodiment;

[0038] FIG. 6A is a schematic diagram of a flow of a network access method, according to an example embodiment;

[0039] FIG. 6B is a schematic diagram of a flow of a network access method, according to an example embodiment;

[0040] FIG. 7A is a schematic diagram of a structure of a first network function, according to an example embodiment;

[0041] FIG. 7B is a schematic diagram of a structure of a second network function, according to an example embodiment;

[0042] FIG. 7C is a schematic diagram of a structure of a third network function, according to an example embodiment;

[0043] FIG. 8A is a schematic diagram of a structure of a communication device, according to an example embodiment;

[0044] FIG. 8B is a schematic diagram of a structure of a chip, according to an example embodiment. DETAILED DESCRIPTION

[0045] Embodiments of the present disclosure provide a network access method, a communication device, a communication system, and a storage medium.

[0046] The first aspect provides a network access method, wherein the method is performed by a first network function, and the method comprises the following steps:

[0047] receiving a first message sent by a second network function, the first message being a message in a first network attachment process performed by a user equipment (UE), the first network using a first access and supporting a store-and-forward function; the first access being a satellite access;

[0048] sending a second message to the second network function, the second message containing first information; the first information being used to indicate that the UE has attached to the second network, or the first information being used to indicate that the UE is rejected to attach to the first network.

[0049] In this way, the first network function determines that the UE has completed the attachment to the second network, and rejects the attachment of the UE to the first network, thereby solving the problem of abnormal access of the UE to the satellite network due to the store-and-forward function performed by the network.

[0050] In some embodiments of the first aspect, when the first network and the second network are the same network, a second access used by the second network is different from the first access.

[0051] In this way, the first attachment and the second attachment can correspond to the same network but use different accesses, and in this case, in order to avoid repeated attachment, the first attachment is rejected or the information related to the first attachment is deleted by the second message in the case where it is detected that the second attachment has been completed.

[0052] In some embodiments of the first aspect, the method further comprises: determining whether the UE has attached to the second network according to second information, the second information comprising at least one of the following: identification information of the UE; first time information, the first time information being used to indicate a time at which the first network rejects the attachment request of the UE, or the time information being used to indicate a time at which the UE requests to attach to the first network; and attachment information of the UE to the second network.

[0053] In this way, the first network function determines whether the UE has attached to the second network according to the second information, and the determination of whether the UE has attached to the second network is simple and convenient.

[0054] In some embodiments of the first aspect, the attachment information of the UE to the second network comprises at least one of the following: identification information of the UE; first network information, the first network information comprising at least identification information of a mobility management function (MME) used by the UE to attach to the second network; and second network information, the second network information comprising at least information of an access network corresponding to the second network to which the UE attaches.

[0055] The information content of the attachment information of the second network is illustrated based on the above scheme, and the information content is not limited to the above illustration in actual implementation.

[0056] In some embodiments of the first aspect, determining whether the UE has attached to the second network according to the second information comprises at least one of: determining whether the UE has attached to the second network after a time indicated by the first time information according to the first time information; determining whether the UE has attached to the second network according to whether there is UE attachment information of the UE to the second network.

[0057] The above scheme defines how to determine whether the UE has attached to the second network according to the second information, and has the characteristics of simple implementation.

[0058] In some embodiments of the first aspect, the first network function is a home subscriber server (HSS), and the second network function is a first mobility management function (MME), or the first network function is a first mobility management function, and the second network function is a second mobility management function, wherein the second mobility management function is deployed on a satellite, and the first mobility management function is deployed on the ground.

[0059] The above scheme illustrates the first network function and the second network function, and the implementation is not limited to the above examples.

[0060] In some embodiments of the first aspect, the first network function is a first mobility management function, and the second network function is a second mobility management function, and the first message is used for a UE attachment request in the first network.

[0061] The above scheme gives the correspondence between the specific message content of the first message and the specific types of the first network function and the second network function.

[0062] The second aspect provides a network access method, wherein the method is performed by a second network function, and the method comprises:

[0063] sending a first message to a first network function, the first message being a message in a first network attachment process of a user equipment (UE), the first network using a first satellite access and supporting a store-and-forward function;

[0064] receiving a second message sent by the first network function, the second message containing first information; the first information being used to indicate that the UE has attached to a second network, or to indicate that the UE is rejected to attach to the first network.

[0065] In some embodiments of the second aspect, when the first network and the second network are the same network, a second access used by the second network is different from a first access used by the first network.

[0066] In some embodiments of the second aspect, the first network function is a home subscriber server (HSS), and the second network function is a first mobility management function (MME), and the method further comprises: deleting attachment information of the first attachment.

[0067] In some embodiments of the second aspect, the method further includes:

[0068] sending, to the third network function, a third message, the third message being used to indicate that the UE has attached to the second network or to indicate that the UE is rejected to attach to the first network, so that the third network function deletes the attachment information of the UE in the first network;

[0069] The third network function is a second mobility management function.

[0070] In some embodiments of the second aspect, the first network function is a first mobility management function, and the second network function is a second mobility management function, and the method further includes: deleting the attachment information of the UE in the first network.

[0071] In some embodiments of the second aspect, the method further includes:

[0072] sending, to the UE, a fourth message, the fourth message being used to reject the UE to attach to the first network.

[0073] The third aspect provides a network access method, wherein the method is performed by a third network function of a first network, and the method includes:

[0074] receiving a third message sent by a second network function, the third message being used to indicate that a user equipment (UE) has attached to the second network or to indicate that the UE is rejected to attach to the first network; the first network uses a first access and supports a store-and-forward function; and the first access is a satellite access;

[0075] deleting the attachment information of the UE in the first network.

[0076] In some embodiments of the third aspect, the method further includes:

[0077] sending, to the UE, a fifth message, the fifth message being used to reject the UE to attach to the first network.

[0078] The fourth aspect provides a first network function, which includes:

[0079] a receiving module configured to receive a first message sent by a second network function, the first message being a message in a first network attachment process of a user equipment (UE), the first network using a first access and supporting a store-and-forward function; and the first access being a satellite access;

[0080] a sending module configured to send, to the second network function, a second message, the second message containing first information; the first information being used to indicate that the UE has attached to the second network, or the first information being used to indicate that the UE is rejected to attach to the first network.

[0081] The fifth aspect provides a second network function, which includes:

[0082] The sending module is configured to send a first message to the first network function, the first message being a message in a first network attachment procedure performed for a user equipment (UE), the first network using a first satellite access and supporting a store-and-forward function;

[0083] The receiving module is configured to receive a second message sent by the first network function, the second message containing first information; the first information being used to indicate that the UE has attached to a second network or to indicate that the UE is rejected to attach to the first network.

[0084] The sixth aspect provides a third network function, comprising:

[0085] The receiving module is configured to receive a third message sent by the second network function, the third message being used to indicate that the UE has attached to the second network or to indicate that the UE is rejected to attach to the first network; the first network using a first access and supporting a store-and-forward function; the first access being a satellite access.

[0086] The processing module is configured to delete attachment information of the UE in the first network.

[0087] The eighth aspect provides a communication system, comprising a first network function, a second network function and a third network function.

[0088] The first network function is used to perform the network access method of any of the technical solutions in the first aspect.

[0089] The second network function is used to perform the network access method of any of the technical solutions in the second aspect.

[0090] The third network function is used to perform the network access method of any of the technical solutions in the third aspect.

[0091] The ninth aspect provides a program product, comprising a computer program, when the computer program is executed by a communication device, the communication device is enabled to implement the network access method described in the optional implementation manners of the first aspect to the third aspect.

[0092] The tenth aspect provides a computer program, when the computer program is executed by a computer, the computer is enabled to perform the network access method described in the optional implementation manners of the first aspect to the third aspect.

[0093] It can be understood that the UE, the network device and the communication system, the program product and the computer program described above are all used to perform the method provided by the embodiments of the present disclosure. Therefore, the beneficial effects achieved thereby can refer to the beneficial effects in the corresponding method, which will not be described here again.

[0094] The embodiments of the present disclosure provide a network access method, a communication device, a communication system and a storage medium. The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the mode after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation mode in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, the steps of different embodiments can be combined arbitrarily, an embodiment can be combined with the optional implementation mode of other embodiments.

[0095] In the embodiments of the present disclosure, the terms and / or descriptions between the embodiments are consistent and can be referred to each other if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0096] The terms used in the embodiments of the present disclosure are only for the purpose of describing the specific embodiments, and not as a limitation on the present disclosure.

[0097] In the embodiments of the present disclosure, unless otherwise specified, the elements expressed in singular form, such as "one", "a", "the", "above", "preceding", "this", etc., can represent "one and only one", or "one or more", "at least one", etc. For example, in the case of using articles such as "a", "an", "the" in English, the noun after the article can be understood as singular expression, or as plural expression.

[0098] In the embodiments of the present disclosure, "plurality" means two or more.

[0099] In some embodiments, the terms "at least one of", "one or more", "a plurality of", "multiple", and the like can be replaced with each other.

[0100] In some embodiments, the description of "at least one of A, B", "A and / or B", "A or B in one case, A or B in another case", "one of A or B", and the like, can include the following technical manners according to the case: in some embodiments, A is executed (A is executed regardless of B); in some embodiments, B is executed (B is executed regardless of A); in some embodiments, A and B are selectively executed (A and B are selectively executed); in some embodiments, A and B are executed (A and B are executed). When there are more branches such as A, B, C, and the like, the above description is similar.

[0101] In some embodiments, the description of "A or B", and the like, can include the following technical manners according to the case: in some embodiments, A is executed (A is executed regardless of B); in some embodiments, B is executed (B is executed regardless of A); in some embodiments, A and B are selectively executed (A and B are selectively executed). When there are more branches such as A, B, C, and the like, the above description is similar.

[0102] The prefix words "first", "second", and the like in the embodiments of the present disclosure are only used to distinguish different description objects, and do not constitute a limitation on the position, order, priority, quantity, or content of the description objects. The description of the description objects should refer to the description in the context of the claims or embodiments, and should not constitute an additional limitation because of the use of the prefix words. For example, the description objects are "fields", and the ordinal words before "fields" in "first field" and "second field" do not limit the position or order between "fields". "First" and "second" do not limit whether the "fields" modified thereby are in the same message, nor do they limit the order of "first field" and "second field". For another example, the description objects are "levels", and the ordinal words before "levels" in "first level" and "second level" do not limit the priority between "levels". For another example, the quantity of the description objects is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "devices" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the description objects are "devices", and "first device" and "second device" can be the same device or different devices, and the types thereof can be the same or different. For another example, the description objects are "information", and "first type of information" and "second type of information" can be the same information or different information, and the content thereof can be the same or different.

[0103] In some embodiments, "including A", "containing A", "for indicating A", "carrying A", can be interpreted as directly carrying A, or indirectly indicating A.

[0104] In some embodiments, the terms "…", "determining …", "in the case of …", "when …", "if …", and the like can be replaced with each other.

[0105] In some embodiments, the terms “greater than”, “greater than or equal to”, “not less than”, “more than”, “more than or equal to”, “not less than”, “higher than”, “higher than or equal to”, “not lower than”, “above”, and the like can be replaced with each other, and the terms “less than”, “less than or equal to”, “not greater than”, “fewer than”, “fewer than or equal to”, “not more than”, “lower than”, “lower than or equal to”, “not higher than”, “below”, and the like can be replaced with each other.

[0106] In some embodiments, an apparatus and the like can be interpreted as an entity, and can also be interpreted as virtual, and the names thereof are not limited to the names described in the embodiments. The terms “apparatus”, “equipment”, “device”, “circuitry”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, “subject”, and the like can be replaced with each other.

[0107] In some embodiments, “network” can be interpreted as an apparatus (for example, an access network device, a core network device, and the like) included in the network.

[0108] In some embodiments, the terms “access network device (AN device)”, “radio access network device (RAN device)”, “base station (BS)”, “radio base station”, “fixed station”, “node”, “access point”, “transmission point (TP)”, “reception point (RP)”, “transmission / reception point (TRP)”, “panel”, “antenna panel”, “antenna array”, “cell”, “macro cell”, “small cell”, “femto cell”, “pico cell”, “sector”, “cell group”, “serving cell”, “carrier”, “component carrier”, “bandwidth part (BWP)”, and the like can be replaced with each other.

[0109] In some embodiments, the terms "terminal," "terminal device," "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," and so on can be replaced with each other.

[0110] In some embodiments, an access network device, a core network device, or a network device can be replaced with a UE. For example, for a structure in which communication between an access network device, a core network device, or a network device and a UE is replaced with communication between a plurality of UEs (e.g., device-to-device (D2D), vehicle-to-everything (V2X), or the like), embodiments of the present disclosure can also be applied. In this case, a structure in which a UE has all or part of the functions of an access network device can also be provided. Further, the terms "uplink," "downlink," and the like can also be replaced with terms corresponding to inter-UE communication (e.g., "side"). For example, an uplink channel, a downlink channel, and the like can be replaced with a sidelink channel, and an uplink, a downlink, and the like can be replaced with a sidelink.

[0111] In some embodiments, a UE can be replaced with an access network device, a core network device, or a network device. In this case, a structure in which an access network device, a core network device, or a network device has all or part of the functions of a UE can also be provided.

[0112] In some embodiments, data, information, etc. can be obtained in compliance with laws and regulations of the country where the location is situated.

[0113] In some embodiments, data, information, etc. can be obtained after obtaining consent of the user.

[0114] In addition, each element, each row, or each column in the table of the embodiments of the present disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0115] FIG. 1A is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure.

[0116] As shown in FIG. 1A, the communication system 100 includes a UE (terminal) 101 and a network device 102. The network device 102 can include an access network device and / or a core network device.

[0117] In some embodiments, the UE 101 includes at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a Pad, a computer with wireless transceiver function, a virtual reality (VR) UE device, an augmented reality (AR) UE device, a wireless UE device in industrial control, a wireless UE device in self-driving, a wireless UE device in remote medical surgery, a wireless UE device in smart grid, a wireless UE device in transportation safety, a wireless UE device in smart city, a wireless UE device in smart home, etc., but is not limited thereto.

[0118] In some embodiments, the UE is also referred to as a User Equipment (UE).

[0119] In some embodiments, the access network device may, for example, be at least one of a node or a device that accesses a UE to a wireless network, and the access network device may, for example, include at least one of an evolved NodeB (eNB) in a 5G communication system, a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open RAN, a Cloud RAN, a base station in other communication systems, an access node in a Wi-Fi system, but is not limited thereto.

[0120] In some embodiments, the technical means of the present disclosure can be applicable to an Open RAN architecture, in which case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0121] In some embodiments, the access network device can be composed of a central unit (CU) and a distributed unit (DU), where the CU can also be referred to as a control unit. The CU-DU structure can split the protocol layers of the access network device, and some of the protocol layers can be controlled by the CU, while the rest or all of the protocol layers can be distributed in the DU and controlled by the CU, but is not limited thereto.

[0122] In some embodiments, the core network device can be one device including the first network element, or can be multiple devices or device groups each including the first network element. The network element can be virtual or physical. The core network may, for example, include at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0123] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical means of the embodiments of the present disclosure, and does not constitute a limitation on the technical means provided by the embodiments of the present disclosure. It can be known by those skilled in the art that, as the system architecture evolves and new service scenarios appear, the technical means provided by the embodiments of the present disclosure are also applicable to similar technical problems.

[0124] The embodiments of the present disclosure described below can be applied to the communication system 100 shown in FIG. 1A or part of the subjects, but are not limited thereto. The subjects shown in FIG. 1A are exemplary, and the communication system can include all or part of the subjects in FIG. 1A, or other subjects other than those in FIG. 1A. The number and form of each subject is arbitrary, and the connection relationship between the subjects is exemplary. The subjects can not be connected or can be connected, and the connection can be in any manner, can be direct connection or indirect connection, and can be wired connection or wireless connection.

[0125] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other resources, next-generation system extended based thereon, and the like. Further, a plurality of systems can be combined (for example, combination of LTE and NR).

[0126] A communication network includes a Terrestrial network (TN) and a Non-Terrestrial Network (NTN). A TN includes all network functions located on the ground. For example, both the RAN and the Core Network (CN) of a TN are located on the ground. At least some network functions of an NTN are located in space. For example, the RAN and / or part of the CN of an NTN are located on a satellite. Figure IB shows an example of a network implementation where both the eNBs and part of the MME are located on a satellite. In some cases, the satellite network connectivity can be intermittent due to the small number of satellites in a constellation. For example, the service link and the feeder link cannot serve a UE at the same time. In this case, the network uses a store-and-forward function to support the development of delay-tolerant services or non-time-sensitive services. Figure 1C shows an example of a network implementation that supports a store-and-forward function. As shown in Figure 1C, the exchange of signaling and data services end-to-end can be divided into two steps.

[0127] Step A: The exchange of signaling and data between the UE and the satellite, for example, through the service link between the UE and the satellite. In the case where the satellite is not connected to both the UE and the ground station at the same time, the satellite will buffer the data and / or signaling received from the UE, i.e., the satellite temporarily postpones sending the data and / or signaling uploaded by the UE to the ground station.

[0128] Step B: The satellite and the ground station establish a connection, at which time the satellite can send the buffered data and / or signaling of the UE to the ground station. For example, the satellite sends the data and / or signaling of the UE to the ground station through the feeder link. The ground station is connected to the terrestrial network and can transmit the data and / or signaling of the UE to the core network (CN).

[0129] In some embodiments, the store-and-forward function of a communication system with satellite access is intended to provide a certain level of communication service for UEs under satellite coverage. For example, when a satellite is not connected to the ground network through the feeder link or through the inter-satellite link (ISL) at a certain point in time, but can buffer the data and / or signaling sent by the UE through the store-and-forward function, or buffer the data and / or signaling sent by the CN to the UE.

[0130] Figure ID shows a process for a UE to attach to a satellite network that supports store-and-forward, which can include:

[0131] Step 1: UE sends a NAS Attach Request message to MME-SAT (part or full MME functionality deployed on satellite); the NAS Attach Request message can include a Store & Forward (S&F) indication which can be used to indicate that the UE supports Store & Forward functionality.

[0132] Step 2: MME-SAT stores the International Mobile Subscriber Identification Number (IMSI) of the UE;

[0133] Step 3: MME-SAT sends a NAS Attach Reject message to the UE, which can include a failure cause and / or timer information to re-initiate the Attach Request message. Exemplarily, the satellite rejects the UE’s request by sending an Attach Reject message in view of the fact that the satellite is not connected to the ground station.

[0134] The UE does not need to re-initiate the Attach Request message for the duration of the timer indicated.

[0135] Step 4a: MME-SAT sends an Authentication Request (Auth data request) message to MME-GND (part or full MME functionality deployed on ground).

[0136] Step 4b: MME-GND sends an Authentication Request (Auth data request) message to the Home Subscriber Server (HSS).

[0137] Step 5: HSS sends an Authentication Response (Auth data response) to MME-GND. Exemplarily, the Authentication Response can include an EPS Authentication Vector.

[0138] Step 6: MME-GND sends an Update Location Request message to HSS.

[0139] Step 7: HSS sends an Update Location Ack message to MME-GND.

[0140] Step 8: MME-GND sends an Authentication Response and Location Update Ack to MME-SAT.

[0141] Step 9: The UE sends a NAS Attach Request to the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) and the E-UTRAN sends a NAS Attach Request message to the MME-SAT.

[0142] Step 10: The MME-SAT sends a NAS Authentication Response message to the UE through the E-UTRAN. The NAS Authentication Response includes a random number (RAND), AUTN, KSI.

[0143] Step 11: The UE sends a NAS Authentication Response message to the MME-SAT through the E-UTRAN. The NAS Authentication Response can include RES.

[0144] Step 12: The MME-SAT sends a NAS Attach Accept message to the UE through the E-UTRAN.

[0145] Step 13: The UE sends a NAS Attach Complete message to the MME-SAT through the E-UTRAN.

[0146] Step 14: The MME-SAT sends a Location Update Request message to the HSS through the MME-GND.

[0147] Step 15: The HSS sends a Location Update Ack message to the MME-SAT through the MME-GND.

[0148] In the above attachment procedure of the UE, as shown in step 3, if the MME-SAT receives an Attach Request message from the UE but the feeder link of the MME-SAT is unavailable, the MME-SAT will return an Attach Reject message to the UE. The Attach Reject message can carry timer information, which can be used by the UE to start a Wait Timer for requesting attachment again.

[0149] However, how the UE specifically performs the request for attachment again based on the Wait Timer depends on the UE implementation, for example, during the waiting period set by the Wait Timer, the UE can search for another terrestrial or satellite Public Land Mobile Network (PLMN) for attachment to obtain communication services. In this case, it is not clear how the core network handles the conflict caused by the UE attaching to a network supporting store-and-forward capability and attaching to other satellite or terrestrial networks.

[0150] FIG. 2A is an interaction diagram illustrating a network access method according to an example embodiment. As shown in FIG. 2A, the embodiments of the present disclosure relate to a network access method for the communication system 100, the method comprising:

[0151] S2101: The UE sends a sixth message to a third network function of the first network.

[0152] In some embodiments, the third network function can be a core network function for mobility management and / or access management of the UE.

[0153] In some embodiments, the third network function can be a second mobility management function.

[0154] In some embodiments, the third network function can be a core network function deployed on a satellite. Illustratively, the second mobility management function is a Mobile Management Entity (MME) deployed on a satellite.

[0155] In some embodiments, the sixth message is used for the UE to initiate a request for a first attachment to the third network function.

[0156] In some embodiments, the sixth message is a Non Access Stratum (NAS) message.

[0157] In some embodiments, the first attachment is an attachment of the UE in the first network.

[0158] In some embodiments, the first network uses a first access and supports a store-and-forward function.

[0159] In some embodiments, the first access is a satellite access.

[0160] In some embodiments, the sixth information includes attachment information of the first attachment of the UE.

[0161] In some embodiments, the attachment information of the first attachment can include, but is not limited to, at least one of the following:

[0162] identification information of the UE;

[0163] an access method used by the UE, etc.

[0164] In some embodiments, the identification information of the UE includes, but is not limited to, an International Mobile Subscriber Identification Number (IMSI).

[0165] Correspondingly, the third network function receives the sixth information of the UE.

[0166] S2102: The third network function stores the attach information of the first attach.

[0167] In some embodiments, the second mobility management function stores at least the identification information of the UE, for example, the second mobility management function stores at least the IMSI of the UE.

[0168] S2103: The third network function is capable of sending a seventh message to the UE.

[0169] In some embodiments, the second mobility management function determines that the link between the UE and the ground station is disconnected, and sends a seventh message to the UE indicating the attach rejection or the deferred attach.

[0170] In some embodiments, the seventh message can include timer information, which can include a timer duration. Within the timer duration, the UE no longer initiates the first access based attach request to the first network.

[0171] In some embodiments, the seventh message can include a rejection reason. For example, the rejection reason can indicate that the connection (feeder link) between the third network function and the second network function is currently unavailable.

[0172] In some embodiments, if the UE receives the seventh message carrying the rejection reason, the UE can consider that the attach can continue after the timer expires.

[0173] S2104: The third network function sends an eighth message to the second network function.

[0174] In some embodiments, the second network function is deployed on the ground. Illustratively, the second network function can be a first MME. Further, the first MME can be deployed on the ground.

[0175] In some embodiments, the third network function sends the eighth message to the second network function after the connection between the third network function and the second network function is restored. Illustratively, after the feeder link between the second MME and the first MME is restored, the second MME sends the eighth message to the first MME.

[0176] In some embodiments, the eighth message can include all the contents of the sixth message, or can only include part of the contents of the sixth message.

[0177] It is worth noting that there is no certain order between S2104 and S2103. For example, S2104 and S2103 can be executed simultaneously, or can be executed sequentially.

[0178] S2105: The second network function sends the first message to the first network function.

[0179] In some embodiments, the second network function, after receiving the eighth message, sends the first message to the first network function.

[0180] In some embodiments, the first network function can store subscription data of the UE.

[0181] In some embodiments, the first network function can be a Home Subscriber Server (HSS).

[0182] In some embodiments, the first message can be related to the first attachment. For example, the first message is a message used in an attachment procedure of the first attachment.

[0183] In some embodiments, the first message is used for the UE to request an authentication vector in an attachment procedure of the first network, and / or the first message can be used to request subscription data of the UE.

[0184] S2106: The first network function determines whether the UE has attached to the second network.

[0185] In some embodiments, the first network function determines whether the UE has attached to the second network according to the second information.

[0186] In some embodiments, the second network and the first network can be different networks. For example, the second network and the first network have different communication modes, or the second network and the first network have different network architectures, or the second network and the first network have different networking modes, etc. The difference between the second network and the first network can be embodied in different aspects, which will not be limited here.

[0187] In some embodiments, the second network and the first network can be the same core network. In this case, the first attachment and the second attachment request attachment to the same network (i.e., the same network), and at this time, the access network used by the first attachment and the access network used by the second attachment are different. For example, in this scenario, the first attachment corresponds to a first access, and the second attachment corresponds to a second access. The first access is a satellite access. The second access is different from the first access. For example, the second access is not a satellite access. For another example, the second access is a ground access. That is, in some embodiments, when the first network and the second network are the same network, the second access used by the second network is different from the first access.

[0188] In some embodiments, the second information includes at least one of the following:

[0189] identification information of the UE;

[0190] first time information, the first time information being used to indicate a time at which the first network rejects an attachment request of the UE, or the time information being used to indicate a time at which the UE requests to attach to the first network;

[0191] UE's attachment information at the second network.

[0192] In some embodiments, the UE's attachment information at the second network comprises at least one of:

[0193] UE's identity information;

[0194] first network information, the first network information comprising at least UE's identity information of a mobility management entity (MME) used by the UE to attach to the second network;

[0195] second network information, the second network information comprising at least information of an access network corresponding to the second network to which the UE attaches.

[0196] In some embodiments, determining whether the UE has attached to the second network according to the second information comprises at least one of:

[0197] determining whether the UE has attached to the second network after a time indicated by the first time information according to the first time information;

[0198] determining whether the UE has attached to the second network according to the UE's attachment information at the second network.

[0199] If the UE has completed the second attachment at the second network, the first network function records the second attachment information of the second attachment of the UE. The second attachment information is the UE's attachment information at the second network.

[0200] Exemplarily, after the first network function obtains the first time information, the first network function can determine the time when the UE requests the first attachment or the time when the network device rejects the first attachment according to the first time information, and further determine whether there is another attachment after the time indicated by the first time information. If there is the attachment information, it indicates that the UE has completed another attachment, and the another attachment is the second attachment.

[0201] Exemplarily, if the second attachment information is queried based on the UE's identity information, it indicates that the UE has completed the second attachment, otherwise, it can be considered that the UE has no network attachment after the time indicated by the first time information.

[0202] In some embodiments, if the first network function determines that the UE has attached to the second network, for example, according to an operator policy, the first network function can determine to reject the first attachment of the UE.

[0203] In some embodiments, if the first network function determines that the UE is not attached to the second network, further determination is needed according to the subscription data of the UE whether to accept the first attachment of the UE. For example, if the subscription data of the UE indicates that the UE has no permission to attach to the first network using the satellite access, the first attachment of the UE can also be rejected. For another example, if the subscription data of the UE indicates that the UE has permission to attach to the first network using the satellite access, the first attachment of the UE can be accepted.

[0204] S2107: The first network function sends a second message to the second network function.

[0205] In some embodiments, the second message comprises the first information.

[0206] In some embodiments, the first information is used to indicate that the UE has attached to the second network, and / or the first information is used to indicate that the UE is rejected to attach to the first network.

[0207] In some embodiments, the first information can explicitly indicate that the first attachment is rejected or that the UE has attached to the second network. In other embodiments, the first information can implicitly indicate that the first attachment is rejected or that the UE has attached to the second network.

[0208] In some embodiments, the second message can also indicate a rejection reason. For example, the rejection reason can be used for the reason of rejecting the UE to attach to the first network, or the reason of rejecting the UE to attach to the first network using the satellite access. Exemplarily, the rejection reason includes but is not limited to that the UE has attached to the second network.

[0209] S2108: The second network function deletes the attachment information of the first attachment.

[0210] In some embodiments, after receiving the second message, the second network function deletes the attachment information of the first attachment, so as to avoid unnecessary storage of the attachment information of the first attachment by the second network function.

[0211] In some embodiments, when it is determined that the UE is rejected to attach to the first network using the satellite access, the second network function can delete the attachment information of the first attachment. That is, when the UE is accepted to attach to the first network using the satellite access, the second network function does not need to delete the auxiliary information of the first attachment, which means that S2108 is an optional step.

[0212] S2109: The second network function sends a third message to the third network function.

[0213] In some embodiments, the third message is used to indicate that the UE has attached to the second network or to indicate that the UE is rejected to attach to the first network.

[0214] In some embodiments, the third message is used to indicate that the UE has attached to the second network or to indicate that the UE is rejected to attach to the first network.

[0215] S2110: The third network function sends a fifth message to the UE.

[0216] In some embodiments, the fifth message is used to reject the UE to attach to the first network.

[0217] It is noted that S2110 is an optional step, which can not be performed in actual implementation.

[0218] FIG. 2B is an interaction diagram illustrating a network access method according to an example embodiment. As shown in FIG. 2B, the embodiments of the present disclosure relate to a network access method, for the communication system 100, the method comprising:

[0219] S2201: The UE sends a sixth message to a second network function of the first network.

[0220] In some embodiments, the second network function can be a core network function that performs mobility management and / or access management for the UE.

[0221] In some embodiments, the second network function can be a second mobility management function.

[0222] In some embodiments, the second network function can be a core network function deployed on a satellite. Illustratively, the second mobility management function is a Mobile Management Entity (MME) deployed on a satellite.

[0223] In some embodiments, the sixth message is used to request the UE to initiate a first attachment to the third network function.

[0224] In some embodiments, the sixth message is a Non Access Stratum (NAS) message.

[0225] In some embodiments, the first attachment is an attachment of the UE to the first network.

[0226] In some embodiments, the first network uses a first access and supports a store-and-forward function.

[0227] In some embodiments, the first access is a satellite access.

[0228] In some embodiments, the sixth information includes attachment information of the first attachment of the UE.

[0229] In some embodiments, the attachment information of the first attachment can include, but is not limited to, at least one of the following:

[0230] identification information of the UE;

[0231] access mode used by the UE, etc.

[0232] In some embodiments, the identification information of the UE includes, but is not limited to, an International Mobile Subscriber Identification Number (IMSI).

[0233] Correspondingly, the second network function receives the sixth information of the UE.

[0234] S2202: The second network function stores the attach information of the first attach.

[0235] In some embodiments, the second mobility management function stores at least the identification information of the UE, for example, the second mobility management function stores at least the IMSI of the UE, etc.

[0236] S2203: The second network function sends a seventh message to the UE.

[0237] In some embodiments, the second mobility management function determines that the link between the current and the ground station is disconnected, and sends the seventh message of at least rejecting or suspending the attach to the UE.

[0238] In some embodiments, the seventh message can include timer information, and the timer information can include a timing duration. Within the timing duration of the timer, the UE no longer initiates an attach request based on the first access to the first network.

[0239] In some embodiments, the timing duration of the timer information can be determined according to the expected connection recovery time between the third network function and the second network function.

[0240] In some embodiments, the seventh message can include a rejection reason. For example, the rejection reason can indicate that the connection between the third network function and the second network function is currently disconnected.

[0241] In some embodiments, if the UE receives the seventh message carrying the rejection reason, the UE can consider that the attach can continue after the timer expires.

[0242] S2204: The second network function sends a first message to the first network function.

[0243] In some embodiments, the first network function is deployed on the ground. Illustratively, the first network function can be a ground station of a core network function. Illustratively, the first network function can be a first MME. Further, the first MME can be a MME deployed on the ground.

[0244] In some embodiments, the second network function sends the first message to the first network function after restoring the feeder connection between the second network function and the first network function. For example, the second MME sends the first message to the first MME after restoring the connection between the second MME and the first MME.

[0245] In some embodiments, the first message can include all contents of the sixth message, or can include part of the contents of the sixth message.

[0246] In some embodiments, the second network function sends the first message to the first network function after receiving the sixth message.

[0247] In some embodiments, the first network function can store subscription data of the UE.

[0248] In some embodiments, the first network function can be a Home Subscriber Server (HSS).

[0249] In some embodiments, the first message can be related to the first attachment. For example, the first message is a message used in an attachment procedure of the first attachment.

[0250] In some embodiments, the first message is used to request an authentication vector of the UE in the first network attachment procedure, and / or the first message can be used to request subscription data of the UE.

[0251] S2205: The first network function determines whether the UE has attached to the second network according to the second information.

[0252] In some embodiments, the second network and the first network can be different networks. For example, the second network and the first network can have different communication modes, or different network architectures, or different network deployment modes, etc. The difference between the second network and the first network can be embodied in different aspects, which are not limited here.

[0253] In some embodiments, the second network and the first network can be the same network. In this case, the first attachment and the second attachment request attachment to the same network (i.e., the same network), and the access network used by the first attachment and the access network used by the second attachment are different. For example, in this scenario, the first attachment corresponds to a first access, and the second attachment corresponds to a second access. The first access is a satellite access. The second access is different from the first access. For example, the second access is not a satellite access. For another example, the second access is a terrestrial access. That is, in some embodiments, when the first network and the second network are the same network, the second access used by the second network is different from the first access.

[0254] In some embodiments, the second information comprises at least one of:

[0255] identification information of the UE;

[0256] first time information, the first time information indicating a time when the first network rejects the UE's first attachment request, or the first time information indicating a time when the UE requests to attach to the first network;

[0257] attachment information of the UE in the second network.

[0258] In some embodiments, the attachment information of the UE in the second network comprises at least one of:

[0259] identification information of the UE;

[0260] first network information, the first network information comprising at least identification information of a mobility management entity (MME) used by the UE to attach to the second network;

[0261] second network information, the second network information comprising at least information of an access network corresponding to the second network to which the UE attaches.

[0262] In some embodiments, determining whether the UE has attached to the second network according to the second information comprises at least one of:

[0263] determining whether the UE has attached to the second network after the time indicated by the first time information according to the first time information;

[0264] determining whether the UE has attached to the second network according to the attachment information of the UE in the second network.

[0265] If the UE has completed the second attachment, the first network function records the second attachment information of the UE. The second attachment information is the attachment information of the UE in the second network.

[0266] For example, after the first network function obtains the first time information, the first network function can determine the time when the UE requests the first attachment or the time when the network device rejects the first attachment according to the first time information, and then determine whether the UE has another attachment information after the time indicated by the first time information. If there is another attachment information, it indicates that the UE has completed the second attachment.

[0267] For example, if the second attachment information is found based on the identification information of the UE, it indicates that the UE has completed the second attachment. Otherwise, it can be considered that the UE has no network attachment after the time indicated by the first time information.

[0268] In some embodiments, if the first network function determines that the UE has attached to the second network, the first network function can determine to reject the first attachment of the UE according to an operator policy, for example.

[0269] In some embodiments, if the first network function determines that the UE is not attached to the second network, it is further required to determine whether to accept the first attachment of the UE according to the subscription data of the UE. For example, if the subscription data of the UE indicates that the UE has no permission to attach to the first network using the satellite access, the first attachment of the UE can also be rejected. For another example, if the subscription data of the UE indicates that the UE has permission to attach to the first network using the satellite access, the first attachment of the UE can be accepted.

[0270] S2206: The first network function sends a second message to the second network function.

[0271] In some embodiments, the second message comprises the first information.

[0272] In some embodiments, the first information is used to indicate that the UE has attached to the second network, and / or the first information is used to indicate that the UE is rejected to attach to the first network.

[0273] In some embodiments, the first information can explicitly indicate that the first attachment is rejected or the UE has attached to the second network. In other embodiments, the first information can implicitly indicate that the first attachment is rejected or the UE has attached to the second network.

[0274] In some embodiments, the second message can also indicate a rejection reason. For example, the rejection reason can be used to indicate the reason for rejecting the UE to attach to the first network, or the reason for rejecting the UE to attach to the first network using the satellite access. For example, the rejection reason includes but is not limited to that the UE has attached to the second network.

[0275] S2207: The second network function deletes the attachment information of the first attachment.

[0276] In some embodiments, after receiving the second message, the second network function deletes the attachment information of the first attachment, so as to avoid unnecessary storage of the attachment information of the first attachment by the second network function.

[0277] In some embodiments, when it is determined that the UE is rejected to attach to the first network using the satellite access, the second network function can delete the attachment information of the first attachment. That is, when the UE is accepted to attach to the first network using the satellite access, the second network function does not need to delete the auxiliary information of the first attachment, which means that S2207 is an optional step.

[0278] S2208: The second network function sends a fourth message to the UE.

[0279] In some embodiments, the fourth message is used to reject the UE to attach to the first network.

[0280] It is worth noting that S2208 is an optional step, which can not be performed in actual implementation. For example, since the rejection of the attachment of the first network has been indicated through the seventh message in the step of S2208, it is not necessary to indicate again at this time.

[0281] As shown in FIG. 3A, the embodiments of the present disclosure provide a network access method, which is performed by a first network function. The method can include:

[0282] S3101: receiving a first message.

[0283] In some embodiments, the first message is received from a second network function.

[0284] In some embodiments, the first message is a message in a first network attachment procedure performed by a user equipment (UE).

[0285] In some embodiments, the first network uses a first access and supports a store-and-forward function.

[0286] In some embodiments, the first access is a satellite access.

[0287] In some embodiments, the first network function and / or the second network function can be a core network function.

[0288] In some embodiments, the second network function can be a first mobility management function (MME), and the first network function can be a home subscriber server (HSS) or the like.

[0289] In some embodiments, the first message is related to a first attachment of the UE. For example, the first message can be a message transmitted in an attachment procedure in which the UE requests to attach to the first network.

[0290] In some embodiments, the related description of the first message can be referred to the corresponding embodiments of FIG. 2A.

[0291] In some embodiments, the first message is used by the UE to request an authentication vector or request subscription data of the UE in the first network attachment procedure.

[0292] In some embodiments, the first network function is a home subscriber server (HSS), the second network function is a first mobility management function (MME), and the first message is used by the UE to request an authentication vector or request subscription data of the UE in the first network attachment procedure.

[0293] In some embodiments, the related description of the first message can be referred to the corresponding embodiments of FIG. 2A, which will not be repeated here.

[0294] S3102: determining whether the UE has attached to a second network.

[0295] In some embodiments, the first network and the second network can be the same network or different networks.

[0296] In some example embodiments, the first network and the second network are different networks, and the first attachment uses satellite access, and the second attachment uses other access than the satellite access used by the first attachment.

[0297] In some embodiments, the first network function determines whether the UE has attached to the second network according to the second information. For example, the related description of the second information can be referred to the corresponding embodiment of S2106 in FIG. 2A.

[0298] For example, the related description of the first network function determining whether the UE has attached to the second network can be referred to the corresponding embodiment of S2107 in FIG. 2A.

[0299] S3103: sending a second message.

[0300] In some embodiments, the first network function sends the second message to the second network function.

[0301] In some embodiments, the second message contains the first information.

[0302] In some embodiments, the first information is used to indicate that the UE has attached to the second network, and / or the first information is used to indicate that the UE is rejected to attach to the first network.

[0303] In some embodiments, the first information can explicitly indicate that the first attachment is rejected or the UE has attached to the second network. In other embodiments, the first information can implicitly indicate that the first attachment is rejected or the UE has attached to the second network.

[0304] For example, the related description of the first network function determining whether the UE has attached to the second network in S3103 can be referred to the corresponding embodiment of S2107 in FIG. 2A.

[0305] It is worth noting that any one of S3101 to S3103 can be performed alone. For example, the first network function does not need to send the second message when it determines to accept the first attachment of the UE after receiving the first message, which means that S3103 is an optional step, i.e., S3101 to S3102 can be combined.

[0306] As shown in FIG. 3B, the embodiments of the present disclosure provide a network access method, which is performed by a first network function. The method can include:

[0307] S3201: receiving a first message.

[0308] In some embodiments, the first message is sent by a second network function.

[0309] In some embodiments, the first message is a message in a first network attachment process of a user equipment (UE).

[0310] In some embodiments, the first network uses a first access and supports store-and-forward function.

[0311] In some embodiments, the first access is satellite access.

[0312] In some embodiments, the first network function and / or the second network function can be a core network function.

[0313] In some embodiments, the first network function is a first mobility management function, the second network function is a second mobility management function, and the first message is for a UE attach request at the first network.

[0314] In some embodiments, the related description of the first message can be referred to the corresponding embodiments of FIG. 2B, which will not be repeated here.

[0315] S3202: Determine whether the UE has attached to the second network.

[0316] In some embodiments, the first network and the second network can be the same network or different networks.

[0317] In some embodiments, the first network and the second network are different networks, the first attach uses satellite access, and the second attach does not use satellite access.

[0318] In some embodiments, the first network function determines whether the UE has attached to the second network according to the second information. For example, the related description of the second information can be referred to the corresponding embodiments of FIG. 2B.

[0319] The related description of the first network function determining whether the UE has attached to the second network can be referred to S2206 of FIG. 2B.

[0320] S3203: Send a second message.

[0321] In some embodiments, the first network function sends the second message to the second network function.

[0322] In some embodiments, the second message contains the first information.

[0323] In some embodiments, the first information is used to indicate that the UE has attached to the second network, and / or the first information is used to indicate that the UE is rejected to attach to the first network.

[0324] In some embodiments, the first information can explicitly indicate that the first attach is rejected or that the UE has attached to the second network. In other embodiments, the first information can implicitly indicate that the first attach is rejected or that the UE has attached to the second network.

[0325] The description of the first network function determining whether the UE has attached to the second network in S3203 can refer to the corresponding S2207 in FIG. 2B.

[0326] It is worth noting that any one of S3201 to S3203 can be performed alone. For example, the first network function does not need to send the second message when determining to accept the first attachment of the UE after receiving the first message, which means that S3203 is an optional step, i.e., S3201 to S3202 can be combined.

[0327] As shown in FIG. 4A, the embodiment of the present disclosure provides a network access method, which is performed by a second network function. The method can include:

[0328] S4101: sending a first message.

[0329] In some embodiments, the second network function sends the first message to the first network function.

[0330] In some embodiments, the second network function can be a first mobility management function. The first mobility management function can be deployed on the ground.

[0331] In some embodiments, the second network function sends the first message to the first network function.

[0332] In some embodiments, the second network function sends the first message to the first network function after receiving an eighth message sent by a third network function.

[0333] The description of the first network function determining whether the UE has attached to the second network in S4101 can refer to the corresponding S2105 in FIG. 2A.

[0334] S4102: receiving a second message.

[0335] In some embodiments, the second network function receives the second message of the first network function.

[0336] In some embodiments, the second network function receives the second message returned based on the first message after sending the first message.

[0337] In some embodiments, the second message contains first information; the first information is used to indicate that the UE has attached to the second network, or the first information is used to indicate that the UE is rejected to attach to the first network.

[0338] It is worth noting that the description of the second message can refer to the corresponding part of the embodiment in FIG. 2A.

[0339] S4103: sending a third message.

[0340] In some embodiments, the second network function sends a third message to the third network function.

[0341] In some embodiments, the third message is used to indicate that the UE has attached to the second network or to indicate that the UE is rejected to attach to the first network.

[0342] In some embodiments, the third message is used to cause the third network function to delete the attachment information of the UE in the first network. Illustratively, the third message indicates the third network function to delete the attachment information of the first attachment. That is, the third message indicates the third network function to delete the attachment information of the first attachment.

[0343] In some embodiments, the first network function can be a HSS, the second network function can be a first mobility management, and the third network function can be a second mobility management function.

[0344] S4104: deleting the attachment information of the UE in the first network.

[0345] Illustratively, the deleting the attachment information of the UE in the first network can be understood as that the second network function deletes the attachment information of the first attachment.

[0346] In some embodiments, the second network function deletes the locally stored attachment information of the UE in the first network.

[0347] It is worth noting that each of the steps in S4101 to S4104 can be performed independently. For example, S4101 can be performed independently, but the second message returned by the first network function can not be received. For example, the first network function can not send the second message when it is determined that the first attachment of the UE is not accepted. Or, the second network function receives a message indicating that the first attachment of the UE is accepted from the first network function when the first network function accepts the first attachment of the UE, instead of the second message. Since the second network function does not receive the second message, the third message does not need to be sent based on the second message, and thus S4102 is an optional step. Similarly, if the first UE is accepted to attach to the first network, the attachment information of the first attachment does not need to be deleted, and thus S4104 is an optional step. That is, S4101 can be performed independently.

[0348] In other embodiments, if it is determined that the UE is rejected to attach to the first network, the sending of the third message can also be omitted, and the third network function can default to reject the UE to attach to the first network if the third network function does not receive the third message within a specified time period, and thus can reject the first attachment of the UE and / or delete the stored attachment information of the first attachment. Thus, S4103 is also an optional step.

[0349] As shown in FIG. 4B, the embodiments of the present disclosure provide a network access method performed by a second network function. The method can include:

[0350] S4201: sending a first message.

[0351] In some embodiments, the second network function sends the first message to the first network function.

[0352] In some embodiments, the second network function can be a spaceborne CN function. For example, the second network function can be a second mobility management function. The second mobility management function can be deployed on a satellite.

[0353] In some embodiments, the second network function sends the first message to the first network function.

[0354] In some embodiments, the second network function sends the first message to the first network function after receiving the seventh message sent by the third network function.

[0355] Here, the first network function in S4201 determines whether the UE has attached to the second network. The related description can refer to the corresponding S2205 in FIG. 2B.

[0356] S4202: receiving a second message.

[0357] In some embodiments, the second network function receives the second message of the first network function.

[0358] In some embodiments, the second network function receives the second message returned by the first network function based on the first message after sending the first message.

[0359] In some embodiments, the second message contains first information; the first information is used to indicate that the UE has attached to the second network, or the first information is used to indicate that the UE is rejected to attach to the first network.

[0360] It is worth noting that the related description of the second message can refer to the related part of the corresponding embodiment in FIG. 2B.

[0361] S4203: sending a fourth message.

[0362] In some embodiments, the second network function sends the fourth message to the UE.

[0363] In some embodiments, the fourth message is used to reject the UE to attach to the first network.

[0364] In some embodiments, the fourth message can be a NAS message sent to the UE through the NAS layer.

[0365] In some embodiments, the first network function can be a first mobility management function, the second network function can be a second mobility management function, and the third network function can be a second mobility management function.

[0366] The first network function in S4203 determines whether the UE has attached to the second network. The description of the determination can be found in S2208 of FIG. 2B.

[0367] S4204: deleting the attachment information of the UE in the first network.

[0368] In an example, the deleting the attachment information of the UE in the first network can be understood as that the second network function deletes the attachment information of the first attachment. In some embodiments, the second network function deletes the locally stored attachment information of the UE in the first network.

[0369] As shown in FIG. 5, the embodiments of the present disclosure provide a network access method, which is performed by a third network function. The method can include:

[0370] S5101: receiving a third message.

[0371] In some embodiments, the third message is used to indicate that the UE has attached to the second network or to indicate that the UE is rejected to attach to the first network.

[0372] In some embodiments, the third message is used to make the third network function delete the attachment information of the UE in the first network.

[0373] In some embodiments, the third network function is a second mobility management function.

[0374] In some embodiments, the third network function receives the third message from the second network function after sending the eighth message to the second network function.

[0375] In some embodiments, the fourth message can be found in S2109 of the corresponding example of FIG. 2A.

[0376] S5102: sending a fifth message.

[0377] In some embodiments, the third network function sends the fifth message to the UE.

[0378] In some embodiments, the fifth message is used to reject the UE to attach to the first network.

[0379] Two optional ways to solve the UE access conflict are provided as follows:

[0380] Solution one:

[0381] (1) The HSS receives a first message sent by the MME-GND. The first message is used to request an authentication vector or to request user subscription information, etc. The first message is sent by the MME-GND to the HSS after the MME-GND receives the UE access initiated by the satellite to send an attach request.

[0382] The HSS returns a second message to the MME-GND. The second message contains the first information. The first information is used to indicate that the UE has completed access through other access or to reject the UE's attach request.

[0383] Before the HSS sends the second message, the HSS determines that the UE has completed access through other access and / or needs to reject the UE's attach request initiated through satellite access.

[0384] The HSS determines that the UE has completed access through other access and / or needs to reject the UE's attach request initiated through satellite access according to the second information.

[0385] The second information includes at least one of the following:

[0386] The IMSI of the UE;

[0387] The time at which the MME-SAT sends a third message to the UE, the third message being used to notify the UE of a temporary rejection of access due to an interruption of satellite connection;

[0388] The access context of the UE, the access context containing information related to the UE's access, such as the IMSI of the UE, the MME used by the UE for access, access information of the UE, and the like.

[0389] According to the first information, the MME-GND deletes the saved access information of the UE.

[0390] The MME-GND returns the first information to the MME-SAT. The first information can include but is not limited to the first indication and / or the second indication. The first indication is used to indicate a rejection indication of the attach request. The second indication is used to indicate deletion of the access information of the UE.

[0391] The MME-SAT deletes the saved access information of the UE.

[0392] The MME-SAT returns a fourth message to the UE. The fourth message is used to indicate a rejection of access, and the fourth message can also contain a rejection reason. The rejection reason can be used to indicate that the UE has completed access through other access.

[0393] Scheme two:

[0394] After the MME-GND receives the attach request message of the UE, if the MME-GND determines whether there is access information of the UE. When it is determined that the access information of the UE is information that the UE has completed access through other access, the MME-GND returns a first indication and / or a second indication to the MME-SAT. The first indication is used to indicate a rejection indication of the attach request. The second indication is used to indicate deletion of the access information of the UE.

[0395] The MME-SAT deletes the saved attach request of the UE.

[0396] The MME-SAT returns a message to the UE indicating access rejection, which can also contain a rejection cause that the UE has completed access through other access.

[0397] If the MME-GND does not have access information of the UE through other access, the first scheme is used.

[0398] Embodiment 1:

[0399] As shown in FIG. 6A, the embodiment of the present disclosure provides a UE access method, which can include:

[0400] Steps 1-3: When the UE determines that it is in the coverage of the satellite, the UE attempts to access the network by sending an initial attach request message to the MME-SAT. If the UE supports the store and forward (S&F) capability, the S&F indication is included in the attach request message. The MME-SAT saves the attach information of the UE, for example, which can include the IMSI, GUTI, etc. of the UE. Since the satellite is not connected with the ground station, the satellite rejects the attach request of the UE by sending an attach reject message. The attach reject message can also include a cause value indicating that the attach procedure is temporarily stopped, and a wait timer value indicating how long the UE should not attempt to initiate attach to the network. The MME-SAT stores the time of sending the attach reject message (“requested time”). Before the wait timer expires, the UE can initiate attach to other available networks (such as LTE access), for example, complete attach through LTE access. As part of the attach procedure, the HSS stores the attach information of the UE. For example, the attach message can include the IMSI of the UE, the information of the MME providing access service for the UE, and / or the access type and / or radio access technology (RAT) type used by the UE.

[0401] Step 4: When the feeder link is available, the MME-SAT establishes a connection with the MME-GND and sends an attach request of the UE to the MME-GND. The attach request message can contain information such as IMSI, requested time (“requested time”), etc. After receiving the attach request message, the MME-GND requests an authentication vector for the UE by sending an authentication request (IMSI, “requested time”) to the HSS.

[0402] Step 5. The HSS decides whether to generate an authentication vector for the UE and sends it to the MME-GND. The decision can be based on the request time information, UE information, etc., for example, after the above-mentioned request time, the UE has attached through another access, i.e., the HSS already has the UE attachment information, the HSS determines to refuse to generate an authentication vector for the UE.

[0403] Step 6. The HSS returns a verification data response message to the MME-GND to refuse the UE attachment, and the message contains an indication that the UE has completed attachment through another access.

[0404] Step 7. After receiving the response message containing the indication, the MME-GND deletes the UE information related to the attachment request.

[0405] 8. The MME-GND returns an attachment refusal message to the MME-SAT with a cause value. The refusal message indicates that the UE has completed attachment through another access.

[0406] 9. According to the prompt, the MME-SAT can delete the stored information related to the attachment request through the satellite access.

[0407] 10. Optionally, the MME-SAT can send an attachment refusal message to the UE with a cause value indicating that the UE has completed attachment through another access.

[0408] Embodiment 2:

[0409] As shown in FIG. 6B, the embodiment of the present disclosure provides a UE access method, which can include:

[0410] Steps 1-3: When the UE determines that it is in satellite coverage, the UE attempts to access the network by sending an initial attach request (without PDN connection) message to the MME-SAT. If the UE is enhanced with S&F capability, the S&F indication is included in the attach request message. The MME-SAT saves the UE's attach information, which can include, for example, the UE's IMSI, GUTI, etc. Since the satellite has no connection with the ground station, the satellite rejects the UE's attach request by sending an attach reject message. The attach reject message can also include a cause value indicating that the attach procedure is temporarily stopped, and a wait timer value indicating how long the UE should not attempt to initiate attach to the network. The MME-SAT stores the time at which the attach reject message is sent ("requested time"). Before the wait timer expires, the UE can initiate attach to other available networks (e.g., LTE access) and complete the attach, for example, through LTE access. As part of the attach procedure, the HSS stores the UE's attach information. For example, the attach information can include the UE's IMSI, information of the MME that provides access service to the UE, and / or the type of access and / or the type of radio access technology (RAT) used by the UE.

[0411] 4. When the feeder link is available, the MME-SAT establishes a connection with the MME-GND and sends an attach request for the UE to the MME-GND. The attach request message can include the IMSI, the "requested time", etc.

[0412] 5. If the MME-GND determines that the UE has attach information of a UE that has attached through a different access than the current access after the requested time, the MME-GND decides to reject the attach request.

[0413] 6. The MME-GND returns an attach reject message to the MME-SAT with a cause value indicating that the UE has completed attach through another access.

[0414] 7. Upon prompting, the MME-SAT deletes the stored UE information related to the attach request through satellite access.

[0415] 8. Optionally, the MME-SAT can send an attach reject message to the UE with a cause value indicating that the UE has attached through another access.

[0416] In the embodiments of the present disclosure, part or all of the steps, and optional implementation manners thereof, can be combined with part or all of the steps in other embodiments, or combined with optional implementation manners of other embodiments.

[0417] In the embodiments of the present disclosure, part or all of the steps, and optional implementation manners thereof, can be combined with part or all of the steps in other embodiments, or combined with optional implementation manners of other embodiments.

[0418] The embodiments of the present disclosure further provide a device for implementing any of the above methods, for example, providing a device, the device comprising units or modules for implementing the steps performed by the UE in any of the above methods. For another example, another device is provided, comprising units or modules for implementing the steps performed by the network device (for example, an access network device, or a core network device, etc.) in any of the above methods.

[0419] It should be understood that the division of units or modules in the above device is only a logical function division, and all or part of them can be integrated into one physical entity, or can be physically separated. In addition, the units or modules in the device can be implemented in the form of processor calling software: for example, the device includes a processor, the processor is connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules of the device, wherein the processor is, for example, a general processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be implemented by the design of hardware circuit, and the hardware circuit can be understood as one or more processors; for example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are implemented by the design of the logical relationship of elements in the circuit; for another example, in another implementation, the hardware circuit is a programmable logic device (PLD), and taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to implement the functions of part or all of the units or modules. All units or modules of the above device can be implemented by processor calling software, or all units or modules can be implemented by hardware circuit, or part of the units or modules can be implemented by processor calling software, and the remaining part can be implemented by hardware circuit.

[0420] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), and the like. In another implementation, the processor can implement certain functions through a logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads an instruction to implement the functions of the above part or all units or modules. In addition, the hardware circuit can also be designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0421] As shown in FIG. 7A, the embodiments of the present disclosure provide a first network function, comprising:

[0422] The receiving module 7101 is configured to receive a first message sent by a second network function, the first message being a message in a first network attachment process performed by a user equipment (UE), the first network using a first access and supporting a store-and-forward function; and the first access being a satellite access.

[0423] The sending module 7102 is configured to send a second message to the second network function, the second message containing first information; and the first information being used to indicate that the UE has attached to the second network, or the first information being used to indicate that the UE is rejected to attach to the first network.

[0424] In some embodiments, the sending module and / or the receiving module can correspond to a network interface and / or a transceiving antenna of the first network function.

[0425] In some embodiments, the first network function further comprises a processing module.

[0426] In some embodiments, the processing module can be configured to perform, by the first network function, steps related to information processing in any one of the network access methods.

[0427] In some embodiments, the sending module can be configured to perform, by the first network function, steps related to information sending in any one of the network access methods.

[0428] In some embodiments, the receiving module can be configured to perform, by the first network function, steps related to information sending in any one of the network access methods.

[0429] In some embodiments, when the first network and the second network are the same network, the second network uses a second access different from the first access.

[0430] In some embodiments, the apparatus further comprises:

[0431] a processing module configured to determine, according to second information, whether the UE has attached to the second network, the second information comprising at least one of

[0432] :

[0433] identification information of the UE;

[0434] first time information, the first time information being used to indicate a time at which the first network rejects the UE attachment request, or the time information being used to indicate a time at which the UE requests to attach to the first network;

[0435] attachment information of the UE in the second network.

[0436] In some embodiments, the attachment information of the UE in the second network comprises at least one of:

[0437] identification information of the UE;

[0438] first network information, the first network information comprising at least identification information of a mobility management function (MME) used by the UE to attach to the second network;

[0439] second network information, the second network information comprising at least information of an access network corresponding to the second network to which the UE attaches.

[0440] In some embodiments, determining, according to the second information, whether the UE has attached to the second network comprises at least one of:

[0441] determining, according to the first time information, whether the UE has attached to the second network after a time indicated by the time information;

[0442] determining, according to the attachment information of the UE in the second network, whether the UE has attached to the second network.

[0443] In some embodiments, the first network function is a home subscriber server (HSS), and the second network function is a first mobility management function (MME), or

[0444] The first network function is a first mobility management function, and the second network function is a second mobility management function.

[0445] The second mobility management function is deployed on a satellite, and the first mobility management function is deployed on the ground.

[0446] In some embodiments, the first network function is a home subscriber server (HSS), and the second network function is a first mobility management function (MME), and the first message is used for the UE to request an authentication vector or request subscription data of the UE in a first network attachment procedure.

[0447] In some embodiments, the first network function is a first mobility management function, the second network function is a second mobility management function, and the first message is used for an attachment request of the UE to the first network.

[0448] As shown in FIG. 7B, the embodiments of the present disclosure provide a second network function, which includes:

[0449] The sending module 7201 is configured to send a first message to a first network function, the first message being a message in a first network attachment procedure of a user equipment (UE), the first network using a first satellite access and supporting a store-and-forward function;

[0450] The receiving module 7202 is configured to receive a second message sent by the first network function, the second message containing first information; the first information being used to indicate that the UE has attached to a second network or to indicate that the UE is rejected to attach to the first network.

[0451] In some embodiments, the sending module and / or the receiving module can correspond to a network interface and / or a transceiving antenna of the second network function.

[0452] In some embodiments, the second network function can include a processing module.

[0453] In some embodiments, the processing module can be used for the second network function to perform steps related to information processing in any one of the network access methods.

[0454] In some embodiments, the sending module can be used for the second network function to perform steps related to information sending in any one of the network access methods.

[0455] In some embodiments, the receiving module can be used for the second network function to perform steps related to information sending in any one of the network access methods.

[0456] In some embodiments, the first network and the second network are the same network, and the second network uses a second access different from a first access used by the first network.

[0457] In some embodiments, the first network function is a home subscriber server (HSS), and the second network function is a first mobility management function, and the method further comprises deleting the attachment information of the first attachment.

[0458] In some embodiments, the sending module is further configured to send, to a third network function, a third message indicating that the UE has attached to the second network or rejecting the UE from attaching to the first network, so that the third network function deletes the attachment information of the UE in the first network; and the third network function is a second mobility management function.

[0459] In some embodiments, the first network function is a first mobility management function, and the second network function is a second mobility management function, and the method further comprises deleting the attachment information of the UE in the first network.

[0460] In some embodiments, the sending module is further configured to send, to the UE, a fourth message rejecting the UE from attaching to the first network.

[0461] As shown in FIG. 7C, the embodiments of the present disclosure provide a third network function, which comprises:

[0462] The receiving module 7301 is configured to receive a third message sent by a second network function, the third message indicating that a user equipment (UE) has attached to the second network or rejecting the UE from attaching to the first network; the first network uses a first access and supports a store-and-forward function; and the first access is a satellite access.

[0463] The processing module 7302 is configured to delete the attachment information of the UE in the first network.

[0464] In some embodiments, the third network function further comprises the receiving module and / or the processing module.

[0465] In some embodiments, the sending module and / or the receiving module can correspond to a network interface and / or a transceiving antenna of the third network function.

[0466] In some embodiments, the sending module is configured to send, to the UE, a fifth message rejecting the UE from attaching to the first network.

[0467] The embodiments of the present disclosure also provide a communication device, which can comprise one or more processors; wherein the processor is configured to invoke instructions to cause the communication device to perform the network access method implemented by any one of the preceding embodiments.

[0468] In some embodiments, as shown in FIG. 8A and / or FIG. 8B, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 can also be outside the communication device 8100.

[0469] The communication device can be the aforementioned UE and network device. In some embodiments, the network device can be a master node and / or a secondary node.

[0470] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps in the above methods, such as sending and receiving, are performed by the transceiver 8103, and other steps are performed by the processor 8101.

[0471] In some embodiments, the transceiver can include a receiver and a transmitter, which can be separate or integrated together. Optionally, the terms transceiver, transceiving unit, transceiver, transceiving circuit, etc. can be replaced by each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced by each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced by each other.

[0472] Optionally, the communication device 8100 further includes one or more interface circuits 8104 connected with the memory 8102, which can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 can read the instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0473] The communication device 8100 described in the above embodiments can be a network device or a UE, but the scope of the communication device 8100 described in the present disclosure is not limited to this, and the structure of the communication device 8100 can not be limited by FIG. 8A. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be: (1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, optionally, the above-mentioned IC set can also include storage components for storing data, programs; (3) an ASIC, such as a Modem; (4) a module that can be embedded in other devices; (5) a receiver, UE device, smart UE device, cellular phone, wireless device, handset, mobile unit, vehicle-mounted device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0474] FIG. 8B is a structural schematic diagram of the chip 8200. For the case that the communication device 8100 can be a chip or a chip system, the structural schematic diagram of the chip 8200 shown in FIG. 8B can be referred to, but is not limited thereto.

[0475] The chip 8200 includes one or more processors 8201 configured to invoke instructions to cause the chip 8200 to perform any of the above network access methods.

[0476] In some embodiments, the chip 8200 further includes one or more interface circuits 8202 connected with the memory 8203, which can be configured to receive signals from the memory 8203 or other devices, and can be configured to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201. Alternatively, the terms interface circuit, interface, transceiver pin, transceiver, etc. can be replaced with each other.

[0477] In some embodiments, the chip 8200 further includes one or more memories 8203 configured to store instructions. Alternatively, all or part of the memory 8203 can be outside the chip 8200.

[0478] The present disclosure further provides a storage medium having instructions stored thereon, which, when executed on the communication device 8100, cause the communication device 8100 to perform any of the above methods. Alternatively, the storage medium is an electronic storage medium. Alternatively, the storage medium is a computer readable storage medium, but can also be a storage medium readable by other devices. Alternatively, the storage medium can be a non-transitory storage medium, but can also be a transitory storage medium.

[0479] The present disclosure further provides a program product, which, when executed by the communication device 8100, causes the communication device 8100 to perform any of the above network access methods. Alternatively, the program product is a computer program product.

[0480] The present disclosure further provides a computer program, which, when executed on a computer, causes the computer to perform any of the above network access methods.

[0481] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the features disclosed herein. It is intended that the present disclosure cover any and all variations of the embodiments of the present disclosure described herein and any and all equivalents thereof and it is intended that the present disclosure be limited only by the claims. The specification and examples given herein are to be considered exemplary only, and the true scope and spirit of the present disclosure shall be indicated by the following claims.

[0482] It is to be understood that the embodiments of the present disclosure are not limited to the precise structures as has been described herein and as shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the claims appended hereto.

Claims

1. A network access method, wherein, Performed by a first network function, the method includes: The system receives a first message sent by a second network function. The first message is a message sent by the user equipment (UE) during the first network attach process. The first network uses a first access and supports store-and-forward functionality. The first access is a satellite access. Send a second message to the second network function, the second message containing first information; the first information is used to indicate that the UE has attached to the second network, or the first information is used to indicate that the UE is rejected from attaching to the first network.

2. The method according to claim 1, wherein, When the first network and the second network are the same network, the second access used by the second network is different from the first access.

3. The method according to claim 1 or 2, wherein, The method further includes: The UE is determined to have attached to the second network based on second information, wherein the second information includes at least one of the following: The UE's identification information; First time information, the first time information is used to indicate the time when the first network rejects the UE's attach request, or the time information is used to indicate the time when the UE requests to attach to the first network; The UE's attachment information in the second network.

4. The method according to claim 3, wherein, The UE's attachment information in the second network includes at least one of the following: The UE's identification information; First network information, the first network information includes at least the identification information of the Mobility Management Function (MME) used by the UE to attach to the second network; The second network information includes at least the information about the access network to which the UE is attached.

5. The method according to claim 3 or 4, wherein, Determining whether the UE has attached to the second network based on the second information includes at least one of the following: Based on the first time information, determine whether the UE has attached to the second network after the time indicated by the time information; Based on whether there is attachment information for the UE in the second network, it is determined whether the UE has attached to the second network.

6. The method according to any one of claims 1 to 5, wherein, The first network function is the Home Subscriber Server (HSS), and the second network function is the First Mobility Management Function (MME), or... The first network function is a first mobility management function, and the second network function is a second mobility management function. The second mobility management function is deployed on a satellite, while the first mobility management function is deployed on the ground.

7. The method according to claim 6, wherein, The first network function is the Home Subscriber Server (HSS), the second network function is the first mobility management function, and the first message is used by the UE to request an authentication vector or request the UE's subscription data during the first network attach process.

8. The method according to claim 6, wherein, The first network function is a first mobility management function, the second network function is a second mobility management function, and the first message is used for the UE's attach request in the first network.

9. A network access method, wherein, Performed by a second network function, the method includes: Send a first message to a first network function. The first message is a message sent by the user equipment (UE) during the first network attach process. The first network uses a first access and supports store-and-forward functionality. The first access is a satellite access. The system receives a second message sent by a first network function, the second message containing first information; the first information is used to indicate that the UE has attached to the second network, or to indicate that the UE is refused to attach to the first network.

10. The method according to claim 9, wherein, When the first network and the second network are the same network, the second access used by the second network is different from the first access used by the first network.

11. The method according to claim 9 or 10, wherein, The first network function is a Home Subscriber Server (HSS), the second network function is a first mobility management function, and the method further includes: deleting the attachment information of the first attachment.

12. The method according to any one of claims 9 to 11, wherein the method further comprises: Send a third message to a third network function, the third message being used to indicate that the UE has attached to the second network or to indicate that the UE is refused to attach to the first network, so that the third network function deletes the UE's attachment information in the first network; The third network function is the second mobility management function.

13. The method according to claim 10 or 11, wherein, The first network function is a first mobility management function, the second network function is a second mobility management function, and the method further includes: deleting the UE's attachment information in the first network.

14. The method according to claim 9 or 11, further comprising: A fourth message is sent to the UE, the fourth message being used to refuse the UE from attaching to the first network.

15. A network access method, wherein, Performed by a third network function of the first network, the method includes: The system receives a third message sent by a second network function, the third message being used to indicate that the user equipment (UE) has attached to the second network or to indicate that the UE is denied attachment to the first network; the first network uses a first access and supports store-and-forward functionality; the first access is a satellite access; Delete the UE's attachment information in the first network.

16. The method according to claim 15, wherein, The method further includes: A fifth message is sent to the UE, the fifth message being used to refuse the UE from attaching to the first network.

17. A first network function, wherein, include: The receiving module is configured to receive a first message sent by a second network function. The first message is a message sent by the user equipment (UE) during the first network attach process. The first network uses a first access and supports store-and-forward functionality. The first access is a satellite access. The sending module is configured to send a second message to the second network function, the second message containing first information; the first information is used to indicate that the UE has attached to the second network, or the first information is used to indicate that the UE is rejected from attaching to the first network.

18. A second network function, wherein, include: The sending module is configured to send a first message to a first network function. The first message is a message that the user equipment (UE) performs during the first network attach process. The first network uses a first satellite access and supports store-and-forward functions. The receiving module is configured to receive a second message sent by a first network function, the second message containing first information; the first information is used to indicate that the UE has attached to the second network, or to indicate that the UE is refused to attach to the first network.

19. A third network function, wherein, include: The receiving module is configured to receive a third message sent by a second network function. The third message is used to indicate that the user equipment (UE) has attached to the second network or to indicate that the UE is refused to attach to the first network. The first network uses a first access and supports store-and-forward functionality. The first access is a satellite access. The processing module is configured to delete the UE's attachment information in the first network.

20. A communication system, wherein, The communication system includes a first network function, a second network function, and a third network function; The first network function is used to perform the network access method according to any one of claims 1 to 8; The second network function is used to perform the network access method according to any one of claims 9 to 14; The third network function is used to perform the network access method according to any one of claims 15 to 16.

21. A communication device, wherein, The communication device includes: One or more processors; The processor is configured to invoke instructions to cause the communication device to execute the network access method according to any one of claims 1 to 8, 9 to 14, or 15 to 16.

22. A storage medium, wherein, The storage medium stores instructions that, when executed on a communication device, cause the communication device to perform the network access method according to any one of claims 1 to 8, 9 to 14, or 15 to 16.

23. A program product, wherein, The program product includes a computer program that, when executed by a communication device, enables the communication device to implement any one of 1 to 8, 9 to 14, or 15 to 16 of the network access method.

Images