Subscription information configuration

Abstract

Methods and systems are disclosed for subscription information configuration (200). One method includes transmitting a subscription information configuration message from an external server to an authentication device, wherein the subscription information configuration message includes assistance information that configures parameters of a base unit for a mobile unit; authenticating the subscription information configuration message at the authentication device and, in response to a successful authentication, sending the subscription information configuration message to the subscription server; and storing the subscription information configuration message at the subscription server.

Description

Technical Field

[0001] The topics disclosed in this article generally relate to wireless communication, and more specifically to subscription information configuration. Background Technology

[0002] The following abbreviations are defined herein, and at least some of them are referenced in the following descriptions: 3rd Generation Partnership Project (“3GPP”), Affirmative Acknowledgment (“ACK” or “Ack”), Access Layer (“AS”), Downlink (“DL”), Evolved Node B (“eNB”), Equipment Identifier Register (“EIR”), Frequency Division Multiple Access (“FDMA”), Home Subscriber Server (“HSS”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Mobility Management Entity (“MME”), Mobile Equipment (“ME”), Non-Access Layer (“NAS”), Next Generation Node B (“gNB”), Orthogonal Frequency Division Multiplexing (“OFDM”), PDN Gateway (“PGW”). Radio Resource Control (“RRC”), Access Network (“AN”), Radio Access Network (“RAN”), Radio Link Failure (“RLF”), Service Capability Exposure Function (“SCEF”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Serving Gateway (“SGW”), User Entity / Equipment (Mobile Terminal) (“UE”), Uplink (“UL”), Global Interoperability for Microwave Access (“WiMAX”), Core Access and Mobility Management Function (“AMF”), Network Exposure Function (“NEF”), Session Management Function (“SMF”), Unified Data Management (“UDM”), User Plane Function (“UPF”), and Application Function (“AF”).

[0003] There is a growing interest in utilizing cellular networks to cover aircraft such as drones. Use cases for commercial drones are growing rapidly and include package delivery, search and rescue, monitoring of critical infrastructure, wildlife conservation, aerial cameras, and surveillance. All of these use cases are likely to grow rapidly, with more emerging in the coming years. Many of these emerging use cases can benefit from connecting drones as UEs to cellular networks. LTE is well-positioned to serve aircraft such as drones. In fact, a growing number of field trials have already involved using LTE networks to provide connectivity to drones. The rapid and significant growth of the drone industry is expected to bring new and promising business opportunities for LTE operators. To meet the growing market demand, 3GPP TSG RAN#75 has approved a new research project (SI) entitled “Study on Enhanced LTE Support for Aircraft.” The following enhancements are proposed:

[0004] Interference mitigation solutions for improving system-level performance in UL and DL;

[0005] Solution for detecting whether the UL signal from an over-the-air UE increases interference from multiple neighboring cells and whether the over-the-air UE causes interference from multiple cells;

[0006] The identifier of an airborne UE that lacks proper authentication to connect to a cellular network while airborne;

[0007] Handover: Identify whether enhancements in cell selection and handover efficiency, as well as robustness of handover signaling, are achievable;

[0008] Location: If time permits, this is the second priority, and existing location technologies are used to assess achievable accuracy and identify potential enhancements.

[0009] The main discussion will now focus on solutions related to drone UEs in RAN 2. The following document has been submitted to the RAN 2 meeting.

[0010] 1. R2-1704997, Enhanced Mobility for Drones, Huawei, HiSilicon

[0011] The document considers and lists many possible enhancements, as follows. However, no further details are revealed.

[0012] 1. Mobility control parameter optimization (TTT, CIO, etc.)

[0013] 2. Enhanced measurement reports

[0014] 3. RLF and Re-establishment

[0015] 4. Coordination and Scheduling

[0016] 5. Interference Control

[0017] 6. UE Mobility Status Assessment

[0018] 7. Introduce a speed-based switching strategy

[0019] 8. Utilize beamforming technology to improve downlink signal quality

[0020] 9. Enhanced proximity indication process

[0021] ·10. Pre-switching configuration based on the UAV's fixed flight path information

[0022] 2. R2-1705999, Recommendation for potential LTE enhancements for aircraft, KDDI

[0023] The proposal suggests the following solutions to enhance the handover process: changing handover-related parameters (trigger time, event threshold, etc.); introducing a handover disable timer mechanism; and activating joint transmission.

[0024] However, there is no discussion regarding unmanned aerial vehicle (UAV) UEs in SA2. The solutions proposed in this disclosure mainly involve network capability exposure characteristics (TS 23.682) and attachment procedures (TS 23.401).

[0025] References

[0026] [1]RP-170779, “New SID for Enhanced Support of Aircraft”, Ericsson NTT DOCOMO INC.

[0027] [2]R2-1705999, “Proposals for Potential LTE Enhancements for Aircraft”, KDDI

[0028] [3]R2-1704997, "Enhancing the Mobility of Drones", Huawei, HiSilicon

[0029] From a radio perspective, the above references are identified by the RAN group. However, other issues remain to be addressed. Summary of the Invention

[0030] Methods and systems for configuring subscription information are disclosed. A method for providing subscription information to the core network is disclosed. An enhanced attachment process is disclosed.

[0031] In one embodiment, a method includes: transmitting a subscription information configuration message from an external server to an authentication device, wherein the subscription information configuration message includes auxiliary information for configuring parameters of a base station unit for a mobile unit; authenticating the subscription information configuration message at the authentication device, and in response to successful authentication, sending the subscription information configuration message to a subscription server; and storing the subscription information configuration message at the subscription server.

[0032] In one embodiment, the auxiliary information includes at least one of the expected altitude range, expected speed range, and path information. In another embodiment, in response to successful authentication, the subscription information configuration message is converted into a format understandable by the base station unit, and the converted subscription information configuration message is sent to the subscription server.

[0033] In one embodiment, the subscription information configuration message further includes mobility restriction parameters. The mobility restriction parameters include an altitude limit, which defines the maximum altitude of the mobile unit. In response to the mobile unit exceeding the maximum altitude, the base station unit sends an alert message to an external server. The mobility restriction parameters also include a speed limit, which defines the maximum speed of the mobile unit. In response to the mobile unit exceeding the maximum speed, the base station unit sends an alert message to an external server.

[0034] In one embodiment, storing the subscription information configuration message includes modifying a previous subscription information configuration message into a new subscription information configuration message. The method may further include sending the subscription information configuration message from the subscription server to a control node in response to successful authentication of the mobile unit by the subscription server. In response to the mobile unit attaching to the control node, the subscription information configuration message is sent from the control node to a base station unit. The subscription information configuration message is also sent from the base station unit to the mobile unit. Preferably, the transmission of the subscription information configuration message is performed in response to a request from the subscription server.

[0035] A system includes: an authentication device that receives and authenticates a subscription information configuration message from an external server, wherein the subscription information configuration message includes auxiliary information for configuring parameters of a base station unit for a mobile unit; and a subscription server that stores the subscription information configuration message sent from the authentication device, wherein the subscription information configuration message is sent from the authentication device in response to successful authentication.

[0036] A method includes: initiating an attachment procedure for a mobile unit; and, in response to authentication of the attachment, transmitting a subscription information configuration message to a base station unit, wherein the subscription information configuration message includes auxiliary information and mobility restriction parameters for configuring parameters of the base station unit for the mobile unit. Attached Figure Description

[0037] A more detailed description of the embodiments briefly described above will be presented by referring to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are therefore not intended to limit the scope; the embodiments will be described and explained with additional features and details using the drawings, wherein:

[0038] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system;

[0039] Figure 2 This is a schematic block diagram illustrating one embodiment of subscription information configuration;

[0040] Figure 3 This is a schematic flowchart illustrating one embodiment of a method for configuring subscription information;

[0041] Figure 4 This is a schematic flowchart illustrating another embodiment of a method for configuring subscription information;

[0042] Figure 5 This is a schematic diagram illustrating the transformation of path information;

[0043] Figure 6-1 This is a schematic diagram illustrating one embodiment of the attachment process;

[0044] Figure 6-2 This is a schematic diagram illustrating a detailed embodiment of step 620 of the attachment process; and

[0045] Figure 7 This is a schematic flowchart illustrating one embodiment of a method for mobility restriction. Detailed Implementation

[0046] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which may generally be referred to herein as "circuit," "module," or "system." Furthermore, embodiments can take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as "code." The storage device can be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device only employs signals for accessing the code.

[0047] Certain functional units described in this specification may be labeled modules to more specifically emphasize their implementation independence. For example, modules may be implemented as hardware circuits comprising custom-designed very large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0048] Modules can also be implemented in code and / or software to be executed by various types of processors. The identified code module may, for example, comprise one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executable files of the identified module do not need to be physically located together, but may include unrelated instructions stored in different locations, which, when logically connected together, constitute the module and achieve the module's stated purpose.

[0049] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and span multiple memory devices. Similarly, in this document, operational data can be identified and visualized within a module, and can be represented in any suitable form and organized within any suitable type of data structure. This operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. Where the module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0050] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination thereof.

