Network parameter adjustment method, and electronic apparatus and computer program product

Abstract

Provided in the embodiments of the present disclosure are a network parameter adjustment method, and an electronic apparatus and a computer program product. The method comprises: a mobility management entity (MME) receiving a first store-and-forward parameter configured by a configuration management network element; and on the basis of the first store-and-forward parameter, the MME sending a second store-and-forward parameter to a user equipment (UE).

Description

Network parameter adjustment methods, electronic devices and computer program products

[0001] Cross-references to related applications

[0002] This application is based on and claims priority to Chinese patent application CN202510368208.7, filed on March 26, 2025, entitled “Network Parameter Adjustment Method, Electronic Device and Computer Program Product”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communications, and more specifically, to a method for adjusting network parameters, an electronic device, and a computer program product. Background Technology

[0004] In traditional cellular networks, terrestrial base stations maintain a constant connection with the core network, enabling real-time signaling and data transmission. However, in satellite-based store-and-forward (S&F) mode, communication between the UE and the core network is affected by longer latency and discontinuous connections due to satellite orbital motion and intermittent link availability. Therefore, how to dynamically adjust relevant network parameters (such as S&F waiting timers and monitoring lists) based on UE mobility, ephemeris information, satellite coverage changes, and satellite link status in S&F mode to optimize UE network connectivity, improve network reliability, and enhance system efficiency is a pressing technical problem that needs to be solved. Summary of the Invention

[0005] This disclosure provides a method for adjusting network parameters, which at least solves the problem in related technologies that it is impossible to dynamically adjust store-and-forward parameters.

[0006] According to one embodiment of this disclosure, a network parameter adjustment method is provided, comprising: a mobility management entity (MME) receiving first store-and-forward parameters configured by a configuration management network element; and the MME sending second store-and-forward parameters to a user equipment (UE) based on the first store-and-forward parameters.

[0007] According to another embodiment of this disclosure, a network parameter adjustment method is provided, comprising: a UE receiving second store-and-forward parameters from an MME; the UE adjusting communication behavior based on the second store-and-forward parameters.

[0008] According to yet another embodiment of this disclosure, a network device is also provided, the network device including a receiver, a transmitter, and a processor, the network device being configured to perform the steps of any of the above method embodiments via at least one of the receiver, the transmitter, and the processor.

[0009] According to yet another embodiment of this disclosure, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0010] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0011] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments. Attached Figure Description

[0012] Figure 1 is a hardware structure block diagram of a mobile terminal for a network parameter adjustment method according to an embodiment of the present disclosure;

[0013] Figure 2 is a flowchart of a network parameter adjustment method according to an embodiment of the present disclosure;

[0014] Figure 3 is another flowchart of the network parameter adjustment method according to an embodiment of the present disclosure;

[0015] Figure 4 is a structural block diagram of a network device according to an embodiment of the present disclosure;

[0016] Figure 5 is a flowchart of configuring the MME and eNB to add S&F related parameters according to an embodiment of this disclosure;

[0017] Figure 6 is a flowchart of the MME dynamically updating the second store-and-forward parameters according to an embodiment of this disclosure;

[0018] Figure 7 is a flowchart of a UE adjusting its communication behavior according to a second store-and-forward parameter according to an embodiment of this disclosure. Detailed Implementation

[0019] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.

[0020] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of the embodiments of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0021] In related technologies, with the development of Non-Terrestrial Network (NTN) technology, satellite-based communication has become an important supplement to cellular networks, especially in remote areas, emergency scenarios, and hotspot areas. S&F mode allows User Equipment (UE) to establish a connection with the satellite when the serving link is available, with the satellite network element temporarily storing signaling and / or data, and forwarding the signaling and / or data to the terrestrial core network when the feeder link is available. Existing 3GPP standards have defined the basic mechanisms of S&F mode, including how the UE perceives the S&F mode, how the UE adjusts some behaviors according to received S&F-related parameters to adapt to the characteristics of this mode, and how the Mobility Management Entity (MME) adapts relevant timers (such as the mobile reachability timer and implicit deregistration timer) to adapt to the S&F operation mode. However, current technology has not fully considered how the MME dynamically adjusts S&F-related parameters to adapt to changes in UE mobility, ephemeris information, and satellite coverage.

