Communication methods, communication device, communication system, storage medium and computer program product

Abstract

Provided in the embodiments of the present disclosure are communication methods, a communication device, a communication system, a storage medium and a computer program product. A communication method is executed by means of a first core network device and comprises: sending first information to a terminal, wherein the first information is used for indicating the reason why the first core network device rejects a request of the terminal for access to a first public land mobile network (PLMN). The embodiments of the present disclosure enable a communication mechanism to adapt to communication after the introduction of a satellite access network.

Description

Communication methods, communication equipment, communication systems, storage media and computer program products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to an information processing method, communication equipment, communication system, storage medium, and computer program product. Background Technology

[0002] In the field of communication technology, satellite communication has been introduced. However, due to the insufficient number of satellites deployed, satellite networks may suffer from problems such as limited coverage, making it impossible to provide continuous coverage services for terminals.

[0003] Summary of the Invention

[0004] With the introduction of satellite communication, the communication mechanism needs to be adjusted.

[0005] According to a first aspect of the present disclosure, a communication method is provided, the method being performed by a first core network device, the method comprising:

[0006] Send the first message to the terminal;

[0007] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0008] According to a second aspect of the embodiments of this disclosure, a communication method is provided, the method being executed by a terminal, the method comprising:

[0009] Receive the first information sent by the first core network device;

[0010] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0011] According to a third aspect of the embodiments of this disclosure, a communication method is provided, the method comprising:

[0012] The first core network device sends the first information to the terminal;

[0013] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0014] According to a fourth aspect of the present disclosure, a communication device is provided for performing the communication methods of the first and / or second aspects.

[0015] According to a fifth aspect of the present disclosure, a communication system is provided, comprising: a first core network device or a terminal; wherein the first core network device is configured to implement the communication method described in the first aspect, and the terminal is configured to implement the communication method described in the second aspect.

[0016] According to a sixth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a method as described in an optional implementation of the first and / or second aspects.

[0017] According to a seventh aspect of the present disclosure, a computer program product is provided, the computer program product including a computer program or instructions, which, when executed by a processor, implement the method as described in the optional implementations of the first and / or second aspects.

[0018] The embodiments disclosed herein enable the communication mechanism to adapt to communication after the introduction of satellite access networks. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0020] Figure 1A is a schematic diagram of the structure of an information processing system according to an embodiment of the present disclosure.

[0021] Figure 1B is a schematic diagram of a communication architecture according to an embodiment of the present disclosure.

[0022] Figure 1C is a schematic diagram of a communication architecture according to an embodiment of the present disclosure.

[0023] Figure 1D is a schematic diagram illustrating a communication method according to an embodiment of the present disclosure.

[0024] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0025] Figure 3 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0026] Figure 4A is a flowchart illustrating a communication method according to an embodiment of the present disclosure.

[0027] Figure 4B is a flowchart illustrating a communication method according to an embodiment of the present disclosure.

[0028] Figure 5A is a schematic diagram of the structure of a first core network device according to an embodiment of the present disclosure.

[0029] Figure 5B is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure.

[0030] Figure 6A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0031] Figure 6B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0032] This disclosure provides an information processing method, a first core network device, a terminal, a communication device, a communication system, a storage medium, and a computer program product.

[0033] In a first aspect, embodiments of this disclosure provide a communication method, the method being executed by a first core network device, the method comprising:

[0034] Send the first message to the terminal;

[0035] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0036] In the above embodiments, since the first information sent by the first core network device to the terminal indicates the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN), the terminal can understand the reason after receiving the first information, and thus can perform the associated operation according to the reason, thereby improving the communication mechanism and making the communication more reliable.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the reason is at least one of the following:

[0038] Feeder link interruption;

[0039] Network congestion;

[0040] Network connection interrupted.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0042] Send the second information to the terminal;

[0043] The second information is used to indicate a first time, after which the first core network device allows the terminal to re-request access to the first PLMN.

[0044] In the above embodiments, since the second information indicates the first time associated with reconnecting to the first PLMN, the first PLMN can be reconnected in a timely manner based on the first time, making the communication more continuous and stable.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0046] Send third information to the terminal;

[0047] The third information is used to instruct the first area that the first core network device in the first area prohibits the terminal from re-requesting access to the first PLMN.

[0048] In the above embodiments, since the third information instructs the first core network device to prohibit the terminal from re-requesting access to the area corresponding to the first PLMN, the access mechanism is improved, making access more accurate and improving access efficiency.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the first region includes at least one of the following:

[0050] The area consisting of the tracking area (TA);

[0051] The area comprised of the user registration area (RA);

[0052] An area composed of residential communities.

[0053] In the above embodiments, the first region can be indicated in different ways, making the implementation more flexible.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0055] The first region is determined based on the fourth information;

[0056] The fourth piece of information is used to indicate one of the following:

[0057] The satellite's signal coverage area;

[0058] The location of the terminal;

[0059] Operator's regional configuration strategy.

[0060] In the above embodiments, the first region can be determined based on different methods, making the implementation more flexible.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the first information, the second information, and / or the third information are carried in a non-access stratum (NAS) message.