[0051] A non-exhaustive list of more specific examples of storage devices will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable compact optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing programs for use by or in connection with an instruction execution system, apparatus, or device.

[0052] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the last case, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider).

[0053] References to “an embodiment,” “embodiment,” or similar language in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases “in an embodiment,” “in an embodiment,” and similar language appearing throughout this specification may, but not necessarily all, refer to the same embodiment, but rather mean “one or more, but not all, embodiments.” Unless expressly stated otherwise, the terms “comprising,” “including,” “having,” and variations thereof mean “including, but not limited to,”. Unless expressly stated otherwise, the list of items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms “a,” “an,” and “the” also mean “one or more.”

[0054] Furthermore, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details, or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring some aspects of the embodiments.

[0055] The aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / operations specified in the schematic flowcharts and / or schematic block diagrams for blocks, or blocks.

[0056] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art that implements the function / operation specified in blocks or blocks of a schematic flowchart and / or schematic block diagram.

[0057] The code may also be loaded onto a computer, other programmable data processing apparatus or other device, causing a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in blocks or blocks of flowcharts and / or block diagrams.

[0058] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0059] It should also be noted that in some alternative implementations, the functions annotated in the blocks may occur in a different order than those annotated in the figures. For example, two blocks shown consecutively may be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods are conceivable that are functionally, logically, or effectively equivalent to one or more blocks or portions thereof in the illustrated figures.