[0022] The method embodiments provided in this application can be executed in a mobile terminal, computer terminal, or similar computing device. Taking a mobile terminal as an example, FIG1 is a hardware structure block diagram of a mobile terminal for the network parameter adjustment method of this disclosure. As shown in FIG1, the mobile terminal may include one or more (only one is shown in FIG1) processors 102 (processor 102 may include, but is not limited to, processing devices such as microprocessors MCUs or programmable logic devices FPGAs) and a memory 104 for storing data. The mobile terminal may also include a transmission device 106 for communication functions and an input / output device 108. It will be understood by those skilled in the art that the structure shown in FIG1 is only illustrative and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than shown in FIG1, or have a different configuration than shown in FIG1.

[0023] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the network parameter adjustment method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0024] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0025] This embodiment provides a network parameter adjustment method. Figure 2 is a flowchart of the network parameter adjustment method according to this embodiment. As shown in Figure 2, the process includes the following steps:

[0026] Step S202: The MME receives the first store-and-forward parameters configured by the configuration management network element.

[0027] In one exemplary embodiment, the first store-forward parameter includes at least one of the following: store-forward support indication (SfSupportInd); ephemerisInfoSet; and non-access stratum (NAS) counter management mode (nasCounterMgmtMode).

[0028] In one exemplary embodiment, the NAS counter management mode includes at least one of the following: default mode: when the UE re-accesses, the MME obtains the updated UE context; separate counters per satellite mode: the MME maintains an independent NAS counter for each satellite; and overflow handling mode: when the MME experiences an integrity check failure, the MME increments the uplink NAS overflow counter.

[0029] In step S204, the MME sends the second store-and-forward parameter to the UE based on the first store-and-forward parameter.

[0030] In this embodiment, the MME sends a second store-and-forward parameter to the UE based on the first store-and-forward parameter. When creating or updating the MME and evolved Node B (eNB) instances, the NFMS_P (i.e., the aforementioned configuration management network element) configures the S&F support indicator (SfSupportInd) and the ephemeris information set (ephemerisInfoSet). The MME also includes a NAS counter management mode (nasCounterMgmtMode). These configurations provide the prerequisites for the MME to handle communication in S&F mode. When the UE enters a network area in S&F mode, the MME dynamically generates and updates the "S&F waiting timer" and the "S&F monitoring list" based on these basic parameters configured by NFMS_P, combined with the current UE mobility state, ephemeris information, and satellite link status.

[0031] In one exemplary embodiment, the second store-and-forward parameter includes at least one of the following: a store-and-forward wait timer; a store-and-forward monitoring list; and a store-and-forward monitoring list deletion instruction.

[0032] In an exemplary embodiment, the MME sends a second store-and-forward parameter to the user equipment (UE), including: the MME adjusting the second store-and-forward parameter according to the UE's mobility and / or satellite link status, and sending the adjusted second store-and-forward parameter to the UE.

[0033] In one exemplary embodiment, the MME adjusts the second store-and-forward parameters based on the UE's mobility and satellite link status, including adjusting the second store-and-forward parameters when the UE's behavior and / or satellite link status differ from the initial assigned values ​​of the store-and-forward wait timer and the store-and-forward monitoring list.

[0034] In this embodiment, when a UE enters a network coverage area that supports store-and-forward (S&F) operations and attempts to access the network via NAS signaling, the MME calculates an initial S&F wait timer and S&F monitoring list based on factors such as the current network status, the UE's location, and mobility. These parameters are then sent to the UE via NAS messages (such as Attach Accept or Tracking Area Update Acknowledge). If the initial parameters differ from the initial values, the second store-and-forward parameters are updated.

[0035] In one exemplary embodiment, the MME sends a second store-and-forward parameter to the user equipment (UE), including: the MME sending the second store-and-forward parameter to the UE through a NAS procedure or a Globally Unique Temporary UE Identity (GUTI) reallocation procedure.

[0036] This embodiment provides a network parameter adjustment method. Figure 3 is another flowchart of the network parameter adjustment method according to this embodiment. As shown in Figure 3, the process includes the following steps:

[0037] In step S302, the UE receives the second store-and-forward parameters from the MME.

[0038] In one exemplary embodiment, the second store-forward parameter includes at least one of the following: a store-forward wait timer; a store-forward monitoring list; and a store-forward monitoring list deletion instruction.

[0039] Step S304: The UE adjusts its communication behavior based on the second store-and-forward parameters.

[0040] In one exemplary embodiment, the UE adjusts its communication behavior based on a second store-forward parameter, including: if the UE is denied access to the network through a NAS procedure, the store-forward wait timer received by the UE takes effect immediately; or, if the UE is accepted access to the network through a NAS procedure or receives a store-forward wait timer from the MME during a GUTI reallocation procedure, the store-forward wait timer takes effect when the UE loses its current service link.

[0041] In this embodiment of the disclosure, if the UE receives the S&F wait timer when it is rejected in the NAS procedure, it takes effect immediately; if the UE receives the S&F wait timer when it is accepted in the NAS procedure or during GUTI reallocation, it takes effect when the UE loses the current service link.

[0042] In one exemplary embodiment, when the store-and-forward wait timer is active and the UE is in an extended mobility management-deregistered state (EMM-DEREGISTERED), the UE may connect to satellite nodes of the PLMN or terrestrial network (TN) nodes other than the satellite nodes of the current Public Land Mobile Network (PLMN).

[0043] Alternatively, if the store-and-forward wait timer is active and the UE is in Extended Mobility Management-Registered (EMM-REGISTERED) state, the UE should not connect to the satellite nodes of the current PLMN or satellite nodes of other PLMNs or TN nodes.

[0044] Alternatively, if the store-and-forward wait timer is active and the UE is in the extended mobility management-registered state (EMM-REGISTERED), only the MME corresponding to the satellite nodes or TN nodes of other PLMNs will be constrained, and no wait constraints will be imposed on the UE behavior;

[0045] Alternatively, if the UE experiences an integrity verification failure, the UE decrements the downlink NAS overflow counter.

[0046] The above embodiments of this disclosure provide a network parameter adjustment method. A first store-and-forward parameter configured by a configuration management network element is received by a Mobility Management Entity (MME). Based on the first store-and-forward parameter, the MME sends a second store-and-forward parameter to a User Equipment (UE). This solves the problem in related technologies where dynamic adjustment of store-and-forward parameters is not possible, achieving the effect of dynamically adjusting store-and-forward parameters, optimizing the UE's network connection experience, and improving network reliability and system efficiency.

[0047] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solutions of the embodiments of this disclosure, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the embodiments of this disclosure.

[0048] This embodiment also provides a network parameter adjustment device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0049] In this embodiment, the network parameter adjustment device may include different modules. The naming and functional division of these modules may be chosen in different ways depending on the actual situation. No specific restrictions are imposed here, as long as the steps of the network parameter adjustment method in the above method embodiment can be implemented.

[0050] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0051] This disclosure also provides a network device. FIG4 is a structural block diagram of the network device according to an embodiment of this disclosure. As shown in FIG4, the network device 400 includes a receiver 401, a transmitter 402 and a processor 403. The network device 400 is used to execute the steps of the above-described model access method embodiment through at least one of the receiver 401, transmitter 402 and processor 403.

[0052] This disclosure also provides a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.

[0053] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0054] This disclosure also provides an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0055] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0056] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0057] In one exemplary embodiment, the computer program product described above includes a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the methods described in various embodiments of this application.

[0058] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0059] Obviously, those skilled in the art should understand that the modules or steps of the embodiments of this disclosure described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the embodiments of this disclosure are not limited to any particular combination of hardware and software.

[0060] To enable those skilled in the art to better understand the technical solutions of the embodiments of this disclosure, the following description is provided in conjunction with different embodiments.

[0061] Example 1

[0062] In this embodiment of the disclosure, in the store and forward (S&F) scenario, S&F-related parameters (i.e., the first store and forward parameters in the above embodiment, such as whether S&F mode is supported, integrity protection policy and ephemeris information) should be added when configuring the MME and eNB to enable them to support the service.