[0062] In the above embodiments, NAS messages can be reused to send the first information, the second information, and / or the third information, which can save signaling overhead and improve efficiency.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the NAS message includes at least one of the following:

[0064] Attach a rejection message;

[0065] Tracking region update TAU rejection message.

[0066] In the above embodiments, the first information can be sent through different NAS messages, which makes the implementation more flexible.

[0067] Secondly, embodiments of this disclosure provide a communication method, which is executed by a terminal, and the method includes:

[0068] Receive the first information sent by the first core network device;

[0069] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the reason is at least one of the following:

[0071] Feeder link interruption;

[0072] Network congestion;

[0073] Network connection interrupted.

[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0075] Receive the second information sent by the terminal;

[0076] The second information is used to indicate a first time, after which the first core network device allows the terminal to re-request access to the first PLMN.

[0077] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0078] Receive third information sent by the terminal;

[0079] The third information is used to instruct the first area that the first core network device in the first area prohibits the terminal from re-requesting access to the first PLMN.

[0080] In conjunction with some embodiments of the first aspect, in some embodiments, the first region includes at least one of the following:

[0081] The area consisting of the tracking area (TA);

[0082] The area comprised of the user registration area (RA);

[0083] An area composed of residential communities.

[0084] In conjunction with some embodiments of the first aspect, in some embodiments, the first region is determined based on fourth information, which is used to indicate one of the following:

[0085] The satellite's signal coverage area;

[0086] The location of the terminal;

[0087] Operator's regional configuration strategy.

[0088] In conjunction with some embodiments of the first aspect, in some embodiments, the first information, the second information, and / or the third information are carried in a non-access stratum (NAS) message.

[0089] In conjunction with some embodiments of the first aspect, in some embodiments, the NAS message includes at least one of the following:

[0090] Attach a rejection message;

[0091] Tracking region update TAU rejection message.

[0092] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0093] Receive broadcast information sent by the first access network device;

[0094] The broadcast information includes at least one of the following:

[0095] Community signage;

[0096] TA identifier;

[0097] Second PLMN identifier.

[0098] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes one of the following:

[0099] If the second PLMN is different from the first PLMN, a fifth message is sent to the first access network device; wherein the fifth message is used to request access to the second PLMN;

[0100] If the second PLMN is the same as the first PLMN, perform the first operation;

[0101] The second PLMN is the PLMN that the terminal requests to access.

[0102] In conjunction with some embodiments of the first aspect, in some embodiments, performing the first operation includes one of the following:

[0103] If the first time limit expires, send the sixth message to the first access network device;

[0104] If the first time has not expired and the area indicated by any of the cell identifiers and / or the area indicated by any of the TA identifiers is included in the first area, the sixth information shall not be sent to the first access network device;

[0105] If the first time has not expired and the area indicated by all the cell identifiers and / or the area indicated by all the TA identifiers is not included in the first area, a sixth message is sent to the first access network device.

[0106] The sixth piece of information is used to request access to the first PLMN.

[0107] Thirdly, this disclosure provides a communication method, the method comprising: a first core network device sending first information to a terminal;

[0108] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0109] Fourthly, embodiments of this disclosure provide a first network device, including: a transceiver module configured to send first information to a terminal;

[0110] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0111] Fifthly, embodiments of this disclosure provide a terminal, including: a transceiver module configured to receive first information sent by a first core network device;

[0112] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0113] In a sixth aspect, embodiments of this disclosure provide a communication device including one or more processors; wherein the communication device is used to perform embodiments or alternative implementations as described in the first and / or second aspects.

[0114] In a seventh aspect, embodiments of this disclosure provide a communication device for performing an implementation of, as described in the first aspect, the second aspect, or an optional implementation of the first and second aspects.

[0115] Eighthly, embodiments of this disclosure provide a communication system, including: a first core network device and a terminal; wherein the first network device is configured to perform the method described in the optional implementation of the first aspect, and the terminal is configured to perform the method described in the optional implementation of the second aspect.

[0116] Ninthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect, the second aspect, or an optional implementation of the first aspect or the second aspect.

[0117] In a tenth aspect, embodiments of this disclosure provide a computer program product, which includes a computer program or instructions that, when executed by a processor, implement the method described in the first aspect, the second aspect, or an optional implementation of the first and second aspects.

[0118] In one aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described as in the first aspect, the second aspect, or alternative implementations of the first and second aspects.

[0119] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system including processing circuitry configured to perform the methods described according to the first aspect, the second aspect, or alternative implementations of the first and second aspects.

[0120] It is understood that the aforementioned first core network equipment, terminal, communication system, storage medium, program product, computer program, chip, or chip system are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0121] This disclosure provides a communication method, a first core network device, a terminal, a communication system, and a storage medium. In some embodiments, terms such as communication method and information processing method are interchangeable, as are terms such as information processing device and communication device, and terms such as information processing system and communication system.

[0122] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0123] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be used interchangeably. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0124] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0125] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0126] In the embodiments disclosed herein, "multiple" refers to two or more.

[0127] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0128] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0129] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0130] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0131] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0132] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0133] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0134] 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,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0135] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0136] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0137] 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," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0138] 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", and "client" can be used interchangeably.

[0139] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

[0140] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0141] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0142] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0143] Furthermore, each element, each row, or each column in the table of this 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.