[0060] While various arrow and line types may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the respective embodiments. In fact, some arrows or other connectors may be used solely to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It will also be noted that each block of the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a system based on dedicated hardware, or a combination of dedicated hardware and code, performing a specific function or operation.

[0061] The description of the elements in each figure can be referenced to the elements in the preceding figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0062] Figure 1 An embodiment of a wireless communication system 100 is depicted. In one embodiment, the wireless communication system 100 includes a mobile unit 105, a base station unit 110, a core network 130, and an over-the-air server 120. Although Figure 1 A specific number of mobile units 105 and base station units 110 are depicted, but those skilled in the art will recognize that the wireless communication system 100 may include any number of mobile units 105 and base station units 110. Similarly, although in Figure 1The diagram depicts only one core network 130 and only one over-the-air server 120, but those skilled in the art will recognize that the wireless communication system 100 may include more core networks 130 and more over-the-air servers 120.

[0063] In one embodiment, mobile unit 105 may include an aircraft such as a drone. Use cases for drones include package delivery, search and rescue, monitoring of critical infrastructure, wildlife conservation, aerial cameras, and surveillance. Mobile unit 105 may be referred to as a remote unit, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, UE, subscriber station, user terminal, device, or by other terms used in the art. Mobile unit 105 may wirelessly communicate with one or more base station units 110.

[0064] Base station unit 110 can be distributed across a geographical area. In some embodiments, base station unit 110 may also be referred to as an access point, access terminal, base station, base station, node B, eNB, gNB, home node B, relay node, device, or any other term used in the art. Base station unit 110 is connected to core network 130, which may be coupled to other networks, such as the Internet and public switched telephone networks, as well as other networks, such as over-the-air servers.

[0065] In one implementation, the wireless communication system 100 conforms to the LTE protocol of 3GPP. However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols. This disclosure is not intended to limit itself to any particular wireless communication system architecture or protocol implementation.

[0066] Base station unit 110 can serve multiple mobile units 105 within a service area (e.g., a cell or cell sector) via a wireless communication link. Base station unit 110 can communicate directly with one or more remote units 105 via communication signals. Typically, base station unit 110 transmits downlink (“DL”) communication signals in the time domain, frequency domain, and / or spatial domain to serve the remote units 105.