[0063] In this embodiment of the disclosure, S&F related parameter information is added during the creation of MME and / or base station instances, as shown in Table 1.

[0064] Table 1. Example of configuration parameters for ENB Information Object Class (IOC)

[0065] Wherein, "M" indicates mandatory, "CM" indicates conditionally mandatory, and "O" indicates optional. The definitions of the newly added field attributes are shown in Table 2.

[0066] Table 2 Example of newly added field attributes in eNB

[0067] SfSupportInd indicates whether the eNB supports store-and-forward operations;

[0068] ephemerisInfoSetRef represents the set of ephemeris information (DN) associated with the satellite to which the eNB is located.

[0069] In this embodiment of the disclosure, S&F related parameter information is added during the creation of an MME instance, as shown in Table 3.

[0070] Table 3. Example of MME Function IOC Configuration Parameters

[0071] The newly added field attributes of MME are defined as shown in Table 4.

[0072] Table 4. Examples of New Field Attributes in MME

[0073] SfSupportInd indicates whether the MME supports store-and-forward operations; ephemerisInfoSet represents the set of ephemeris information associated with the satellite where the eNB is located. Each ephemerisInfo in the set contains the satellite ID, ephemeris reference time, position angle, etc.; nasCounterMgmtMode indicates the NAS counter management mode adopted by the MME, including three options: default, SeparateCountersPerSatellite, and OverflowHandling.

[0074] Specifically, `default` requires the MME to have an updated UE context when the UE re-accesses, ensuring successful access. `SeparateCountersPerSatellite` requires the MME to maintain an independent NAS counter for each satellite to support NAS count management in multi-satellite environments. `OverflowHandling` specifies that when the MME experiences an integrity check failure, it will attempt to increment the UL NASOC (uplink NAS overflow counter) to match the correct NAS COUNT, thereby restoring communication; when the UE experiences an integrity check failure, it will attempt to decrement the DL NASOC (downlink NAS overflow counter) to match the correct NAS COUNT, thereby restoring communication.

[0075] Figure 5 is a flowchart of configuring the MME and eNB to add S&F related parameters according to an embodiment of this disclosure. As shown in Figure 5, it includes the following steps:

[0076] S1. The Network Function Management Service Consumer (NFMS_C) sends a request to the Network Function Management Service Provider (NFMS_P) to create a Managed Object Instance (MOI). In addition to the original parameters such as the MOI ID, the MOI also needs to carry S&F related information (i.e., the first store-and-forward parameters mentioned above), including whether store-and-forward operation is supported, associated ephemeris information, and the selected integrity protection policy.

[0077] In this embodiment of the disclosure, NFMS_P is the configuration management network element in the above embodiments.

[0078] S2. If the NF instance includes a virtualization component, then NFMS_P retrieves the virtualization-related parameter information from the MOI creation request.

[0079] S3. If it is necessary to perform Virtual Network Function Package (VNFP) upload or modification operations, NFMS_P interacts with the Network Function Virtualization Orchestrator (NFVO) to execute the VNFP lifecycle management process:

[0080] S3a and NFMS_P send an UploadVnfPackage request to NFVO, which includes the VNFP information identifier (VNFPInfoid) and the VNFP or VNFP path;

[0081] S3b and NFVO return an UploadVnfPackage response to NFMS_P.

[0082] S4. Perform the Virtual Network Function (VNF) lifecycle management process:

[0083] S4a and NFMS_P send an UpdateNs (update network service) request to NFVO, which includes the network service instance identifier (nsInstanceId), sets the update type to instantiated VNF, and provides the necessary related data;

[0084] S4b and NFVO return an UpdateNs response to NFMS_P.

[0085] S5. NFMS_P creates an Evolved Base Station Function (ENBFunction) MOI and / or a Mobility Management Entity Function (MMEFunction) MOI. If the ENBFunction MOI and / or MMEFunction MOI include a virtualization component, NFMS_P may send a creation request to other NFMS_Ps responsible for VNF creation.

