A cellular network architecture in which gateway nodes function as hubs.

Abstract

A cellular network architecture is disclosed in which a gateway node (308) functions as a hub. The gateway node (308) determines a unique UE context for each of the first coverage states and second coverage states of the user equipment (UE) (312). The gateway node (308) dynamically stores the unique UE context. Furthermore, the gateway node (308) shares paging messages with the core network (CN) (304). The unique UE context may be stored in the CN (304) to provide seamless mobility services to the UE (312).

Description

Technical Field

[0001] Reservation of Rights Part of the disclosure of this patent specification includes matters that are the subject of intellectual property rights including, but not limited to, copyrights, design rights, trademark rights, rights to use integrated circuit (IC) circuit layouts, and / or trade dress protection owned by Geo Platforms Limited (JPL) or its related companies (hereinafter referred to as "the rights holder"). The rights holder does not object to any person's reproduction of the patent document or patent disclosure content in the form appearing in the patent file or records of the Patent Office, but reserves all other rights. All rights regarding such intellectual property rights are fully reserved by the rights holder.

[0002] This disclosure relates to the field of wireless networks, and more particularly to methods and apparatuses for providing a cellular network architecture in which a gateway functions as a hub.

Background Art

[0003] The following description of related technologies aims to provide background information related to the field of this disclosure. This section may include specific aspects of technologies related to various features of this disclosure. However, it should be understood that this section is used only to deepen the reader's understanding of this disclosure and is not used as an approval of the prior art. The current 5th generation (5G) communication technology has been developed in the 3rd Generation Partnership Project (3GPP (registered trademark)) and aims to provide higher multi-Gbp peak data speeds, very short latency, higher reliability, large network capacity, improved availability, and a uniform user experience for multiple users. The advanced performance and efficiency improvement of 5G technology connect new industries and improve the user experience. Although some of the goals required by the industry have been achieved with the advent of 5G technology, problems to be solved such as the response of the industrial field, the architecture to support private networks, and the support for flexible network deployment still exist.

[0004] Furthermore, while available 5G network architectures support private networks, they remain in a rudimentary manner. Mechanisms for incorporating dynamic addition / removal of private / host-neutral radio access network (RAN) nodes into the network are currently unavailable, hindering the utilization and monetization of certain frequency band pools. Additionally, current 5G architectures do not support coreless operation of radio access nodes, which may be "host-neutral" or consist of private deployments or other diverse combinations of private / public radio access node deployments. Deployment of private radio access nodes requires prior agreement with macro-network operators and interoperability with the core network. Existing 5G architectures do not support the provision of gateways that use private RAN node deployments to search for core networks that can search for available core networks for specific functions and private RAN deployments for capacity expansion. [Overview of the Initiative] [Problems that the invention aims to solve]

[0005] Therefore, there has been a need to provide an improved gateway node that functions as a hub in a cellular network architecture and addresses challenges related to the coreless operating mode of wireless access nodes and network flexibility.

[0006] The purpose of this disclosure is to provide a network architecture having a gateway that functions as a private access connection hub for connecting to one or more core networks (CNs).

[0007] The purpose of this disclosure is to enable third parties to deploy gateways by connecting one or more CNs to a Radio Access Network (RAN) node.

[0008] The purpose of this disclosure is to provide a gateway-assisted cellular network architecture in which paging is successful only after updates to user devices (UEs) have been successfully performed at different levels in a mobile environment.

[0009] The purpose of this disclosure is to enable gateways to be offered as a service by any entity other than RAN service providers and CN service providers.

[0010] The purpose of this disclosure is to enhance communication systems.

[0011] The purpose of this disclosure is to dynamically manage network requirements using a gateway-assisted network.

[0012] The purpose of this disclosure is to provide network upgrades that support sixth-generation (6G) communication technology.

[0013] The purpose of this disclosure is to optimize network infrastructure costs.

[0014] The purpose of this disclosure is to enhance data security.

[0015] The purpose of this disclosure is to dynamically allocate infrastructure based on user-defined requirements.

[0016] The purpose of this disclosure is to provide on-demand communication infrastructure.

[0017] The purpose of this disclosure is to facilitate aspects related to paging and tracking in network communications. [Means for solving the problem]

[0018] This section is provided to give a simplified overview of certain purposes and aspects described later in this specification. This summary is not intended to identify any important features or scope of the subject matter of the claims.

[0019] In one embodiment, the disclosure relates to a system comprising one or more processors and a memory that stores instructions causing the system to determine a unique UE context for each of a first coverage state and a second coverage state of the UE, when executed by the one or more processors. The one or more processors may dynamically store the determined unique UE context of the UE. Furthermore, the one or more processors may send paging messages to the CN. The unique UE context may be stored in the CN to provide the UE with seamless mobility services.

[0020] In one embodiment, the first coverage state may correspond to the UE being within the coverage area provided by the system, and the second coverage state may correspond to the UE being outside the coverage area provided by the system.

[0021] In one embodiment, the system may function as an independent hub for establishing connections between a radio access network (RAN) node and a CN.

[0022] In one embodiment, the system may specify the radio access function of a RAN node to the UE. The radio access function may include information relating to at least one of the following: type, bandwidth, spectrum, bandwidth, and offset, associated with the RAN node.

[0023] In one embodiment, the system may include at least one of the following: a spectrum negotiation function, a payment function, a paging and tracking function, and a security maintenance function.

[0024] In one embodiment, the system and the CN may each send a paging message to the network node and the core network node when a download (DL) message is to be delivered from the CN to the UE.

[0025] In one embodiment, the paging message is sent when the handover between the network node and the core network node via the system is successfully completed.

[0026] In one aspect, the present disclosure relates to a method for determining a unique UE context for each of a first coverage state of a UE and a second coverage state of the UE. The system may dynamically store the determined unique UE context. The system may send a paging message to the CN. The unique UE context is stored in the CN to provide seamless mobility services to the UE.