[0067] In one embodiment, core network 130 is an evolved packet core (“EPC”). In another embodiment, core network 130 may be a 5G core network. Core network 130 may be coupled to an external server such as over-the-air server 120. This disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0068] The core network 130 includes several network elements. As depicted, the core network 130 includes SCEF 135, HSS 140, and MME 145. Although in Figure 1A specific number of MMEs 145 are depicted, but those skilled in the art will recognize that any number of MMEs 145 can be included in the core network 130. Although SCEF 135, HSS 140, and MME 145 are described in the embodiments, those skilled in the art will recognize that in a 5G network, the Network Exposure Function (“NEF”) is equivalent to SCEF, Unified Data Management (“UDM”) is equivalent to HSS, and Core Access and Mobility Management Function (“AMF”) is equivalent to MME. Incidentally, in a 5G network, Session Management Function (“SMF”) is equivalent to SGW, User Plane Function (“UPF”) is equivalent to PGW, and Application Function is equivalent to External Server.

[0069] MME 145 is a control plane network element that handles signaling related to the mobility and security of mobile unit 105. The MME may be referred to as a control node. MME 145 is the termination point for the NAS connection from remote unit 105 to core network 130. HSS 140 is a server for storing subscription information. SCEF 135 is a device for connecting core network 130 to external servers such as air server 120.

[0070] Airborne server 120 is a server that stores information related to mobile unit 105 (and particularly related to controlling the aircraft). Airborne server 120 maintains references Figure 2 Detailed explanation of subscription configuration information. SCEF 135 certified over-the-air server 120.

[0071] Figure 2 The figure illustrates a subscription information configuration 200 transmitted from an over-the-air server 120 to a core network 130 according to an embodiment of the present disclosure. A preferred embodiment of the subscription information configuration 200 includes an AS identifier 210, a UE identifier 220, mobility restrictions 230, and air assistance information 240. Timer information 250 may optionally be included in the subscription information configuration 200.

[0072] AS identifier 210 is the identifier of air server 120. Although Figure 1 Only one air server 120 is shown, but those skilled in the art will recognize that the wireless communication system 100 may include any number of air servers 120. Each air server 120 has its own unique AS identifier 210.

[0073] The UE identifier 220 is the identifier of the mobile unit 105. An over-the-air server 120 can store subscription information configuration 200 for any number of mobile units 105. Each mobile unit 105 has its unique UE identifier 220.

[0074] Mobility restriction 230 serves as a limitation on the behavior of mobile unit 105. For example, an aircraft, as a preferred embodiment of mobile unit 105, can fly at altitudes much higher than the base station unit is allowed to provide connectivity. Therefore, limiting the altitude of the aircraft is necessary.

[0075] A preferred embodiment of mobility restriction 230 includes altitude restriction 231, speed restriction 232, etc. Altitude restriction 231 defines the maximum altitude of mobile unit 105. If mobile unit 105 flies beyond the altitude restriction, mobile unit 105 may be unable to communicate with base station unit 110, or will not be allowed to communicate with base station unit 110. Speed ​​restriction 232 defines the maximum speed of mobile unit 105. If mobile unit 105 flies beyond the speed restriction, mobile unit 105 may be unable to communicate with base station unit 110, or will not be allowed to communicate with base station unit 110.

[0076] Air assistance information 240 serves as information that can help base station units configure their parameters to provide appropriate services. Preferred embodiments of air assistance information 240 include expected altitude range 241, expected speed range 242, path information 243, etc. Air assistance information 240 can be set by an airborne server 120. Alternatively, air assistance information 240 can be predetermined by the core network 130.

[0077] The expected altitude range 241 is the preferred altitude range for the flight of the mobile unit 105. The expected speed range 242 is the preferred speed range for the flight of the mobile unit 105. The path information 243 refers to the flight path of the mobile unit 105.

[0078] Timer information 250 may optionally be included in subscription information configuration 200. Timer information 250 may define the expiration time of subscription information configuration 200. For example, timer information 250 may be a duration such as a week, a day, or several hours (e.g., 5 hours). Timer information 250 indicates that subscription information configuration 200 becomes invalid after the duration (e.g., 5 hours).

[0079] Figure 3 A method (300) for configuring subscription information according to embodiments of the present disclosure is described. In some embodiments, the method (300) is performed by means such as an over-the-air server 120, SCEF 135, and HSS 140. In some embodiments, the method (300) may be performed by a processor, microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc., that executes program code.