[0144] Figure 1A is a schematic diagram of the structure of an information processing system 100 according to an embodiment of the present disclosure.

[0145] As shown in Figure 1A, the information processing system 100 may include: terminal 101 and network device 102.

[0146] In some embodiments, network device 102 may include at least one of an access network device and a core network device.

[0147] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things (IoT) device or terminal, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0148] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system.

[0149] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0150] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0151] In some embodiments, the core network equipment may be a single device, a first network element, or a second network element, or multiple devices or a group of devices, respectively including all or part of the aforementioned first network element and / or second network element. Both the first network element and / or the second network element may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and 6G Core Network (6GCN).

[0152] In some embodiments, the first network element may be any function, network element, or entity in the core network that can be used for registration, connection, and / or mobility management.

[0153] In some embodiments, the name of the first network element is not limited, and it may be, for example, one of the access and mobility management function, session management function, and policy control function.

[0154] In some embodiments, the second network element may be any function, network element, or entity in the core network that can implement the control plane and / or user plane.

[0155] In some embodiments, the name of the second network element is not limited, and it may be, for example, one of the Packet Data Unit Session Connection Anchored User Plane Function and the Intermediate User Plane Function.

[0156] It is understood that the information processing system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0157] The following embodiments of this disclosure can be applied to the information processing system 100 shown in FIG1A, or some of its components, but are not limited thereto. The components shown in FIG1A are illustrative. The information processing system may include all or some of the components in FIG1A, or may include other components outside of FIG1A. The number and form of each component are arbitrary. The connection relationship between the components is illustrative. The components may be unconnected or connected. The connection can be in any way, either direct or indirect, wired or wireless.

[0158] The embodiments disclosed herein 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), 6th generation mobile communication system (6G), 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A combined with 5G, 5G combined with 5G, 5G combined with 6G, etc.) for application.

[0159] In some embodiments, please refer to Figures 1B and 1C, which are schematic diagrams of network deployment based on satellite-borne functions. Figure 1B shows the architecture in which some Mobility Management Entity (MME) functions are deployed on a satellite; Figure 1C shows the architecture in which the core network is deployed on a satellite.

[0160] In some embodiments, satellite networks may be unable to provide continuous coverage services due to insufficient satellite deployment and limited coverage. This discontinuous coverage includes interruptions in the connection between the satellite and the UE (service link) or the connection between the satellite and the ground receiving station (feeder link), meaning that the service link and the feeder link cannot exist simultaneously. In this case, to enable certain services (e.g., latency-tolerant services), the network functions on the satellite need to perform data and / or signaling storage and forwarding functions. For example, for Figure 1B, the onboard MME needs to perform data storage and forwarding functions, and for Figure 1C, the core network functions or servers deployed on the satellite need to perform data storage and forwarding functions.

[0161] In some embodiments, referring to Figure 1D, in the "Save and Forward (S&F) Satellite Operation" mode, the end-to-end exchange of signaling or data services is now divided into a combination of two steps processed at different times (steps A and B in Figure 1D). In step A, signaling / data exchange between the UE and the satellite is initiated, while the satellite is unable to connect to the terrestrial network at this time (i.e., the satellite can use the service link without a feeder link connection). In step B, a connection is established between the satellite and the terrestrial network, enabling communication between them, but the service link between the UE and the satellite is unavailable at this time. Therefore, the satellite needs to perform store and forward operations for data or signaling during the process of moving from connecting to the UE in step A to connecting to the terrestrial network in step B.

[0162] In some embodiments, satellite support for S&F operations is particularly well-suited for latency-tolerant or non-real-time IoT services provided by non-Geostationary Satellite Orbit (NGSO) satellite networks.

[0163] In some embodiments, if the satellite is operating in S&F mode, when the UE initiates an Attach or Tracking Area Update (TAU) procedure, the MME can provide the UE with an S&F wait timer and a list of satellite IDs during the acceptance or rejection of the attach or TAU procedure. The wait timer indicates to the UE the time to wait between accessing the same Public Land Mobile Network (PLMN) using one satellite from the list of satellite IDs. The list of satellite IDs indicates the next satellite the UE can access after the wait timer expires.

[0164] In some embodiments, if a legacy UE (i.e., one that does not support S&F mode) accesses a satellite that supports S&F mode, when the legacy UE initiates an attach or TAU procedure to the network, the MME will reject the NAS request (e.g., attach request or TAU request) due to feeder link unavailability. However, the rejection reason should not be set to be due to the satellite performing S&F, as the legacy UE does not support this feature. Nevertheless, a legacy UE can still access the network through a satellite that supports S&F mode. How to demonstrate to the legacy UE that it will continue to use the satellite to access the same PLMN in the future is a problem that needs to be considered.

[0165] Figure 2 is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 2, the present disclosure relates to an information processing method used in an information processing system 100, the method comprising:

[0166] Step S2101: The first core network device sends the first information to the terminal.

[0167] In some embodiments, the terminal receives first information sent by the first core network device.

[0168] In some embodiments, the first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public terrestrial mobile network (PLMN).

[0169] In some embodiments, the reason is at least one of the following:

[0170] Feeder link interruption;