[0027] In one aspect, the present disclosure relates to a non - transient computer - readable medium comprising processor - executable instructions that cause a processor to determine a unique UE context for each of a first coverage range state of a UE and a second coverage range state of the UE. The processor may dynamically store the determined unique UE context of the UE. The processor may send a paging message to the CN. The unique UE context is stored in the CN to provide seamless mobility services to the UE.

[0028] In one aspect, the present disclosure relates to a UE comprising one or more processors and a memory operatively connected to the one or more processors and the system, wherein the system is configured to determine a unique UE context for each of a first coverage range state and a second coverage range state of the UE. The system may dynamically store the determined unique UE context of the UE. The system may send a paging message to the CN. The unique UE context is stored in the CN to provide seamless mobility services to the UE.

Brief Description of the Drawings

[0029] The accompanying drawings, which are incorporated herein and form a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems where like reference numerals represent the same or similar elements throughout different drawings. The components of the drawings are not necessarily to scale, with emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some of the drawings may use block diagrams to show components and may not necessarily represent the internal circuits of each component. It will be understood by those skilled in the art that such a disclosure of drawings may include the disclosure of electrical components, electronic components or circuits commonly used to implement such components.

[0030] [Figure 1] FIG. 1 shows an independent private 5th generation (5G) network architecture.

[0031] [Figure 2A-2B] FIGS. 2A - 2B show an exemplary shared private 5G network architecture.

[0032] [Figure 3A] FIG. 3A shows a connection architecture showing a gateway node functioning as a core network (CN) interface according to an embodiment of the present disclosure.

[0033] [Figure 3B] FIG. 3B shows an exemplary network architecture showing a gateway node functioning as an interface of the CN according to an embodiment of the present disclosure.

[0034] [Figure 3C] FIG. 3C shows an exemplary block diagram of a gateway node according to an embodiment of the present disclosure.

[0035] [Figure 4]Figure 4 shows a process flow diagram illustrating mutual authentication between a 6G core network (6GCN) and a gateway according to an embodiment of the present disclosure.

[0036] [Figure 5] Figure 5 shows a process flow diagram in which a gateway according to an embodiment of the present disclosure queries the CN for functionality.

[0037] [Figure 6] Figure 6 shows an exemplary configuration of a gateway functioning as a hub according to an embodiment of the present disclosure.

[0038] [Figure 7] Figure 7 shows a process flow diagram in which a CN according to an embodiment of the present disclosure queries a gateway for the availability of a radio access network (RAN) node for service provision.

[0039] [Figure 8] Figure 8 shows a process flow diagram illustrating how a RAN node queries a gateway to determine the availability of a CN to provide a specific service provided by the functionalities of the embodiments of this disclosure.

[0040] [Figure 9] Figure 9 shows a sequence flow diagram illustrating how various problems in a no-movement scenario are addressed according to embodiments of this disclosure.

[0041] [Figure 10] Figure 10 shows a sequence flow diagram illustrating how various problems in situations with small movement are addressed according to embodiments of this disclosure.

[0042] [Figure 11A-11C] Figures 11A to 11C show sequence flow diagrams illustrating how to address various problems in wide-area mobile situations according to embodiments of this disclosure.

[0043] [Figure 12]Figure 12 shows a sequence flow illustrating the operations performed by a gateway node that functions as a hub in a cellular network architecture according to an embodiment of the present disclosure.

[0044] [Figure 13] Figure 13 shows an exemplary computer system that may implement an embodiment of the present disclosure. [Modes for carrying out the invention]

[0045] In the following description, various specific details are provided for illustrative purposes to fully understand embodiments of the disclosure. However, it is clear that embodiments of the disclosure may be carried out without these specific details. The features described below may be used independently of each other or in any combination with other features. Individual features may not address all of the problems described above, or may address only some of the problems described above. Some of the problems described above may not be completely resolved by any feature described herein.

[0046] The following description provides only exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the following description of exemplary embodiments provides a feasible explanation for carrying out the exemplary embodiments for those skilled in the art. It should be understood that various modifications can be made to the function and arrangement of the elements without departing from the spirit and scope of the disclosure described herein.

[0047] In the following description, specific details are provided to allow for a full understanding of the embodiments. However, it will be understood by those skilled in the art that embodiments can be carried out without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as block diagrams to avoid obscuring the embodiments with unnecessary details. In other examples, well-known circuits, processes, algorithms, structures, and techniques may be shown with unnecessary details omitted to avoid obscuring the embodiments.

[0048] Furthermore, note that individual embodiments may be described as processes shown in flowcharts, flow diagrams, data flow diagrams, structural diagrams, or block diagrams. While flowcharts may describe operations as sequential processes, many operations may be performed in parallel or simultaneously. Moreover, the order of operations may be rearranged. A process terminates when its operation is complete, but it may have additional steps not shown. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to the function's return to the calling function or the main function.

[0049] In this specification, the terms “exemplary” and / or “demonstrative” mean that they function as examples, cases, or descriptions. To avoid doubt, the subject matter disclosed herein is not limited by such examples. Furthermore, no aspect or design described herein as “exemplary” and / or “demonstrative” should be construed as being preferable or advantageous to other aspects or designs, nor is it intended to exclude equivalent exemplary structures and techniques well known to those skilled in the art. Furthermore, where “includes,” “has,” “contains,” and other similar terms are used in the detailed description or claims, such terms are as inclusive as the open conjunction “equipped with,” without excluding additional or other elements.