[0086] When configuring the ENBFunction MOI created in step five of S6 and NFMS_P, in addition to configuring the original parameters, you also need to add SfSupportInd (store-and-forward support indicator) and ephemerisInfoSetRef (ephemeris information set reference). Similarly, when configuring the MMEFunction MOI, you should also include SfSupportInd, ephemerisInfoSet, and nasCounterMgmtMode (non-access stratum counter management mode).

[0087] S7, NFMS_P sends a MOI creation response to NFMS_C, carrying MOI id information.

[0088] Example 2

[0089] In this embodiment of the disclosure, in addition to providing S&F-related parameters to the UE during the NAS procedure, the MME also dynamically updates the S&F-related parameters (i.e., the second store-and-forward parameters in the above embodiment) based on UE mobility, ephemeris information and changes in satellite coverage.

[0090] In this embodiment of the disclosure, it is known from the previous configuration whether the on-board base station and MME support S&F operation. When both the on-board base station and MME are running in S&F mode and the UE supports S&F operation, the MME may carry the S&F Wait Timer and / or S&F Monitoring List and the S&F Monitoring List deletion instruction through the accept or reject signaling when performing the NAS procedure.

[0091] In one embodiment, the S&F Wait Timer is used to control the communication connection interval between the UE and the satellite base station, ensuring that the UE re-initiates NAS requests or receives data from the mobile terminal at the appropriate time. The duration of this timer is dynamically determined by the MME based on multiple factors, such as the availability of the feeder link, the availability of the service link, the UE's energy-saving requirements, communication mode, UE location, and mobility.

[0092] In one embodiment, the S&F Monitoring List is a list of satellites that support S&F operations and should contain the UE context, which the UE can use to select satellites for subsequent communication services.

[0093] When a UE establishes a signaling association with an MME, the MME can initiate a GUTI Reallocation Procedure to reallocate parameters such as the GUTI (General Packet Radio Service, GPRS) user temporary identifier and / or Tracking Area Identifier (TAI) list and / or UE Radio Capability ID assigned by the PLMN (Public Land Mobile Network) and / or S&F Wait Timer and / or S&F Monitoring List, as well as delete S&F Monitoring List indications.

[0094] Figure 6 is a flowchart of the MME dynamically updating the second store-and-forward parameters according to an embodiment of this disclosure. As shown in Figure 6, it includes the following steps:

[0095] There is a signaling association between S0, MME and UE, and MME detects that the current UE behavior and / or satellite link status has changed compared to when the S&F wait timer and S&F monitoring list were previously allocated in the NAS procedure.

[0096] S1. MME initiates GUTI reassignment command: When the MME needs to reassign the GUTI and / or TAI list and other parameters, it must send a GUTI reassignment command to the UE. This command may contain the following parameters: GUTI, TAI list, UE radio capability identifier assigned by PLMN, PLMN-assigned UE radio capability identifier deletion instruction, S&F wait timer and S&F monitoring list, and deletion instruction for S&F Monitoring List.

[0097] S2. UE returns a GUTI reallocation completion message: After receiving the GUTI reallocation command, the UE returns a GUTI reallocation completion message to the MME, indicating that the process has been successfully completed.

[0098] Example 3

[0099] In this embodiment of the disclosure, the UE and the network adjust their behavior based on the received and configured S&F related parameters (i.e., the second store-and-forward parameters in the above embodiments).

[0100] In this embodiment of the disclosure, the UE will receive S&F related parameters (i.e., the second store-and-forward parameters in the above embodiment) during the NAS procedure and the GUTI Reallocation Procedure, wherein:

[0101] In one embodiment, if the UE receives an S&F wait timer when it is rejected in the NAS procedure, it takes effect immediately;

[0102] In one embodiment, if the UE is received in the NAS procedure or receives the S&F wait timer in the GUTI Reallocation Procedure, the S&F wait timer will take effect after the UE loses the current service link.

[0103] In this embodiment of the disclosure, when the S&F wait timer is running:

[0104] In one embodiment, if the UE is in EMM-DEREGISTERED state, the UE should not attempt to connect to the satellite node of the current PLMN, but may attempt to connect to the satellite node of another PLMN or TN node.