[0080] Method (300) begins and transmits (310) a subscription information configuration message from air server 120 to SCEF 135. The transmission of the subscription information configuration message may be initiated by air server 120. Alternatively, the transmission of the subscription information configuration message may be in response to a request from HSS 140.

[0081] like Figure 2 As depicted, the subscription information configuration includes AS identifier 210, UE identifier 220, mobility restriction 230, and air assistance information 240. Those skilled in the art will recognize that the subscription information configuration message may not include all of these. For example, mobility restriction 230 may be omitted. In other words, a subscription information configuration message including only air assistance information 240 may be transmitted to SCEF 135.

[0082] The method also includes authenticating (320) the subscription information configuration message at SCEF 135. SCEF 135 determines whether AS identifier 210 and UE identifier 220 are valid. If this determination is successful, SCEF 135 sends (330) the subscription information configuration message to HSS 140. If this determination is unsuccessful, the method proceeds to step 370, which will be discussed later.

[0083] Method (300) also includes receiving (340) a subscription information configuration message at HSS 140. If the reception is successful, HSS 140 stores (350) the subscription information configuration message. If the reception is unsuccessful, the method proceeds to step 360, which will be discussed later.

[0084] In step 350, HSS 140 stores the subscription information configuration message. If an existing subscription information configuration message for a specific mobile unit 105 is already stored at HSS 140, the HSS can replace the existing subscription information configuration message with the most recently received subscription information configuration message.

[0085] As described above, the subscription information configuration message may include only air assistance information 240, excluding mobility restriction 230. This can be achieved by sending a subscription information configuration message that includes both air assistance information 240 and mobility restriction 230, where the value of mobility restriction 230 is set to NULL. A NULL value for a field indicates that the value of that field has not been transmitted. In some embodiments, the NULL value is set to both air assistance information 240 and mobility restriction 230. It is used to delete existing subscription information configuration messages for a specific mobile unit stored at HSS 140.

[0086] The method also includes sending a (360) response from HSS 140 to SCEF 135. If reception of the subscription information configuration message fails at step 340, a response including a reason value indicating the failure is sent to SCEF 135. If the subscription information configuration message is successfully received at step 340, a response including a reason value indicating successful reception is sent to SCEF 135 after the storage of the subscription information configuration message or the replacement of an existing subscription information configuration message is performed at step 350.

[0087] The method also includes transmitting a (370) response from SCEF 135 to air server 120. If authentication fails in step 320, a response containing a reason value indicating the authentication failure is sent to air server 120. If a response containing a reason value indicating failure or success of reception is received from HSS 140, the same response is sent from SCEF 135 to air server 120.

[0088] Figure 4 Another method (400) for configuring subscription information according to embodiments of the present disclosure is described. The main difference between method (400) and method (300) lies in steps 430, 435, and 450. Other steps 410, 420, 440, 460, and 470 are the same as steps 310, 320, 340, 360, and 370.

[0089] exist Figure 3 In step 330, SCEF 135 sends the subscription information configuration message to HSS 140. On the other hand, according to... Figure 4 In the depicted embodiment, SCEF 135 converts subscription information configuration 200 430 into a format that is easily understood by base station unit 110.

[0090] In some embodiments, only a portion of the subscription information configuration 200 is converted.

[0091] For example, path information 243 can be converted into a list of base station units or a list of cells. This list preferably includes the access order. Path information transmitted from the over-the-air server 120 may include a specific route that the mobile unit 105 will take.

[0092] Figure 5 This illustration shows an example of converting path information. For example... Figure 5 As depicted, path information 243 may include movement from point X to point Y, and movement from point Y to point Z. Multiple base station units 1101, 1102, 1103, 1104, and 1105, each with illustrative coverage areas, are also shown. Each base station unit exemplarily includes cells A, B, and C.

[0093] Therefore, after the path information 243 is converted, the converted path information 243 may include: base station unit 1101, base station unit 1102, base station unit 1104, base station unit 1103, and base station unit 1105. Preferably, the converted path information 243 may include: cell A of base station unit 1101, cell C of base station unit 1102, cell B of base station unit 1102, cell A of base station unit 1104, cell B of base station unit 1103, cell A of base station unit 1105, and cell C of base station unit 1105.