[0050] Throughout this specification, the expressions “one embodiment,” “embodiment,” “example,” or “example” mean that a particular function, structure, or feature described in relation to an embodiment is included in at least one embodiment of this disclosure. Therefore, expressions such as “in one embodiment” or “in an embodiment” appearing in various places throughout this specification do not necessarily all refer to the same embodiment. Furthermore, a particular function, structure, or feature may be combined in any suitable manner in one or more embodiments.

[0051] The terms used herein are for the purpose of describing specific embodiments and are not intended to limit the scope of the disclosure. In this specification, the singular forms “a,” “an,” and “the” are intended to include the plural form unless otherwise intended by context. Furthermore, it is understood that the terms “including” and / or “including” as used herein specify the presence of the features, elements, steps, actions, components, and / or components described herein, but do not exclude the presence or addition of one or more other features, elements, steps, actions, components, and / or groups thereof. In this specification, the terms “and / or” include any combination of one or more of the related enumerated items.

[0052] Private fifth-generation (5G) network architectures are categorized into several categories, as shown below, according to their differing deployment options based on the level of integration with the mobile operator's public network. • Independent network: In this specification, the entire private network is owned and operated by the user and is completely isolated from the public network. • Shared Network: The shared network has a hybrid configuration that utilizes part of the infrastructure of the telecommunications service provider. • Private network slicing under a public network: Private networks are realized through network slicing and leverage the operator's existing public network infrastructure, providing private connectivity through software-defined network slicing.

[0053] Figure 1 shows an independent private 5G network architecture 100. In this architecture, the entire network is hosted and operated by the user to have complete control over the network. The network is completely isolated from the public network to minimize the risk of data leakage. However, the investment in building and operating the infrastructure of this architecture is very high and requires personnel with advanced knowledge of communication networks. An isolated private 5G network architecture is suitable for public safety agencies or large corporations that have abundant resources and are highly concerned with data privacy. For example, a public communication system may be maintained for a rescue team with an isolated private 5G network installed in a mobile vehicle.

[0054] Figures 2A and 2B show exemplary shared private 5G network architectures 200 and 210, respectively. As illustrated, the shared private 5G network architecture shares the infrastructure of the mobile operator's public network. This is to reduce the cost of building a private 5G network. Depending on one or more business requirements, the user may choose the ratio of components managed by the user to components managed by the user. For example, in the case of a smart factory, it may be preferable to place multi-access edge computing (MEC) and user plane functions (UPF) on-premises. This can provide a private 5G architecture that enables low-latency communication while leaving room for future modifications. In other use cases requiring high-speed and stable connectivity, such as stadiums or exhibition halls, operators may maintain a radio access network (RAN) locally. This allows them to manage network coverage and network quality while leaving system management to the operator.

[0055] This disclosure relates to an architecture that supports dynamic connection / disconnection between a private RAN (hereinafter also referred to as a host-neutral RAN node / mobility node / RAN node) and a core network via a gateway (hereinafter also referred to as a gateway node or gateway hub). The gateway provides necessary security measures, spectrum negotiation functions, and settlement functions, and facilitates the execution of related procedures and mechanisms. The connection between the RAN and the core network via the gateway is also useful in mobile communications situations where the RAN node is an unmanned aerial vehicle (UAV) and may be unable to access the core network for a certain period of time.

[0056] Various embodiments of this disclosure will be described in detail with reference to Figures 3-13.

[0057] Figure 3A shows a connectivity architecture 300 that includes a gateway node 308 that functions as a core network interface according to an embodiment of the present disclosure. As shown in Figure 3, in the connectivity network architecture, there is a gateway node 308 that functions as an interface to the core network (CN) 304 (also referred to herein as the 6G core network (6GCN) 304). The gateway node 308 may be owned by a mobile network operator. The gateway node 308 is implemented as a system and may be referred to interchangeably with system 308.

[0058] Figure 3B shows an exemplary network architecture 340 of a gateway node 308 that functions as an interface to CN304 according to an embodiment of the present disclosure.

[0059] As shown in Figure 3B as an example that is not limited, the exemplary network architecture 340 may have multiple user devices (UEs) 312-1, 312-2...312-N, which are individually referred to as UE312 and collectively as UE312. Note that UE312 may be read interchangeably as user device, client device, or computer device. Multiple UE312s may have, but are not limited to, scanners such as cameras, webcams, and scanning devices.

[0060] In one embodiment, UE312 may have smart devices operating in a smart environment, such as an Internet of Things (IoT) system. In such embodiments, UE312 includes, but is not limited to, smartphones, smartwatches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), network-connected home appliances, network-connected peripherals, network-connected lighting systems, communication equipment, network-connected vehicle accessories, network-connected in-vehicle equipment, smart accessories, tablets, smart televisions (TVs), computers, smart security systems, smart home systems, other devices for monitoring or interacting with users and / or entities, or any combination thereof.

[0061] Those skilled in the art will understand that the computing device, user equipment, or UE312 may include, but not be limited to, intelligent multisensing network connectivity devices that can seamlessly integrate with each other and / or with a central server, cloud computing system, or other network-connected devices.

[0062] In one embodiment, UE312 includes, but is not limited to, portable wireless communication devices (e.g., mobile phones, smartphones, phablet devices, etc.), wearable computer devices (e.g., head-mounted display computer devices, head-mounted camera devices, wristwatch computer devices, etc.), global positioning system (GPS) devices, laptop computers, tablet computers, other types of portable computers, media players, portable game systems, and / or other types of computer devices with wireless communication capabilities. In one embodiment, UE312 includes, but is not limited to, electrical equipment, electronic equipment, electromechanical equipment, or one or more combinations of the above-mentioned devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptops, general-purpose computers, desktops, personal digital assistants, tablet computers, mainframe computers, or other computing devices, and UE312 includes, but is not limited to, one or more built-in or externally connected accessories, including visual aids such as cameras, audio aids, microphones, keyboards, and input devices that receive input from a user or entity such as touchpads, touch-enabled screens, and electronic pens.