[0105] In one embodiment, if the UE is in EMM-REGISTERED state, the UE should not attempt to connect to the satellite nodes of the current PLMN or other PLMN satellite nodes or TN nodes, or impose constraints on the MMEs corresponding to other PLMN satellite nodes or TN nodes without imposing waiting constraints on the UE's behavior. In one embodiment, if the nasCounterMgmtMode configured by the aforementioned MME is default, then the MMEs connected to other PLMN nodes or TN nodes are required to obtain the latest UE context. In one embodiment, if the nasCounterMgmtMode configured by the aforementioned MME is SeparateCountersPerSatellite, then the MMEs connected to other PLMN nodes or TN nodes are required to obtain a UE context that does not necessarily contain the latest NAS COUNT. In one embodiment, if the nasCounterMgmtMode configured by the aforementioned MME is OverflowHandling, then the MMEs connected to other PLMN nodes or TN nodes are required to obtain a UE context that does not necessarily contain the latest NAS COUNT, but the MME and UE must attempt to increment the uplink NAS overflow counter (UL) upon receiving the message. The MME includes a downlink NAS overflow counter (DL NASOC) and a decrementing downlink NAS overflow counter (DL NASOC). The MME carries nasCounterMgmtMode in the ATTACH and Tracking Area Update (TAU) accept. In this embodiment, ATTACH is used as an example.

[0106] Figure 7 is a flowchart of the UE adjusting its communication behavior according to the second store-and-forward parameters according to an embodiment of this disclosure. As shown in Figure 7, it includes the following steps:

[0107] S1. The UE sends an access request (Attach Request).

[0108] S2, eNodeB selects MME: eNodeB selects MME based on the old Globally Unique MME Identity (GUMMEI) and Radio Access Technology (RAT) type. If the MME is in S&F mode, it may reject the access request and carry the S&F waiting timer, S&F monitoring list, and deletion of S&F monitoring list indication in the access rejection (Attach Reject) message. When accessing the satellite, the MME can verify the legality of the UE's location.

[0109] S3. New and Old MME Authentication: The new MME requests the IMSI and MME context from the old MME or the Serving GPRS Support Node (SGSN) via the old GUTI. If the previous node authentication fails, an error is returned. This includes the transmission of identification requests and identification responses between the new MME and the old MME / SGSN.

[0110] S4. Identity Request: If neither the old nor the new MME has a UE context, the new MME will forcibly obtain the International Mobile Subscriber Identity (IMSI) through an Identity Request.

[0111] S5a, Security Activation (Transmission of Authentication / Security): If there is no valid security context or the integrity verification fails, the MME performs authentication and NAS security activation. When accessing the satellite, the MME can request the UE to report coarse-grained location information and verify it through the Enhanced Serving Mobile Location Center (E-SMLC).

[0112] S5b, Device Identity Verification (Transmission of Identity Request / Response and MME Identity Check): The MME obtains the International Mobile Equipment Identity (IMEI) and can optionally verify it with the Equipment Identity Register (EIR). Authentication can be skipped for emergency / RLOS access.

[0113] S6. Encryption Options Transmission (including Ciphered Options Request and Ciphered Options Response): If the UE sets the encryption flag, the MME obtains the encryption Protocol Configuration Options (PCO) or Access Point Name (APN) parameters.

[0114] S7. Clean up old bearers: The new MME deletes residual active bearer contexts.

[0115] This step involves the deletion session request and deletion session response between the new MME and the Serving GW. Since cleaning up the old bearer can be implemented using conventional techniques in the art, it will not be described in detail here.

[0116] S8, HSS Location Update: The MME sends an Update Location Request to the Home Subscriber Server (HSS), carrying the initial access flag. If the MME is in S&F mode, it may send a temporary location update request carrying a timestamp.

[0117] S9. HSS Cleans Up Old Nodes: The HSS sends a Cancel Location message to the old MME / SGSN and receives a Cancel Location Ack message to clear the old context.

[0118] S10. Deletion of old node bearers: The old MME / SGSN is deleted from its associated Serving Gateway (SGW) or Packet Data Network Gateway (PGW) bearer.

[0119] This step involves the transmission of delete session requests and delete session responses. Since the deletion of old nodes can be implemented using conventional techniques in this field, it will not be described in detail here.