[0171] Network congestion;

[0172] Network connection interrupted. But this is not the only one.

[0173] In some embodiments, the first core network device is an MME, such as a spaceborne MME, but not limited thereto.

[0174] In some embodiments, the terminal does not support S&F mode, but the MME does support S&F mode.

[0175] In some embodiments, when the first core network device supports S&F mode, the first core network device sends first information to the terminal.

[0176] In some embodiments, the first core network device sends a non-access stratum (NAS) message to the terminal.

[0177] In some embodiments, the NAS message includes the first information.

[0178] In some embodiments, the NAS message includes at least one of the following:

[0179] Attach a rejection message;

[0180] Tracking region update TAU rejection message.

[0181] In some embodiments, the first information may also be referred to as the cause information.

[0182] It should be noted that the reasons mentioned are not limited to feeder link interruption, network congestion and / or network connection interruption, but are only illustrative examples; the reasons can be any cause related to network (e.g., networks related to satellite communications) communication failure or temporary connection interruption, such as new causes that emerge as the network evolves, and the above examples do not represent a limitation of this application.

[0183] In step S2102, the first core network device sends the second information to the terminal.

[0184] In some embodiments, the terminal receives second information sent by the first core network device.

[0185] In some embodiments, the second information is used to indicate a first time.

[0186] In some embodiments, after the first time period, the first core network device allows the terminal to re-request access to the first PLMN.

[0187] In some embodiments, the terminal may re-request access to the first PLMN after receiving the second information.

[0188] In some embodiments, the terminal may re-request access to the first PLMN after receiving the first information.

[0189] In some embodiments, the terminal may be the terminal that re-requests access to the first PLMN after communication is interrupted.

[0190] In some embodiments, the second information may be referred to as time information.

[0191] In some embodiments, the NAS message includes the second information.

[0192] In some embodiments, the NAS message includes at least one of the following:

[0193] Attach a rejection message;

[0194] Tracking region update TAU rejection message.

[0195] Step S2103: The first core network device determines the first area.

[0196] In some embodiments, the first region is determined based on fourth information.

[0197] In some embodiments, the fourth information is used to indicate one of the following:

[0198] The satellite's signal coverage area;

[0199] The location of the terminal;

[0200] Operator's regional configuration strategy.

[0201] In some embodiments, the satellite's signal coverage area can be the signal coverage area of ​​a list of satellites. The list can be configured by the network and contains identifiers for at least one satellite.

[0202] In some embodiments, the first core network device determines the first region based on the signal coverage areas of the satellites in the list.

[0203] In some embodiments, the first core network device determines the first region based on the location of the terminal.

[0204] In some embodiments, the first core network device determines the first region based on the operator's regional configuration policy.

[0205] In some embodiments, the first region includes at least one of the following:

[0206] The area consisting of the tracking area (TA);

[0207] The area comprised of the user registration area (RA);

[0208] An area composed of residential communities.

[0209] In step S2104, the first core network device sends third information to the terminal.

[0210] In some embodiments, the terminal receives third information sent by the first core network device.

[0211] In some embodiments, the third information is used to indicate a first region.

[0212] In some embodiments, the first core network device in the first region prohibits the terminal from re-requesting access to the first PLMN.

[0213] In some embodiments, the third information may indicate the identifier of the first area, such as a TA identifier, RA identifier, and / or cell identifier.

[0214] In some embodiments, the third information may also be referred to as regional information.

[0215] In some embodiments, the NAS message includes the third information.

[0216] In some embodiments, the NAS message includes at least one of the following:

[0217] Attach a rejection message;

[0218] Tracking region update TAU rejection message.

[0219] Step S2105: The first access network device sends broadcast information to the terminal.

[0220] In some embodiments, the terminal receives broadcast information sent by the first access network device.

[0221] In some embodiments, the first access network device is deployed on a satellite.

[0222] In some embodiments, the broadcast information includes at least one of the following:

[0223] Community signage;

[0224] TA identifier;

[0225] Second PLMN identifier.

[0226] Step S2106: The terminal performs the operation.

[0227] In some embodiments, the operation is an operation associated with accessing the PLMN and / or access network equipment.

[0228] In some embodiments, if the second PLMN is different from the first PLMN, the fifth information is sent to the first access network device.

[0229] In some embodiments, the fifth information is used to request access to the second PLMN.

[0230] In some embodiments, if the second PLMN is the same as the first PLMN, the first operation is performed.

[0231] In some embodiments, the second PLMN is the PLMN that the terminal requests to access.

[0232] In some embodiments, if the first time expires, a sixth message is sent to the first access network device.

[0233] In some embodiments, if the first time has not expired and the area indicated by any of the cell identifiers and / or the area indicated by any of the TA identifiers is included in the first area, the sixth information is not sent to the first access network device.

[0234] In some embodiments, if the first time has not expired and the area indicated by all the cell identifiers and / or the area indicated by all the TA identifiers is not included in the first area, a sixth message is sent to the first access network device.

[0235] In some embodiments, the sixth information is used to request access to the first PLMN.