[0063] Those skilled in the art will understand that UE312 is not limited to the apparatus described above and that various other apparatuses may be used.

[0064] In one embodiment, UE312 can communicate with CN304 via network 302 and gateway node 308. Gateway nodes 308-1, 308-2...308-N are individually referred to as gateway node 308 and collectively as gateway node 308. Gateway node 308 may be one or more gateways, such as one or more next-generation radio access network (NG-RAN) node gateways or one or more home NG-RAN node gateways. Network 302 may include, but is not limited to, at least part of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process or combine thereof one or more messages, packets, signals, waves, voltage or current levels, or some combination thereof. Network 302 includes, but is not limited to, wireless networks, wired networks, the Internet, intranets, public networks, private networks, packet-switched networks, circuit-switched networks, ad-hoc networks, infrastructure networks, public switched telephone networks (PSTN), cable networks, cellular networks, satellite networks, fiber optic networks, and several combinations thereof.

[0065] In one embodiment, CN304 may be associated with multiple base stations 306-1, 306-2, ..., 306-N, and these multiple base stations 306-1, 306-2, ..., 306-N are individually called base stations 306 and collectively called a group of base stations 306. Base stations 306 include, but are not limited to, macro base stations, small cell base stations, etc. It is understood that base station 306 may also be a next-generation NodeB (gNB). Base station 306 may also be called a core network node 306 or gNodeB306 below.

[0066] In one embodiment, one or more network nodes 310-1, 310-2...310-N may be distributed to a geographical area to provide communication between UE312 and CN304, and one or more network nodes 310-1, 310-2...310-N may be individually called network nodes 310 and collectively called a group of network nodes 310. Network nodes 310 may use wireless communication technology to communicate with UE312 via a communication channel. For example, each network node 310 may be configured as a base station. In various embodiments, the communication channel may be associated with a license spectrum. Furthermore, network nodes 310 may communicate between UE312 and CN304. As shown in Figure 3B, network node 310-1 may function as an interface between UE312-1 and CN304 via gateway node 308-2. Furthermore, network node 310-N may function as an interface between UE312-N and CN304 via gateway node 308-N. Network node 310 is also referred to as RAN node 310 in this specification.

[0067] In one embodiment, paging messages are forwarded from the core network node 306 to the UE 312 connected to the network node 310, via the gateway node 308. The core network node 306 may be connected to the CN 304. In one embodiment, paging messages are forwarded upon successful completion of the handover between the UE 312 and the CN 304. In one embodiment, the UE 312 receives paging messages and download (DL) messages from the core network node 306 via the gateway node 308. The UE 312 may connect to the paging messages and perform continuous measurements to the core network node 306. As understood, the continuous measurements correspond to the core network node 306 having a predetermined strength in order to provide the UE 312 with a seamless mobility service.

[0068] In one embodiment, the gateway node 308 may determine a unique UE context for UE312 for each of the first and second coverage states of UE312. Furthermore, based on the determined unique UE context of UE312, the gateway node 308 may dynamically store the UE context. Furthermore, the gateway node 308 may share paging messages with CN304. The unique UE context may be stored in CN304 to provide seamless mobility services to UE312. In one embodiment, the first coverage state may correspond to UE312 being within the coverage area provided by the gateway node 308, and the second coverage state may correspond to UE312 being outside the coverage area provided by the gateway node 308. In one embodiment, the gateway node 308 may function as an independent hub for establishing connections between radio access network (RAN) nodes and CN.

[0069] In one embodiment, when a downlink message should be delivered from the core network node 304 to the user terminal 312, the gateway node 308 and the core network node 304 may each send a paging message to the network node 310 and the core network node 306. The paging message may also be sent when the handover between the network node 310 and the core network node 306 via the gateway node 308 is successfully completed.

[0070] Figure 3B shows exemplary components of the network architecture 340, but in other embodiments, the network architecture 340 may have fewer components than those shown in Figure 3B, components different from those shown in Figure 3B, components in a different arrangement than those shown in Figure 3B, or additional functional components to those shown in Figure 3B. Additionally or alternatively, one or more components of the network architecture 340 may perform functions described as being performed by one or more other components of the network architecture 340.

[0071] In one embodiment, the gateway node 308 may facilitate the deployment of a private RAN node 310 to search for available CN304 for a specific function. Furthermore, CN304 may search for a private RAN deployment for capacity expansion. In such a scenario, the gateway node 308 functions as a hub. In other deployments, the gateway node 308 may be part of a core / macro network deployment.

[0072] In one embodiment, the gateway node 308 may function as an independent hub that enables one-to-many connectivity from the RAN nodes 310 to the core network. The gateway node 308 may provide necessary security considerations, spectrum negotiation capabilities, settlement capabilities, manage related procedures and mechanisms, and maintain considerations regarding paging and tracking areas.

[0073] Figure 3C shows an exemplary block diagram 380 of a gateway node 308 according to an embodiment of the present disclosure.

[0074] In one embodiment, as shown in Figure 3C, the gateway node 308 may have one or more processors 314. One or more processors 314 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuits, and / or any devices that process data based on operational instructions. Among other functions, one or more processors 314 may be configured to retrieve and execute computer-readable instructions stored in the memory 316 of the gateway node 308. The memory 316 may store one or more computer-readable instructions or routines, which may be retrieved and executed to create or share data units over network services. The memory 316 may comprise any non-temporary storage device, including, for example, volatile memory such as random access memory (RAM) or non-volatile memory such as erasable programmable read-only memory (EPROM), flash memory, etc.