[0120] S11, HSS returns subscription data (Update Location Ack): HSS returns subscription data (including enhanced coverage restrictions, service interval time, etc.), MME verifies the legality of the Tracking Area (TA), if the UE supports S&F operation and MME is in S&F mode, MME processes the S&F related procedures.

[0121] S12. Create Session Request: The MME selects the SGW / PGW to initiate a Create Session Request. When optimizing the control plane for Cellular Internet of Things (CIoT), it indicates that only the control plane is connected. When using satellite access, it considers Machine Type Enhanced Delay Tolerance (MT-EDT) support.

[0122] S13, SGW forwards session creation request: SGW forwards the request to PGW. If it is in control plane optimization mode, it marks the control plane call detail record (CDR) only.

[0123] S14. Policy and Charging Control (PCC) Rule Interaction: If dynamic PCC is deployed, the PGW interacts with the Policy Control and Charging Rules Function (PCRF) to obtain the default policy, and sets the Allocation and Retention Priority (ARP) values ​​for the Emergency APN. This step involves the transmission of the PCEF-initiated IP-CAN Session Establishment / Modification.

[0124] S15, PGW Creates Bearer: PGW assigns an IP address and returns a Create Session Response, which includes a latency-tolerant connection indication.

[0125] S16, SGW confirms bearer: SGW returns a response (session creation response) to MME, which includes the APN rate control status.

[0126] S17. Send Attach Accept: The MME sends an Attach Accept message, including GUTI, TA list, Quality of Service (QoS) parameters, nasCounterMgmtMode, etc. If the MME is in S&F mode, it may carry an S&F wait timer and / or an S&F monitoring list and / or an estimated uplink transmission time, and an indication to delete the S&F monitoring list. For satellite access, it may include discontinuous coverage parameters. The sent nasCounterMgmtMode may be default, SeparateCountersPerSatellite, or OverflowHandling. If it is default, the UE's operation after receiving the downlink message is consistent with the existing procedure; if it is SeparateCountersPerSatellite, the NAS COUNT carried in subsequent messages sent by the UE will be counted separately for different satellite nodes; if it is OverflowHandling, when the UE receives a subsequent downlink message, if the integrity check fails, it will attempt to decrement the DL NASOC.

[0127] In this step, the new MME sends an Initial Context Setup Request or Downlink NAS transport with Attach Accept to the eNodeB.

[0128] S18, eNodeB forwarding configuration: eNodeB sends Attach Accept via RRC reconfiguration or direct transmission message, and UE stores enhanced coverage limit and service interval time parameters.

[0129] In this step, the eNodeB sends an RRC Connection Reconfiguration or RRC Direct Transfer to the UE.

[0130] S19, RRC Reconfiguration Complete: The UE sends an RRC Connection Reconfiguration Complete message to confirm the bearer establishment.

[0131] S20. Initial Context Response: The eNodeB returns an Initial Context Response, which contains S1-U tunnel information. If a Correlation ID exists, a direct connection path to the local IP address is established.

[0132] S21. UE confirms access completion: The UE sends Attach Complete via Direct Transfer. If control plane CIoT optimization is used, the bearer ID is omitted.

[0133] S22, MME Receive Complete: The eNodeB forwards "Attach Complete" to the MME, and the UE begins uplink data transmission.

[0134] S23. Modify Bearer Request: The MME sends a Modify Bearer Request to the SGW to update the path. This step is skipped when the control plane CIoT is optimized and there is no Service Capability Exposure Function (SCEF).

[0135] S23a, PGW Path Switching: The SGW notifies the PGW to switch the downlink path to 3GPP access, carrying the existence of the reported area information.

[0136] S23b, PGW confirms modification: PGW returns a Modify Bearer Response confirming the path update.

[0137] S24, SGW confirms modification: SGW returns a response (modification bearer response) to MME, triggering a Dual Data Network (DDN) failure monitoring event.

[0138] S25, HSS Notification Update: If it is not a handover request and the PDN GW has changed, the MME notifies the HSS to update the PDN GW information. Emergency / RLOS access skips this step.

[0139] S26. HSS Storage Information: The HSS stores the APN-PGW mapping relationship and returns a Notify Response to complete the process.