[0236] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0237] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0238] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0239] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0240] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0241] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0242] The information processing method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2106. For example, step S2101 can be implemented as an independent embodiment; step S2102 can be implemented as an independent embodiment; step S2103 can be implemented as an independent embodiment; step S2104 can be implemented as an independent embodiment; step S2105 can be implemented as an independent embodiment; step S2106 can be implemented as an independent embodiment; a combination of steps S2101, S2103, S2104, S2105, and S2106 can be implemented as an independent embodiment; a combination of steps S2101, S2102, S2103, S2104, S2105, and S2106 can be implemented as an independent embodiment.

[0243] In some embodiments, step S2102 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0244] In some embodiments, steps S2103 and S2104 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0245] In some embodiments, steps S2102, S2103 and S2104 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0246] In the embodiments disclosed herein, each embodiment can be implemented individually or in combination with each other, and the steps in each embodiment can be distinguished by their order.

[0247] Figure 3 is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 3, the present disclosure relates to an information processing method, which includes:

[0248] Step S3101: The first core network device sends the first information to the terminal.

[0249] In some embodiments, the first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public terrestrial mobile network (PLMN).

[0250] The optional implementations of step S3101 can be found in the optional implementations of step S2101 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0251] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0252] An information processing method according to an embodiment of this disclosure includes:

[0253] Step S3201: The first core network device sends the first information to the terminal;

[0254] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0255] The optional implementation of step S3201 can be found in the optional implementation of step S2102 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0256] In some embodiments, the reason is at least one of the following:

[0257] Feeder link interruption;

[0258] Network congestion;

[0259] Network connection interrupted.

[0260] In some embodiments, the method further includes:

[0261] Send the second information to the terminal;

[0262] The second information is used to indicate a first time, after which the first core network device allows the terminal to re-request access to the first PLMN.

[0263] In some embodiments, the method further includes:

[0264] Send third information to the terminal;

[0265] The third information is used to instruct the first area that the first core network device in the first area prohibits the terminal from re-requesting access to the first PLMN.

[0266] In some embodiments, the first region includes at least one of the following:

[0267] The area consisting of the tracking area (TA);

[0268] The area comprised of the user registration area (RA);

[0269] An area composed of residential communities.

[0270] In some embodiments, the method further includes:

[0271] The first region is determined based on the fourth information;

[0272] The fourth piece of information is used to indicate one of the following:

[0273] The satellite's signal coverage area;

[0274] The location of the terminal;

[0275] Operator's regional configuration strategy.

[0276] In some embodiments, the NAS message includes the first information.

[0277] In some embodiments, the NAS message includes at least one of the following:

[0278] Attach a rejection message;

[0279] Tracking region update TAU rejection message.

[0280] In some embodiments, the NAS message includes at least one of the following:

[0281] Attach a rejection message;

[0282] Tracking region update TAU rejection message.

[0283] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0284] An information processing method according to an embodiment of this disclosure includes:

[0285] Step S3301: The terminal receives the first information sent by the first core network device;

[0286] The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

[0287] The optional implementation of step S3301 can be found in the optional implementation of step S2101 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0288] In some embodiments, the reason is at least one of the following:

[0289] Feeder link interruption;

[0290] Network congestion;

[0291] Network connection interrupted.

[0292] In some embodiments, the method further includes:

[0293] Receive the second information sent by the terminal;

[0294] The second information is used to indicate a first time, after which the first core network device allows the terminal to re-request access to the first PLMN.

[0295] In some embodiments, the method further includes:

[0296] Receive third information sent by the terminal;

[0297] The third information is used to instruct the first area that the first core network device in the first area prohibits the terminal from re-requesting access to the first PLMN.

[0298] In some embodiments, the first region includes at least one of the following:

[0299] The area consisting of the tracking area (TA);

[0300] The area comprised of the user registration area (RA);

[0301] An area composed of residential communities.

[0302] In some embodiments, the first region is determined based on fourth information, which indicates one of the following:

[0303] The satellite's signal coverage area;

[0304] The location of the terminal;

[0305] Operator's regional configuration strategy.

[0306] In some embodiments, the NAS message includes the first information.

[0307] In some embodiments, the NAS message includes at least one of the following:

[0308] Attach a rejection message;

[0309] Tracking region update TAU rejection message.

[0310] In some embodiments, the NAS message includes at least one of the following:

[0311] Attach a rejection message;

[0312] Tracking region update TAU rejection message.

[0313] In some embodiments, the method further includes:

[0314] Receive broadcast information sent by the first access network device;

[0315] The broadcast information includes at least one of the following:

[0316] Community signage;

[0317] TA identifier;

[0318] Second PLMN identifier.

[0319] In some embodiments, the method further includes one of the following:

[0320] If the second PLMN is different from the first PLMN, a fifth message is sent to the first access network device; wherein the fifth message is used to request access to the second PLMN;

[0321] If the second PLMN is the same as the first PLMN, perform the first operation;

[0322] The second PLMN is the PLMN that the terminal requests to access.

[0323] In some embodiments, performing the first operation includes one of the following:

[0324] If the first time limit expires, send the sixth message to the first access network device;

[0325] If the first time has not expired and the area indicated by any of the cell identifiers and / or the area indicated by any of the TA identifiers is included in the first area, the sixth information shall not be sent to the first access network device;