[0075] In one embodiment, the gateway node 308 may also have an interface 328. Interface 328 may include various interfaces, such as interfaces to data input / output devices called I / O devices, storage devices, etc. One or more interfaces 328 may facilitate communication between the gateway node 308 and various devices connected thereto. Interface 328 may provide a communication path for one or more components of the gateway node 308. Examples of such components include, but are not limited to, one or more processing engines 318 and a database 330.

[0076] In one embodiment, the processing engine 318 may be implemented as a combination of hardware and programming (e.g., programmable instructions) to implement one or more functions of the processing engine 318. In the examples described herein, such a combination of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine 318 may be processor-executable instructions stored in a non-temporary machine-readable storage medium, and the hardware for one or more processors 314 may include processing resources (e.g., one or more processors) for executing such instructions. In this embodiment, the machine-readable storage medium may store instructions that, when executed by the processing resources, implement the (one or more) processing engines 318. In such an example, the gateway node 308 may include a machine-readable storage medium for storing instructions and processing resources for executing the instructions, or the machine-readable storage medium may be separate but accessible to the gateway node 308 and the processing resources. In other examples, the (one or more) processing engines 318 may be implemented by electronic circuits.

[0077] In one embodiment, the database 330 may include data that may be stored or generated as a result of a function implemented by any of the components of the processor 314, processing engine 318, or gateway node 308.

[0078] In one embodiment, the processing engine 318 may include one or more engines selected from the decision engine 320, the storage engine 322, the sharing engine 324, and other units / engines 326. The other units / engines 326 include, but are not limited to, a monitoring engine, a receiving engine, etc.

[0079] In one embodiment, one or more processors 314 may determine a unique UE context for UE312 for each of a first coverage state and a second coverage state of UE312 via a decision engine 320. The first coverage state may correspond to UE312 being within the coverage area provided by the gateway node 308, and the second coverage state may correspond to UE312 being outside the coverage area provided by the gateway node 308. The unique UE context may be stored in the gateway node 308. The gateway node 308 may function as an independent hub for establishing connections between the RAN node 310 and CN304.

[0080] In one embodiment, one or more processors 314 may dynamically save a determined unique UE context of the UE 312 via a storage engine 322.

[0081] In one embodiment, one or more processors 314 may share paging messages with CN 304 via a shared engine 324. A unique UE context is stored in CN to provide seamless mobility services to UE 312. The gateway node may specify the radio access function of RAN node 310 to UE 312. The radio access function includes, for example, information related to at least one of the type, bandwidth, spectrum, bandwidth, and offset associated with RAN node 310. The gateway node 308 may include at least one of spectrum negotiation function, settlement function, paging and tracking function, and security maintenance function.

[0082] In one embodiment, when a downlink message should be delivered from the core network node 304 to the user terminal 312, the gateway node 308 and the core network node 304 may each send a paging message to the network node 310 and the core network node 306. The paging message is sent when the handover between the network node 310 and the core network node 306 via the gateway node 308 is successfully completed.

[0083] Figure 3C shows an example of the components of gateway node 308, but in other embodiments, gateway node 308 may have fewer components than those shown in Figure 3C, components different from those shown in Figure 3C, components arranged differently from those shown in Figure 3C, or additional functional components to those shown in Figure 3C. Additionally or alternatively, one or more components of gateway node 308 may perform functions described as being performed by one or more other components of gateway node 308.

[0084] Figure 4 shows a process flow diagram 400 illustrating the mutual authentication of 6GCN304 and gateway 308 according to an embodiment of the present disclosure.

[0085] With respect to Figure 4, 6GCN304 and gateway 308 may authenticate each other and create local contexts for each other (i.e., 6GCN304 may have a gateway context, and vice versa). The context may be, for example, a private network group (ID), a private base station (ID), a list of QoS (Quality of Service) / QoE (Quality of Experience) negotiated for a base station / base station group, and / or a list of bandwidths collectively or individually guaranteed for a base station or a user / device / device type behind a base station.

[0086] Gateway 308 may query CN / 6GCN304 for functionality and cache the functionality of CN304. The functionality of CN 304 may include, for example, spectral information, information about the available RAN load that CN304 can use at a particular location, and functionality that provides a specific class of QoS / QoE experience for a specific class of available devices / applications.

[0087] The diagram 500 shows a process flow in which a gateway 308 according to an embodiment of the present disclosure queries a CN 304 for functionality. In one embodiment, the gateway 308 may function as a hub, i.e., the gateway 308 may be deployed by a “gateway service provider,” and the hub may advertise services. Multiple radio base stations may use a hub gateway to connect to different CN 304s to access a variety of services. Services on the CN 304 may include, for example, service provision for a specific class of applications such as the Internet of Things (IoT), provision of video surveillance connectivity with video analytics capabilities, conversational services, gaming services, and the like.

[0088] Figure 6 shows an exemplary representation 600 of a gateway 308 functioning as a hub according to an embodiment of the present disclosure. As illustrated, the gateway 308 as a hub can be pre-registered with and queried by either the RAN node 310 or the CN304, in one embodiment following a flow similar to the flow described in the paragraph above, except that the hub may have pre-context information of the RAN node 310 and what that node is searching for, or context information of the CN304 and what its network is searching for. The CN304 or the RAN node 310 may register with the gateway 308 via a callback when the CN304 / RAN node 310 becomes available.

[0089] Figure 7 shows a process flow diagram 700 in which CN304 queries gateway 308 for the availability of RAN node 310 for service provision according to an embodiment of the present disclosure.