[0094] Figure 5 The diagram also illustrates movement from point Z to point P. All base station units 1101, 1102, 1103, 1104, and 1105 are connected to MME 1451. Another base station unit 1106 is connected to another MME 1452. The transformed path information for movement from point Z to point P may include: base station unit 1105 of MME 1451 and base station unit 1106 of MME 1452.

[0095] The converted path information can be used to set specific parameters for base station units 1101, 1102, 1103, 1104 and 1105.

[0096] For another example, the expected speed range 242 can be converted into the mobility mode and / or handover interval of the mobile unit. Mobility mode refers to the speed at which the mobile unit moves, such as low speed, high speed, etc. The expected speed range also helps predict when a handover will occur from one base station unit to another and / or from one cell to another.

[0097] The expected altitude range 241 also helps predict when a handover will occur. In some embodiments, various aspects of the subscription information configuration 200 can be used collaboratively to perform the handover. For example, the expected speed range 242 and the expected altitude range 241 can be used collaboratively to predict the handover interval.

[0098] Explanation back Figure 4 In step 435, SCEF 135 sends the converted subscription information configuration to HSS 140. In step 440, HSS 140 receives the converted subscription information configuration. In step 450, HSS 140 stores the converted subscription information configuration. Alternatively, HSS 140 may replace the existing converted subscription information configuration with the most recently received converted subscription information configuration.

[0099] Figure 6-1 The figure illustrates an attachment process 600 according to an embodiment of the present disclosure.

[0100] In step 610, the mobile unit 105 sends an attachment request to the MME 145.

[0101] In step 620, HSS 140 authenticates mobile unit 105 and sets NAS security to activate integrity protection and NAS encryption. If authentication is successful, HSS 140 sends subscription information configuration 200 as the subscription information for mobile unit 105 to MME 145. Figure 2 As illustrated, the subscription information configuration 200 includes air assistance information 240 and mobility restrictions 230. As explained above, the subscription information configuration 200 can preferably be a converted subscription information configuration that is easily understood by the base station unit.

[0102] In step 630, the ME identifier (IMEISV) should be retrieved from the mobile unit 105. This ME identifier should be transmitted encrypted. To minimize signaling latency, the retrieval of the ME identifier can be performed simultaneously with the NAS security settings in step 620. The MME 145 can send an ME identifier check request (ME identifier, IMSI) to the EIR. The EIR must respond with an ME identifier check confirmation (result). Depending on the result, the MME 145 decides whether to continue this attachment process or reject the mobile unit.

[0103] In step 640, the MME sends a Create session request to the SGW.

[0104] In step 650, the SGW sends a session creation request to the PGW.

[0105] In step 660, the PGW sends a session creation response to the SGW.

[0106] In step 670, the SGW sends a session creation response to the MME.

[0107] In step 680, the MME sends an Initial Context Establishment Request or a downlink NAS transmission with Attach Acceptance to the base station unit. This message includes a UE temporary identifier and subscription information configuration 200 (or a converted subscription information configuration). The base station unit can use subscription information configuration 200 (or the converted subscription information configuration) to set specific parameters.

[0108] In step 690, the base station unit sends an RRC connection reconfiguration message to the mobile unit. This message includes a UE temporary identifier and subscription information configuration 200 (or a converted subscription information configuration).

[0109] During the attachment process, subscription information configuration is received at the base station unit. The base station unit can set its parameters according to the subscription information configuration. Preferably, the subscription information configuration is received at the mobile unit. The mobile unit can adjust its own flight parameters according to the subscription information configuration.

[0110] Figure 6-2 Illustration Figure 6-1 A detailed embodiment of step 620 is shown in FIG. 6. The communication of step 620 is performed in the mobile unit 105, MME 145 and HSS 140. Figure 6-2 The communication performed between MME 145 and HSS 140 is described in detail. In step 620-1, MME 145 sends a request for subscription information configuration 200 to HSS 140. (See previous reference...) Figure 6-1 As discussed, if the HSS 140 is successfully authenticated, the HSS 140 sends the subscription information configuration 200 to the MME 145 as the subscription information of the mobile unit 105.

[0111] However, there may be situations where a valid subscription information configuration 200 is not available at HSS 140. For example, the HSS may not receive any subscription information configuration 200. Alternatively, timer information 250 of the subscription information configuration 200 can indicate that the duration of the subscription information configuration 200 has expired in HSS 140. In this case, because no valid subscription information configuration 200 is stored at HSS 140, HSS 140 cannot send the subscription information configuration 200 to MME 145.