[0326] If the first time has not expired and the area indicated by all the cell identifiers and / or the area indicated by all the TA identifiers is not included in the first area, a sixth message is sent to the first access network device.

[0327] The sixth piece of information is used to request access to the first PLMN.

[0328] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0329] This disclosure relates to a communication method, which may include:

[0330] In some embodiments, the MME sends a first message to the UE, the first message indicating the reason for rejecting the UE's request to access the first PLMN.

[0331] In some embodiments, the information sent by the MME to the UE may also include second information, wherein the second information is time information, used to indicate that after a specified time period, the UE is allowed to re-initiate an access request to the first PLMN.

[0332] In some embodiments, the information sent by the MME to the UE may also include third information, wherein the third information is area information, used to indicate that the UE is prohibited from re-initiating the access request of the first PLMN within the area.

[0333] In some embodiments, the region information is at least one of the following:

[0334] A region consisting of a set of TAs;

[0335] User Registration Area (RA);

[0336] An area composed of residential communities.

[0337] In some embodiments, the region information is determined by the MME based on at least one of the following:

[0338] The satellite coverage areas in the satellite identifier list;

[0339] The current location of the UE;

[0340] Operator's regional configuration strategy.

[0341] In some embodiments, the MME sends the first, second, and third pieces of information to the UE via NAS messages. The NAS messages include one of the following: an attach rejection message and a tracking area update rejection message.

[0342] In some embodiments, the UE stores the first, second, and third information.

[0343] In some embodiments, the UE receives a broadcast message from a first base station, the broadcast message containing a cell identifier and / or a tracking area identifier (TAI).

[0344] In some embodiments, the UE determines whether to access the PLMN based on the first, second, and third pieces of information, including:

[0345] If the second PLMN requested by the UE is different from the first PLMN, the UE sends an access request to the second PLMN to the first base station.

[0346] In some embodiments, if the UE requests access to the first PLMN, then:

[0347] If the second information indication time expires, the UE sends an access request to the first base station to access the first PLMN.

[0348] If the second information indication time has not expired, and at least one of the broadcast cell identifier and / or tracking area identity (TAI) is included in the area information indicated by the third information, the UE will not send an access request to the first base station to access the first PLMN.

[0349] If the second information indication time has not expired, and all cell identifiers and / or TAIs broadcast are not included in the area information indicated by the third information, the UE sends an access request to the first base station to access the first PLMN.

[0350] Example 1

[0351] As shown in Figure 4A

[0352] In this scenario, the MME is divided into two parts: onboard MME functionality and ground-based MME functionality. Multiple onboard MMEs located on different satellites and ground-based MMEs together constitute a complete MME function. Onboard MMEs and eNBs can be deployed on the same satellite.

[0353] Please refer again to Figure 4A, which provides a communication method including the following steps:

[0354] Step S4101: Send an attach request message.

[0355] In some embodiments, at time T0, the eNB-1 carrying the satellite provides coverage to the UE, the UE sends an attach request (i.e., an attach request message) to the eNB-1, and further sends an attach request to the MME-1 carrying the satellite to access the PLMN.

[0356] Step S4102: Send an attach rejection message.

[0357] In some embodiments, when an attach request is received, the UE’s onboard MME-1 determines that the terminal does not support S&F mode. The onboard MME-1 with S&F capability detects that the feeder link of the ground MME is unavailable. The onboard MME can store the attach request and related information as the UE context.

[0358] In some embodiments, the onboard MME can send an attach rejection message to the UE, indicating that the attach procedure cannot be performed and explaining the reasons for rejection, such as network congestion.

[0359] In some embodiments, a wait timer is used to indicate that the UE can retry the NAS procedure after the wait timer expires. The wait timer value can be set to the waiting time for the next satellite of the satellite access network to provide coverage to the area of ​​the UE.

[0360] In some embodiments, the onboard MME sends area information along with information about the wait timer to the terminal (corresponding to sending the first information). Area information, such as TAIs, is used to indicate that the wait timer is valid in that area.

[0361] Step S4103: Store the rejection reason value, the wait timer, and the region information.

[0362] In some embodiments, the UE stores a rejection reason value, a wait timer, and area information.

[0363] Step S4104: The terminal performs context synchronization.

[0364] In some embodiments, when the onboard MME-1 detects that the feeder link has become available, UE context synchronization is performed between the onboard MME-1 and the ground MME. Additionally, the ground MME is provided with a list of satellite IDs indicating satellites that will be able to provide coverage in the future.

[0365] Step S4105: Store the UE context and satellite ID list.

[0366] In some embodiments, the ground MME stores the UE context and a list of satellite IDs.

[0367] Step S4106: Send a broadcast message.

[0368] In some embodiments, at time T1, the UE is moving to a new area. In this area, eNB2 on a satellite provides coverage and broadcasts TAIs.

[0369] In some embodiments, the broadcast message may be SIB1.

[0370] Step S4107: Determine that the area information contains a TAI and the waiting timer has not expired.

[0371] Step S4107a: Determine that the area information contains a TAI and wait for the timer to expire.

[0372] In some embodiments, when the UE receives an SIB message in the area, based on the waiting timer and area information stored in the UE, at least one broadcast TAIs is in the area information (TAI list), the waiting timer is running, and the UE cannot access the PLMN via eNB2.