[0090] As illustrated, CN304 may query gateway 308 for the availability of RAN nodes 310 that have capacity to provide service. However, if no service / capacity is available, CN304 may register with gateway 308 to receive a callback when such RAN node 310 registers with gateway 308. To understand, the parameter “coverage geography” provides Global Positioning System (GPS) coordinates for the geographical area where RAN functionality is provided or available. The parameter “RAN capacity” provides capacity details such as the required number of 6GNodeBs (6GNBs), the required number of connected users supported, the required total throughput support, the required latency support, and the required QoS support. The parameter “RAN type” indicates which type of RAN functionality is required, such as macro-type 6GNB only, small-cell type 6GNB only, a combination of either, non-terrestrial network (NTN) based 6GNB only, or a combination of all types. The parameter "RAN availability" is a flag. When this flag is set to "true," it indicates to the gateway that it will begin monitoring the availability of the requested RAN capacity and can send a confirmation request to 6GCN once the expected conditions are met. The parameter "charging rate" provides details of the charging rate and whether the rate is applicable to a continuous period or a time frame.

[0091] Figure 8 shows a process flow diagram 800 in which the RAN node 310 queries the gateway 308 to determine the availability of CN304 to provide a specific service according to an embodiment of the present disclosure.

[0092] As illustrated, RAN node 310 may query gateway 308 about the availability of CN304, which may provide specific services for key performance indicators (KPIs) of QoS / QoE, or the availability of specific bandwidth / load handling functions. If such services / capacity are not available on CN304, RAN node 310 registers a callback with gateway 308 for when service capacity becomes available on CN304. The parameter “coverage geography” may provide GPS coordinates for the geographical area that needs to provide or make available core network functions. The parameter “RAN capacity” provides details of the required capacity, e.g., the number of 6GNBs required, support requirements for the number of connected users, total throughput, latency, and support for QoS. The parameter “CN capacity” may provide CN capacity details such as latency, the number of supported users, supported QoS, slicing support, load balancing support, and Access Traffic Steering Switching & Splitting (ATSSS) support. The parameter “CN Availability” is a flag; when set to “true”, it indicates to the gateway that it can begin monitoring the availability of the requested CN capacity. If the expected conditions are met, confirmation may be sent to the requested (one or more) 6GNB306. The parameter “charging rate” provides details of the charging rate and whether the rate is applicable to a continuous period or a time frame.

[0093] In one embodiment, the gateway 308 may be responsible for maintaining the UE context for a given "(one or more) private RAN nodes." In another embodiment, various device types may be classified at the RAN node 310 based on the UE 312's movement type (i.e., movement within campus / enterprise, wide-area movement, or no movement). The handling of movement context to address the UE 312's movement issues will be described in detail in a later paragraph.

[0094] Regarding the movement context, three broad scenarios may be considered to address various issues such as paging context, location area tracking, and update delivery at gateway 308: no movement, small movement, and wide-area movement.

[0095] In the no-movement scenario, it is assumed that gateway 308 and localized private RAN node 310 are part of the campus / enterprise providing data services, and that only such RAN node 310 exists. Therefore, RAN node 310 only needs to support very limited movement for its users / UE312.

[0096] Figure 9 shows a sequence flow diagram 900 illustrating how to address various problems in a no-movement situation according to embodiments of this disclosure.

[0097] The following steps will be taken in response to this situation. In Step 1, UE1312-1 and UE2312-2 register with the gateway 308 associated with the local or private RANNode B310 for the desired services. In step 2, UE1312-1 initiates a mobile outgoing (MO) data call to UE2312-2. In step 3, UE1312-1 sends a Radio Resource Control (RRC) connection request to the local or private RANNodeB310, with the cause being an MO call. In step 4, RANNodeB310 forwards a message to gateway 308 via a service request that includes the UE identifier and the cause of establishment. In step 5, gateway 308 checks the availability of context and location information for UE1312-1. In step 6, if the context and information are confirmed, gateway 308 performs paging to RANNodeB310, and RANNodeB310 sends a message via the paging channel (PCH) for the search of UE2 312-2. In step 7, UE2312-2 establishes a connection and participates in data calls with UE1312-1.

[0098] For situations involving small movements, the gateway 308 and localized private RAN nodes 310 are considered part of the campus / enterprise providing data services, and it is assumed that there are multiple such RAN nodes 310, with UE 312 being allowed to freely roam between these RAN nodes 310 served by the gateway 308. Therefore, the gateway 308 needs to maintain a UE context related to which private RAN node 310 a particular UE 312 is connected to and served by. Based on this information, paging is performed for incoming messages / calls.

[0099] To ensure understanding, a set of preconditions is declared for situations with small mobility. We may assume that a particular gateway 308 has at least two associated RANNodeB 310s and serves multiple UE 312s in its vicinity. Thus, all UE 312s associated with or registered with a particular gateway 308 (of the private network) can freely roam within the radio coverage provided by the RANNodeB 310s associated with that particular gateway 308.

[0100] A set of preconditions applies to situations involving small movements. An 'Xn' interface exists between the two RANNodeB310s for exchanging handover and other similar messages. If such an interface does not exist, messages are forwarded via gateway 308.

[0101] Figure 10 shows a sequence flow diagram 1000 illustrating how to address various problems in situations with small movement according to embodiments of this disclosure.

[0102] The procedure for exchanging messages when movement is small is as follows: In step 1, UE1312-1 and UE2312-2 register with the gateway 308 associated with the local or private RANNodeB 310 for the desired services. In this specification, UE1312-1 is initially latched to RANNodeB1310-1, and UE2312-2 is latched to RANNodeB 2310-2. In step 2, UE1312-1 shares a measurement report with RANNodeB2310-2 showing that RANNodeB2310-2 is a stronger cell than the service cell. In step 3, RANNodeB1310-1 notifies RANNodeB2310-2 of a handover request, and RANNodeB2310-2 approves it. In step 4, RAN NodeB1310-1 sends a handover start signal to UE1312-1 in order to latch onto RANNodeB2310-2. In step 5, RANNodeB2310-2 updates the context of UE1312-1 for gateway 308, along with its location information. In step 6, gateway 308 uses this context awareness to page UE1312-1 via RANNodeB2310-2 to send downlink (DL) messages. In step 7, the UE2312-2 successfully reads the paging message and connects to and receives the DL data message.