[0112] If no valid subscription information configuration 200 is stored at HSS 140, in step 620-2, HSS 140 sends a request to air server 120 via SCEF 135 to request subscription information configuration 200. In response, in step 620-3, air server 120 sends a response message to HSS 140 including subscription information configuration 200. Step 620-3 can be... Figure 3 Method 300 or shown Figure 4 The method 400 shown is used to implement this. In step 620-4, HSS 140 sends subscription information configuration 200 as subscription information for mobile unit 105 to MME 145.

[0113] Timer information 250 has already been discussed as part of subscription information configuration 200. Timer information 250 defines the expiration time of subscription information configuration 200 in HSS 140. Therefore, according to an embodiment, when stored in HSS 140, subscription information configuration 200 or a converted subscription information configuration includes timer information 250. Figure 6-1 As shown in step 680, the subscription information configuration 200 or the converted subscription information configuration sent to the base station unit 110 may not include the timer information 250. It goes without saying that, as... Figure 6-1As shown in step 690, the subscription information configuration 200 or the converted subscription information configuration sent to the mobile unit 105 may also not include the timer information 250.

[0114] Step 680 in Figure 6 instructs the transmission of subscription information configuration 200 from MME 145 to base station unit 110. Subscription information configuration 200 can also be transmitted between different MMEs or between different base station units.

[0115] refer to Figure 5 The mobile unit can move from point X to point Y, or from point Y to point Z. Due to these movements (location changes), the mobile unit changes its connection with base station 1101 to base station 1102, and then to base station 1104 (for movement from point X to point Y), or changes its connection with base station 1104 to base station 1103, and then to base station 1105 (for movement from point Y to Z). In response to those location changes, subscription information configuration 200 can be sent from base station 1101 to base station 1102, and then to base station 1104, or from base station 1104 to base station 1103, and then to base station 1105.

[0116] Further reference Figure 5 As the mobile unit changes position from point Z to point P, it alters its connection with MME 1451 via base station unit 1105 or with MME 1452 via base station unit 1106. In response to this position change, subscription information configuration 200 can be sent from MME 1451 to MME 1452.

[0117] Figure 7 The diagram illustrates method 700 for configuring (especially using) reservation information.

[0118] The method begins in response to a connection between a specific mobile unit 105 and any of the base station units 110. In step 710, the base station unit 110 monitors the altitude and speed of the mobile unit 105.

[0119] In step 720, the height of the moving unit 105 is compared with the maximum permissible height determined from the height limit 231. If the height of the moving unit 105 does not exceed the maximum permissible height, the method proceeds to step 730. Otherwise, the method proceeds to step 740.

[0120] In step 730, the speed of mobile unit 105 is compared with the maximum permissible speed determined from speed limit 232. If the speed of mobile unit 105 does not exceed the maximum permissible speed, the method returns to step 710, where base station unit 110 continues to monitor the altitude and speed of mobile unit 105. Otherwise, the method proceeds to step 740.

[0121] If the height of mobile unit 105 exceeds the maximum permissible height, or if the speed of mobile unit 105 exceeds the maximum permissible speed, then in step 740, base station unit 110 may decide to terminate the connection from mobile unit 105 to base station unit 110. Step 740 is optional. Even if the height of mobile unit 105 exceeds the maximum permissible height, base station unit 110 may still choose to provide a connection with mobile unit 105 if it is capable of making a connection. Even if the speed of mobile unit 105 exceeds the maximum permissible speed, base station unit 110 may still choose to provide a connection with mobile unit 105 if it is capable of making a connection.

[0122] In step 750, base station unit 110 may send an alert message to air server 120. In response to the alert message, air server 120 may choose to send a new subscription information configuration to core network 130. The subscription information configuration may change mobility restrictions to avoid the alert message.

[0123] Other specific forms of the embodiments may be practiced. The described embodiments should be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than the foregoing description. All variations within the meaning and equivalents of the claims are included within their scope.

Claims