[0373] Step S4108: Send an attach request.

[0374] In some embodiments, after the waiting timer expires, the UE resends the attach request (i.e., the attach request message) to the onboard MME-2 via the onboard eNB-2.

[0375] Step S4109: Send an attach accept message.

[0376] In some embodiments, the MME-2 accepts attachment requests. The onboard MME-2 sends an attach accept (i.e., attach accept message) to the UE. Once the feeder link becomes available, the UE context can be synchronized with the MME on the ground.

[0377] Step S4110: Perform terminal context synchronization.

[0378] Example 2:

[0379] In this scenario, the MME is divided into two parts: the onboard MME and the ground-based MME. Multiple onboard MMEs and ground-based MMEs located on different satellites together constitute a complete MME. The onboard MME and eNB are deployed on the same satellite.

[0380] As shown in Figure 4B, a communication method is provided, including the following steps:

[0381] Step S4201: Send an attach request message.

[0382] In some embodiments, at time T0, the eNB-1 carrying the satellite provides coverage to the UE, the UE sends an attach request (i.e., an attach request message) to the eNB-1, and further sends an attach request to the MME-1 carrying the satellite to access the PLMN.

[0383] Step S4202: Send an attach rejection message.

[0384] In some embodiments, when an attach request is received, the UE’s onboard MME-1 realizes that the terminal does not support S&F mode. The onboard MME-1 with S&F capability detects that the feeder link of the ground MME is unavailable. The onboard MME can store the attach request and related information as the UE context.

[0385] In some embodiments, the onboard MME can send an attach rejection message to the UE, indicating that the attach procedure cannot be performed and specifying a set of reasons for rejection, such as network congestion.

[0386] In some embodiments, a wait timer is used to indicate that the UE can retry the NAS procedure after the wait timer expires. The wait timer value can be set to the waiting time for the next satellite of the satellite access network to provide coverage to the area of ​​the UE.

[0387] In some embodiments, the onboard MME sends area information along with wait timer information to the terminal. Area information, such as TAIs, is used to indicate that the wait timer is valid within that area.

[0388] Step S4203: Store the rejection reason value, the wait timer, and the region information.

[0389] In some embodiments, the UE stores a rejection reason value, a wait timer, and area information.

[0390] Step S4204: Perform terminal context synchronization.

[0391] In some embodiments, when the onboard MME-1 detects that the feeder link has become available, UE context synchronization is performed between the onboard MME-1 and the ground MME. Additionally, the ground MME is provided with a list of satellite IDs indicating satellites that will be able to provide coverage in the future.

[0392] Step S4205: Store the UE context and satellite ID list.

[0393] In some embodiments, the ground MME stores the UE context and a list of satellite IDs.

[0394] Step S4206: Send a broadcast message.

[0395] In some embodiments, at time T1, the UE is moving to a new area. In this area, eNB2 on a satellite provides coverage and broadcasts TAIs.

[0396] In some embodiments, the broadcast message may be SIB1.

[0397] Step S4207: Determine that none of the TAIs broadcast are in the area information.

[0398] In some embodiments, when the UE receives an SIB message in the area, based on the waiting timer and area information stored in the UE, each broadcast TAIs is not in the area information (TAI list). Regardless of whether the waiting timer has expired, the UE can access the PLMN through eNB2.

[0399] Step S4208: Send an attach request message.

[0400] In some embodiments, the UE retransmits the attach request (i.e., the attach request message) to the onboard MME-2 via the onboard eNB-2.

[0401] Step S4209: Send an attach response message.

[0402] In some embodiments, the MME-2 accepts the attach request. The onboard MME-2 sends an attach accept (i.e., attach response message) to the UE. Once the feeder link becomes available, the UE context can be synchronized with the MME on the ground.

[0403] Step S4210: Perform terminal context synchronization.

[0404] In this embodiment of the disclosure, some or all of the steps and their optional implementations can be arbitrarily combined with some or all of the steps in other embodiments, or arbitrarily combined with the optional implementations in other embodiments.

[0405] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed, which includes units or modules for implementing the steps performed by the terminal in any of the above methods. Another apparatus is also proposed, including units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods. Here, the core network device may include, but is not limited to, at least one of the following: a first network element and a second network element, etc.

[0406] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. 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 in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which 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 functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0407] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a Digital Signal Processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an Application-Specific Integrated Circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Units (NPUs), Tensor Processing Units (TPUs), and Deep Learning Processing Units (DPUs).

[0408] Figure 5A is a schematic diagram of the structure of a first core network device 5100 provided in an embodiment of this disclosure. As shown in Figure 5A, the first core network device 5100 includes a first transceiver module 5101. In some embodiments, the first transceiver module 5101 is used to send first information and / or send second information, etc. Optionally, the first transceiver module 5101 is used to perform at least one of the sending and / or receiving steps performed by the first network device 5100 in any of the above methods, which will not be elaborated here. In some embodiments, the first network device 5100 may include a first processing module.