[0103] In the context of wide-area mobility, gateway 308 may assist UE 312 in servicing roaming between a private local network (provided by RAN node 310 and associated gateway 308) and a public network when connected to a predetermined core network. Therefore, gateway 308 needs to maintain the context of UE 312 when UE 312 is within and outside the coverage area, and manage paging messages accordingly with CN 304. To this end, gateway 308 needs to be fully synchronized with CN 304 to accurately preserve the context, so that UE 312 is provided with seamless mobility-related services. This disclosure facilitates the determination of how this context is preserved and kept synchronized with CN 312.

[0104] As a prerequisite for this situation, we may assume that gateway 308 has one or more registered / associated RANNodeB310s. Initially, UE312 is attached to RANNodeB1310-1.

[0105] Furthermore, the scenario assumes that there is no Xn interface between RANNodeB310 and gNodeB306. If such an interface exists, both RANNodeB310 and gNodeB306 can communicate directly with each other, and once a handover is approved by the target NodeB, the target NodeB can perform context updates on both gateway 308 and 6GCN304. Note that gNodeB306 may represent a base station of a public network, which may be 4G, 5G, or 6G.

[0106] Figures 11A to 11C show sequence flow diagrams 1100A, 1100B, and 1100C illustrating how to address various issues in a wide-area mobile situation according to embodiments of this disclosure.

[0107] In a wide-area travel scenario, the following sequence flow is executed. First, UE312 is latched to RANNodeB1310-1 associated with gateway 308. Next, gateway 308 is registered with 6GCN. Then, radio access functionality is indicated from gateway 308 to UE312. This functionality includes whether gateway 308 is registered with 6GCN304 or another CN304, the associated RAN type, bandwidth, spectrum, bandwidth, offset, etc. Subsequently, UE312 generates a measurement report (MR) indicating gNodeB 306. Next, a handover request is sent from RANNodeB1310-1 to gNodeB306 via gateway 308 and 6GCN304. Then, gNodeB306 accepts the handover request, and the context of UE312 is saved in gNodeB306 and 6GCN304, respectively, at each step. When RANNodeB310-1 receives a response, it initiates a handover, and UE312 moves to gNodeB306 and continues the measurement. Subsequently, UE312 again sends an MR indicating RANNodeB310 as a stronger cell. Next, the handover request is acknowledged by RANNodeB310-1, and the acknowledged handover request is sent from RANNodeB310 to gNodeB306 via gateway 308 and 6GCN304. Then, gNodeB 306 initiates a handover to UE312 to move to RANNodeB1310-1. (As described in the sequence flow above) during the above steps, the context is stored in gateway 308 and 6GCN304. Next, when it becomes necessary to send a DL message to UE312, both 6GCN304 and gateway 308 may have means to send paging to the appropriate base station (i.e., RANNodeB 310 and gNodeB 306) to successfully reach UE312. Finally, in order for 6GCN to know which gateway it needs to contact to connect to a particular UE, it is maintained that the UE_ID in this case must always be associated with the gateway ID (GW_ID).

[0108] In one embodiment, a schema for UE_ID is provided. In such a case, the UE_ID needs to be associated with the GW_ID, particularly when messages are exchanged between gateway 308 and 6GCN304. Thus, such a UE_ID is defined as follows:

number

[0109] Gateway 308 adds a GW_ID when communicating with 6GCN304 and sends it to 6GCN304. This is used by 6GCN304 (after decryption) to communicate with Gateway 308 associated with the GW_ID. Gateway 308 then removes this GW_ID and uses the remainder of the UE_ID to communicate with the corresponding UE312.

[0110] Wireless access function scheme

number

[0111] Figure 12 shows a sequence flow of method 1200, which demonstrates the operation performed by system 308, which functions as a hub in a cellular network architecture according to an embodiment of the present disclosure. With respect to Figure 12, system 308 may, in step 1202, determine a unique UE context for UE 312 for each of the first and second coverage states of UE 312. In step 1204, system 308 may dynamically store the determined unique UE context of UE 308. System 308 may then send a paging message to CN 304. The unique UE context may, in step 1206, be stored in CN 304, which provides seamless mobility services to UE 308.

[0112] Regarding the proposed cellular network architecture, for paging-related information, when the gateway is located between the RAN and CN, the context and location information of the UE is known to both the 6GCN and the gateway each time it moves between multiple cells. Therefore, during such movement, paging is successful only after updates have been successfully performed at different levels for the UE context of a particular UE.

[0113] Figure 13 shows an exemplary computer system 1300 that may implement embodiments of the present disclosure.

[0114] As shown in Figure 13, the computer system 1300 may include an external storage device 1310, a bus 1320, a main memory device 1330, a read-only storage device 1340, a mass storage device 1350, a communication port 1360, and a processor 1370. Those skilled in the art will understand that the computer system 1300 may have multiple processors and communication ports. The processor 1370 may have various modules relevant to embodiments of the present disclosure. The (one or more) communication ports 1360 may be an RS-232 port for modem-based dial-up connections, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or optical fiber, a serial port, a parallel port, or any other existing or future port. The (one or more) communication ports 1360 may be selected depending on the network to which the computer system 1300 is connected, such as a local area network (LAN), a wide area network (WAN), or any network to which the computer system 1300 is connected.

[0115] The main memory 1330 may be random access memory (RAM) or other dynamic memory commonly known in the art. The read-only memory (ROM) 1340 may be, but is not limited to, one or more static memory devices, such as a programmable read-only memory (PROM) chip for storing static information, such as startup or basic input / output system (BIOS) instructions for the processor 1370. The mass storage device 1350 may be, but is not limited to, current or future mass storage solutions that can be used to store information and / or instructions. An exemplary mass storage device 1350 includes, but is not limited to, parallel advanced technology attachment (PATA) or serial advanced technology attachment (SATA) hard disk drives, solid-state drives (internal or external, e.g., having a universal serial bus (USB) and / or FireWire interface), one or more optical disks, and redundant independent disk array (RAID) storage, e.g., disk arrays.