1. A method for configuring subscription information, comprising: The authentication device receives a subscription information configuration message transmitted from an external server, wherein the subscription information configuration message includes auxiliary information for configuring parameters of the base station unit for the mobile unit, an air server identifier, a user equipment identifier, an expiration time of the subscription configuration message, and mobility restriction parameters, and the auxiliary information includes at least one of expected altitude range, expected speed range, and path information, and wherein, in response to the expiration time, the subscription configuration message becomes invalid. The subscription information configuration message is authenticated at the authentication device, wherein the authentication device authenticates the subscription information configuration message by determining that the over-the-air server identifier and the user equipment identifier are valid; and In response to the successful authentication, the subscription information configuration message is sent to the subscription server; The subscription server stores the subscription information configuration message.

2. The method according to claim 1, wherein, In response to the successful authentication, the subscription information configuration message is converted into a format understandable by the base station unit, and the converted subscription information configuration message is sent to the subscription server.

3. The method according to claim 1, wherein, The mobility restriction parameters include a height restriction, which defines the maximum height of the mobile unit.

4. The method according to claim 3, wherein, In response to the mobile unit flying above the maximum altitude, an alarm message is sent from the base station unit to the external server.

5. The method according to claim 1, wherein, The mobility restriction parameters include a speed limit that defines the maximum speed of the mobile unit.

6. The method according to claim 5, wherein, In response to the mobile unit flying beyond the maximum speed, an alarm message is sent from the base station unit to the external server.

7. The method according to claim 1, wherein, Storing the subscription information configuration message includes modifying a previous subscription information configuration message into the subscription information configuration message.

8. The method of claim 1, further comprising: In response to the successful authentication of the mobile unit by the subscription server, the subscription information configuration message is sent from the subscription server to the control node.

9. The method of claim 8, further comprising: In response to a change in the position of the mobile unit, the subscription information configuration message is sent from the control node to another control node.

10. The method of claim 8, further comprising: In response to the attachment of the mobile unit to the control node, the subscription information configuration message is sent from the control node to the base station unit.

11. The method of claim 10, further comprising: In response to a change in the location of the mobile unit, the subscription information configuration message is sent from the base station unit to another base station unit.

12. The method of claim 10, further comprising: The subscription information configuration message is further sent from the base station unit to the mobile unit.

13. The method according to claim 1, wherein, The transmission of the subscription information configuration message is performed in response to a request from the subscription server.

14. A system for configuring subscription information, comprising: Authentication device, the authentication device: The system receives a subscription information configuration message from an external server. The subscription information configuration message includes auxiliary information for configuring parameters of the base station unit for the mobile unit, an air server identifier, a user equipment identifier, an expiration time for the subscription configuration message, and mobility restriction parameters. The auxiliary information includes at least one of expected altitude range, expected speed range, and path information. The subscription configuration message becomes invalid in response to the expiration time. Authenticating the subscription information configuration message, wherein the authentication device authenticates the subscription information configuration message by determining that the over-the-air server identifier and the user equipment identifier are valid; and In response to the successful authentication, the subscription information configuration message is sent to the subscription server; The subscription server stores the subscription information configuration messages.

15. The system according to claim 14, wherein, In response to the successful authentication, the authentication device converts the subscription information configuration message into a format understandable by the base station unit and sends the converted subscription information configuration message to the subscription server.

16. The system according to claim 14, wherein, The subscription server deletes the previous subscription information configuration message.

17. The system according to claim 14, wherein, The subscription server requests the external server to send the subscription information configuration message to the authentication device.

18. The system according to claim 14, wherein, The system further includes: a control node, wherein, in response to successful authentication of the mobile unit by the subscription server, the subscription information configuration message is sent from the subscription server to the control node; and a base station unit, wherein, in response to the attachment of the mobile unit to the control node, the subscription information configuration message is sent from the control node to the base station unit.

19. A method for configuring subscription information, comprising: Initiate an attachment process for the mobile unit, wherein the attachment process includes an air server identifier and a user equipment identifier, and the authentication of the attachment process determines whether the air server identifier and the user equipment identifier are valid; and In response to the authentication of the attachment process, a subscription information configuration message is transmitted to the base station unit, wherein the subscription information configuration message includes auxiliary information for configuring parameters of the base station unit for the mobile unit, the air server identifier, the user equipment identifier, the expiration time of the subscription configuration message, and mobility restriction parameters, and the auxiliary information includes at least one of expected altitude range, expected speed range, and path information, and wherein, in response to the expiration time, the subscription configuration message becomes invalid.

20. The method of claim 19, further comprising: Obtain the subscription information configuration message from an external server.

Images