[0409] Figure 5B is a schematic diagram of the structure of a terminal 5200 provided in an embodiment of this disclosure. As shown in Figure 5B, the terminal 5200 includes a second transceiver module 5201. Optionally, the second transceiver module 5201 is used to perform at least one of the sending and / or receiving steps performed by the terminal 5200 in any of the above methods, which will not be described in detail here. In some embodiments, the terminal 5200 may include a second processing module.

[0410] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver. For example, the first transceiver module described above includes a first transmitting module and / or a first receiving module. For example, the second transceiver module described above includes a second transmitting module and / or a second receiving module.

[0411] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0412] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal, a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0413] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0414] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101 and / or steps S2102 and / or steps S2103 and / or steps S2105, etc., but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S2104 and / or steps S2106, etc., but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0415] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and can be used to receive data from the memories 6103 or other devices, and to send data to the memories 6103 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6103 and send that data to the processor 6101.

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

[0417] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.

[0418] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0419] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of the memories 6203 may be located outside chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0420] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101 and / or S2102 and / or S2103 and / or S2105, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S2104 and / or S2106, but not limited thereto).

[0421] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0422] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 6100, cause the communication device 6100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0423] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0424] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method characterized by comprising: The method is executed by a first core network device, and the method includes: Send the first message to the terminal; The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

2. The method of claim 1, wherein, The reason includes at least one of the following: Feeder link interruption; Network congestion; Network connection interrupted.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Send the second information to the terminal; The second information is used to indicate a first time, after which the first core network device allows the terminal to re-request access to the first PLMN.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Send third information to the terminal; The third information is used to instruct the first area that the first core network device in the first area prohibits the terminal from re-requesting access to the first PLMN.

5. The method of claim 4, wherein, The first region includes at least one of the following: The area consisting of the tracking area (TA); The area comprised of the user registration area (RA); An area composed of residential communities.

6. The method according to claim 4 or 5, characterized in that, The method further includes: The first region is determined based on the fourth information; The fourth piece of information is used to indicate one of the following: The satellite's signal coverage area; The location of the terminal; Operator's regional configuration strategy.

7. The method according to any one of claims 1 to 6, characterized in that, The first information, the second information, and / or the third information are carried in the non-access stratum (NAS) message.

8. The method of claim 7, wherein, The NAS message includes at least one of the following: Attach a rejection message; Tracking region update TAU rejection message.

9. A communication method characterized by comprising: The method is executed by a terminal, and the method includes: Receive the first information sent by the first core network device; The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

10. The method of claim 9, wherein, The reason includes at least one of the following: Feeder link interruption; Network congestion; Network connection interrupted.

11. The method according to claim 9 or 10, characterized in that, The method further includes: Receive the second information sent by the terminal; The second information is used to indicate a first time, after which the first core network device allows the terminal to re-request access to the first PLMN.

12. The method according to any one of claims 9 to 11, characterized in that, The method further includes: Receive third information sent by the terminal; The third information is used to instruct the first area that the first core network device in the first area prohibits the terminal from re-requesting access to the first PLMN.

13. The method of claim 12, wherein, The first region includes at least one of the following: The area consisting of the tracking area (TA); The area comprised of the user registration area (RA); An area composed of residential communities.

14. The method according to claim 12 or 13, characterized in that, The first region is determined based on fourth information, which indicates one of the following: The satellite's signal coverage area; The location of the terminal; Operator's regional configuration strategy.

15. The method according to any one of claims 9 to 14, characterized in that, The first information, the second information, and / or the third information are carried in the non-access stratum (NAS) message.

16. The method of claim 15, wherein, The NAS message includes at least one of the following: Attach a rejection message; Tracking region update TAU rejection message.

17. The method according to any one of claims 9 to 16, characterized in that, The method further includes: Receive broadcast information sent by the first access network device; The broadcast information includes at least one of the following: Community signage; TA identifier; Second PLMN identifier.

18. The method of claim 17, wherein, The method also includes one of the following: If the second PLMN is different from the first PLMN, a fifth message is sent to the first access network device; wherein the fifth message is used to request access to the second PLMN; If the second PLMN is the same as the first PLMN, perform the first operation; The second PLMN is the PLMN that the terminal requests to access.

19. The method of claim 18, wherein, The execution of the first operation includes one of the following: If the first time limit expires, send the sixth message to the first access network device; If the first time has not expired and the area indicated by any of the cell identifiers and / or the area indicated by any of the TA identifiers is included in the first area, the sixth information shall not be sent to the first access network device; If the first time has not expired and the area indicated by all the cell identifiers and / or the area indicated by all the TA identifiers is not included in the first area, a sixth message is sent to the first access network device. The sixth piece of information is used to request access to the first PLMN.

20. A communication method, characterized in that, The method includes: The first core network device sends the first information to the terminal; The first information is used to indicate the reason why the first core network device rejects the terminal's request to access the first public land mobile network (PLMN).

21. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1 to 8 or claims 9 to 19.

22. A communication system, characterized in that, include: A first core network device and a terminal; wherein the first core network device is configured to implement the communication method of any one of claims 1 to 8, and the terminal is configured to implement the communication method of any one of claims 9 to 19.

23. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 8 or claims 9 to 19.

24. A computer program product, said computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the communication method according to any one of claims 1 to 8 or claims 9 to 19.

Images