[0140] The above description is merely a preferred embodiment of this disclosure and is not intended to limit the scope of this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the protection scope of this disclosure.

Claims

1. A method for adjusting network parameters, comprising: The Mobility Management Entity (MME) receives the first store-and-forward parameters configured by the Configuration Management Network Element. The MME sends a second store-forward parameter to the UE based on the first store-forward parameter.

2. The method according to claim 1, wherein, The first store-and-forward parameter includes at least one of the following: Storage forwarding support indication; ephemeris information set; non-access stratum NAS counter management mode.

3. The method according to claim 2, wherein, The NAS counter management mode includes at least one of the following: Default mode: In the event of the UE re-accessing the network, the MME obtains the updated UE context; In satellite-independent counting mode: the MME maintains an independent NAS counter for each satellite; Overflow handling mode: If the integrity check of the MME fails, the MME increments the uplink NAS overflow counter.

4. The method according to claim 1, wherein, The second store-and-forward parameter includes at least one of the following: Store-and-forward wait timer; store-and-forward monitoring list; store-and-forward monitoring list deletion instruction.

5. The method according to claim 1, wherein, The MME sends a second store-and-forward parameter to the user equipment (UE), including: The MME adjusts the second store-and-forward parameters based on the UE's mobility and / or satellite link status, and sends the adjusted second store-and-forward parameters to the UE.

6. The method according to claim 5, wherein, The MME adjusts the second store-and-forward parameters based on the UE's mobility and satellite link status, including: If the behavior of the UE and / or the satellite link status differs from the initial allocation values ​​of the store-and-forward wait timer and the store-and-forward monitoring list, the MME adjusts the second store-and-forward parameter.

7. The method according to claim 1, wherein, The MME sends a second store-and-forward parameter to the user equipment (UE), including: The MME sends the second store-and-forward parameter to the UE through a NAS procedure or a globally unique temporary UE identifier (GUTI) reallocation procedure.

8. A method for adjusting network parameters, comprising: The UE receives the second store-and-forward parameters from the MME; The UE adjusts its communication behavior based on the second store-and-forward parameters.

9. The method according to claim 8, wherein, The second store-and-forward parameter includes at least one of the following: Store-and-forward wait timer; store-and-forward monitoring list; store-and-forward monitoring list deletion instruction.

10. The method according to claim 9, wherein, The UE adjusts its communication behavior based on the second store-and-forward parameters, including: If the UE is denied access to the network via the NAS procedure, the store-forward wait timer received by the UE shall take effect immediately. Alternatively, if the UE is accepted when accessing the network via the NAS procedure or receives the store-forward wait timer from the MME during the GUTI reallocation procedure, the store-forward wait timer takes effect when the UE loses its current service link.

11. The method according to claim 10, wherein, When the store-forward wait timer is active and the UE is in Extended Mobility Management - Unregistered (EMM-DEREGISTERED) state, the UE connects to satellite nodes of the PLMN or terrestrial network TN nodes other than the satellite nodes of the current Public Land Mobile Network (PLMN). Alternatively, if the store-forward wait timer is active and the UE is in Extended Mobility Management-Registered (EMM-REGISTERED) state, the UE should not connect to the satellite nodes of the current PLMN or satellite nodes of other PLMNs or TN nodes. Alternatively, if the store-and-forward wait timer is active and the UE is in the Extended Mobility Management-Registered (EMM-REGISTERED) state, constraints are imposed on the MME corresponding to satellite nodes or TN nodes of other PLMNs, but no waiting constraints are imposed on the UE behavior; Alternatively, if the UE experiences an integrity verification failure, the UE decrements the downlink NAS overflow counter.

12. A network device comprising a receiver, a transmitter, and a processor, the network device being configured to perform the steps of the method of any one of claims 1 to 7, or to implement the steps of the method of any one of claims 8 to 11, by means of at least one of the receiver, the transmitter, and the processor.

13. A computer-readable storage medium storing a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 7, or the steps of the method described in any one of claims 8 to 11.

14. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method of any one of claims 1 to 7, or to implement the steps of the method of any one of claims 8 to 11.

15. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 7, or implements the steps of the method according to any one of claims 8 to 11.

Images