[0116] Bus 1320 connects the processor 1370 to other memory, storage, and communication blocks so that it can communicate with them. Bus 1320 may be a Peripheral Component Interconnect (PCI) / PCI Expansion (PCI-X) bus, a Small Computer System Interface (SCSI), a Universal Serial Bus (USB), etc., which connects other buses such as the Floant Side Bus (FSB) that connects expansion cards, drives, other subsystems, and the processor 1370 to the computer system 1300.

[0117] Optionally, operator interfaces and management interfaces (e.g., displays, keyboards, joysticks, and cursor control devices) may be connected to bus 1320 to support direct operator interaction with the computer system 1300. Other operator interfaces and management interfaces may be provided through network connections connected via one or more communication ports 1360. The components described above are merely illustrative examples illustrating various possibilities. The exemplary computer system 1300 described above does not limit the scope of this disclosure in any way.

[0118] The above describes various embodiments of the present invention, but other embodiments and alternative embodiments of the present invention may be conceived without departing from the basic scope. The scope of the present invention is determined by the following claims. The present invention is not limited to the embodiments, versions, or examples described, which are included to enable those skilled in the art to manufacture and use the present invention in combination with information and knowledge available to those skilled in the art.

[0119] Benefits of this disclosure This disclosure provides a network architecture having a gateway that functions as a private access connection hub for connecting to one or more core networks (CNs).

[0120] This disclosure enables third parties to deploy gateways by connecting one or more CNs to a Radio Access Network (RAN) node.

[0121] This disclosure provides a gateway-assisted cellular network architecture. In mobile situations, paging is successful only after updates to user devices (UEs) have been successfully performed at different levels.

[0122] This disclosure enables any entity other than RAN service providers and CN service providers to offer gateways as a service.

[0123] This disclosure enhances communication systems.

[0124] This disclosure enables the dynamic management of network requirements using a gateway-assisted network.

[0125] This disclosure facilitates network upgrades to support 6G communication technology.

[0126] This disclosure aims to optimize network infrastructure costs.

[0127] This disclosure enhances data security.

[0128] This disclosure enables the dynamic allocation of network infrastructure based on user-defined requirements.

[0129] This disclosure facilitates the provision of on-demand communication infrastructure.

[0130] This disclosure facilitates improvements to aspects related to paging and tracking areas in communications.

Claims

1. System (308), One or more processors (314), When executed by one or more processors (314), Determining a unique UE context for the user equipment (UE) (312) for each of the first coverage range state and the second coverage range state of the UE (312), Dynamically save the unique UE context of the determined UE (312), Sending a paging message to the core network (CN) (304), wherein the unique UE context is stored in the CN (304) in order to provide seamless mobility services to the UE (312), A memory (316) that stores instructions to cause the system (308) to perform the above, A system (308) equipped with the following features.

2. The system (308) according to claim 1, wherein the first coverage state corresponds to the UE (312) being within the coverage area provided by the system (308), and the second coverage state corresponds to the UE (312) being outside the coverage area provided by the system (308).

3. The system (308) according to claim 1, wherein the gateway node (308) functions as an independent hub for establishing connections between the radio access network (RAN) node (310) and the CN (304).

4. The system (308) according to claim 3, wherein the gateway node (308) designates the wireless access function of the RAN node (310) as UE (312), and the wireless access function includes information relating to at least one of the type, band, spectrum, bandwidth and offset associated with the RAN node (310).

5. The system (308) according to claim 1, wherein the gateway node (308) includes at least one of a spectrum negotiation function, a payment function, a paging and tracking function, and a security maintenance function.

6. The system (308) according to claim 1, wherein the gateway node (308) and the CN (304) each send paging messages to the network node (310) and the core network node (306) when it is time to deliver a download (DL) message from the CN (304) to the UE (312).

7. The system (308) according to claim 6, wherein the paging message is transmitted when the handover between the network node (310) and the core network node (306) via the gateway node (308) is completed.

8. In the system (308), a unique UE context of the user equipment (UE) (312) is determined for each of the first coverage range state of the UE (312) and the second coverage range state of the UE (312) (1202), In the system (308), the unique UE context of the determined UE (312) is dynamically saved (1204), In the system (308), a paging message is sent to the core network (CN) (304), wherein the unique UE context is stored in the CN (304) in order to provide seamless mobility services to the UE (312) (1206), A method comprising (1200).

9. The method according to claim 8 (1200), wherein the first coverage state corresponds to the UE (312) being within the coverage area provided by the system (308), and the second coverage state corresponds to the UE (312) being outside the coverage area provided by the system (308).

10. User equipment (UE) (312), One or more processors, It is executed by one or more of the aforementioned processors. Determining a unique UE context for each of the first coverage state and the second coverage state of the UE(312), Dynamically save the unique UE context of the determined UE (312), Sending a paging message to the core network (CN) (304), wherein the unique UE context is stored in the CN (304) in order to provide seamless mobility services to the UE (312), A memory (316) that stores instructions to cause the system to perform the following actions, UE (312) equipped with

11. Determining a unique UE context for the user equipment (UE) (312) for each of the first coverage range state and the second coverage range state of the UE (312), Dynamically save the unique UE context of the determined UE (312), Sending a paging message to the core network (CN) (304), wherein the unique UE context is stored in the CN (304) in order to provide seamless mobility services to the UE (312), A non-temporary, computer-readable medium containing instructions that cause a processor to perform a certain action.

Images