Patent Application
20240187843
The present disclosure is generally related to wireless networks and is more particularly related to handling wireless devices with reduced capabilities in such networks.
The current fifth-generation (5G) radio access network (RAN) architecture is described in the specification document 3GPP TS 38.401, as developed by members of the 3rd-Generation Partnership Project (3GPP). A simplified illustration of the architecture of the 5G RAN or “NG-RAN,” often referred to as “NR,” and its relationship to the 5G core network (5GC) is provided in
The NG architecture can be further described as follows. The NG-RAN 100 consists of a set of eNBs (LTE terminology for a base station) and gNBs (NR terminology for a base station) connected to the 5GC through the NG interface. An eNB/gNB can support Frequency Division Duplexing (FDD) mode, Time-Division Duplexing (TDD) mode, or dual-mode operation.
eNB/gNBs 110 can be interconnected to one another through the Xn interface. Some gNBs 110 may have a distributed architecture, in which case the gNB 110 has a single gNB-CU (central unit) 115 and one or several gNB-DUs (distributed units) 120, any or all of which may be physically separated from the gNB-CU 115. A gNB-CU 115 communicates with its DUs 120 through the F1 interface. Note that any given DU 120 is connected to one and only one gNB-CU 115, but a CU 115 may be connected to multiple DUs 120.
NG, Xn and F1 are logical interfaces, specified in detail in the 3GPP standards. For NG-RAN, the NG and Xn-C interfaces for a gNB 110 consisting of a gNB-CU 115 and gNB-DUs 120, terminate in the gNB-CU 115. The gNB-CU 115 and connected gNB-DUs 120 are only visible to other gNBs 110 and the 5GC 130 as a gNB 110.
The NG-RAN 100 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified in 3GPP documentation. The TNL provides services for user plane transport and signaling transport.
3GPP members have participated in a study of how to support so-called reduced capability wireless devices, referred to as “RedCap” devices, in accordance with a defined Study Item called “Study on support of reduced capability NR devices (FS_NR_redcap).” This study item includes an objective, in 3GPP document 3GPP TR 38.875, on how to ensure RedCap UEs are only used for intended use cases, that is, how to ensure that a UE identifying as a RedCap UE can only use services and resources intended for a RedCap UE type.
To support the objective of constraining/differentiating RedCap UE service access, as mentioned in the options listed in the 3gpp TR 38.875 extract above, some network enhancements need to be introduced. In fact, the means of how a NG-RAN node can link the UE being a RedCap UE for the supported bands to an indication to the Access and Mobility Management Function (AMF) signalled over NG-AP is not detailed. Also, the potential purposes and benefits for which this indication could be used by the network (both RAN and CN) are not clear.
Various techniques for addressing these problems are described herein. Introduced are several methods for enabling core network (CN) awareness of RedCap UE type. Being aware of the UE RedCap type, the CN can enable possible constraining/differentiating of RedCap devices, in the event that such constraining or differentiating is required by the operator.
One example method, in a core network node in a wireless communication network having a radio access network and a core network, comprises the step of receiving, for a wireless device operating in the radio access network, an indication that the wireless device is a reduced capability device. This example method further comprises controlling access to core network services by the wireless device and/or controlling session management for the wireless device, based on the indication.
Another example method, also implemented in a core network node in a wireless communication network having a radio access network and a core network, where the core network node comprises an Access and Mobility Management Function (AMF), also comprises the step of receiving, for a wireless device operating in the radio access network, an indication that the wireless device is a reduced capability device. This example method further comprises the step of including the indication that the wireless device is a reduced capability device in either a handover request to a target node for handover of the wireless device or a path switch request to a target node for handover of the wireless device.
Benefits of various embodiments of the techniques detailed below include that they provide flexibility to the network to allow for RedCap capability awareness via multiple signalling options, depending on the requirements. The techniques also provide option to CN for RedCap UE service customization. Other techniques, including methods and procedures carried out by wireless devices and radio access network nodes are described in detail below, as are corresponding apparatuses and systems.
Exemplary embodiments of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment can be tacitly assumed to be present/used in another embodiment. Any two or more embodiments described in this document may be combined with each other.
Various aspects of the techniques and apparatuses may be described with respect to specific messages or specifications of the NR radio access network (RAN) and the 5G core network (5GCN or 5GC). This is done for purposes of explanation, and it should be understood that the described principles and techniques may be advantageously applied to other wireless networks. References to specific named functions and nodes in the NR RAN and 5GC, such as gNB, AMF, SMF, PCF, etc., should be understood to refer to those nodes and functions as specified by 3GPP specifications and as further modified as necessary to carry out the techniques described herein, as well as to their equivalents in other networks and improvements or successors to the 5G wireless networks specified by 3GPP.
In this document, the terms “UE” and “wireless device” are used interchangeably. While “user equipment” or “UE” refers specifically to a device as specified by 3GPP standards, the terms UE and wireless device as used herein should be understood to encompass any wireless access device or end user device, i.e., a device that access a radio network for services. Furthermore, in this document the term “node” or “network node” is used to refer to an apparatus configured to carry out certain functionality discussed herein. The present discussion refers to several “functions” as defined by 3GPP specifications—any one of those functions may be instantiated in a node, alone or with other functions (including other instantiations of the same function), and in some cases a given function may be distributed among several physically distinct hardware units. Thus, the term “node,” while referring to physical structure, may refer to a single discrete hardware unit or a collection of connected hardware units operating together to provide a certain functionality.
As briefly discussed above, 3GPP is developing specifications for support of so-called reduced capability, or “RedCap” devices in 5G networks. By reduced capability device, or RedCAP UE, is meant that the wireless device has reduced capabilities, compared to devices designed for mobile broadband use, with respect to two or more of: supported bandwidth, maximum number of MIMO layers supported, and maximum downlink modulation order supported. It will be appreciated that all of these reduce baseband and other hardware complexity, enabling smaller and less expensive devices.
As noted above, 3GPP members have participated in a study of how to support so-called reduced capability wireless devices, referred to as “RedCap” devices, in accordance with a defined Study Item called “Study on support of reduced capability NR devices (FS_NR_redcap).” This study item includes an objective, in 3GPP document 3GPP TR 38.875, on how to ensure RedCap UEs are only used for intended use cases, that is, how to ensure that a UE identifying as a RedCap UE can only use services and resources intended for a RedCap UE type.
The following potential solutions can be considered (the solutions do not need to be mutually exclusive), as outlined in 3GPP TR 38.875:
Discussed below are several different signaling support options for enabling CN awareness of RedCap UE capability. Techniques for service control and differentiation in CN for RedCap UEs are also described.
Signalling support from the radio access network (RAN) may be grouped into two main options:
Awareness of the RedCap UE capability enables several functions in the CN. In particular, the CN, e.g., the Access Mobility Function (AMF), may use this indication for constraining RedCap devices with respect to, for example, access restriction control based on subscription data or local policy, paging optimization, slice selection in different NFs of the Core Network and for applying different charging policy, as necessary.
A first approach for providing a RedCap indication to the CN is briefly described below.
This first approach, from the UE or wireless device perspective, comprises the following steps:
This first approach from radio access network (RAN) node (e.g., gNB) perspective:
This first approach from the CN network node (e.g., AMF) perspective:
The AMF may also expose the inform to NEF and NWDAF for other smart usage.
A second approach for providing a RedCap indication to the CN is briefly described below. This may be viewed as involving “implicit” signaling, as the UE Redcap indication is deduced by the RAN node from other signaling.
The second approach, from UE perspective:
The second approach from RAN node (e.g., gNB) perspective:
The second approach from CN node (e.g., AMF) perspective:
A third approach for providing a RedCap indication to the CN is briefly described below.
Basic steps of the third approach, from UE perspective:
Basic steps of the third approach from RAN node (e.g., gNB) perspective:
Basic steps of the invention from network node 2 (i.e., AMF) perspective:
A mix of the above options might also be used.
Following is a detailed description of the signaling for the above-summarized approaches.
For the first approach, what follows is a non-limiting example of enhancing the existing 3GPP specifications for Radio Resource Control (RRC) and NG-AP signalling messages to cover the techniques described above, with new changes in bold.
NG-AP signalling (Initial UE message) The following is an example of the signaling described above for the second approach, step 213:
Following is a non-limiting example of enhancing the existing RRC signalling message to cover the second and third approaches summarized above, with new changes in blue highlight for the second approach.
The following is a signaling example of step 340 from the first approach described above.
In some embodiments of the presently disclosed techniques, the RedCap indication, i.e., an indication that the wireless device is a reduced capabilities device, may be included in the UE registration procedure. Below is a modified version of the UE registration procedure from 3GPP TS 23.502, with changes related to the receiving and use of the RedCap indication:
In some embodiments of the presently disclosed techniques, the RedCap indication, i.e., an indication that the wireless device is a reduced capabilities device, may be used in the UE Packet Data Unit (PDU) session establishment procedure. Below is a modified version of the PDU session establishment procedure from 3GPP TS 23.502, with changes related to the receiving and use of the RedCap indication:
In the proposed specification above, the description of step 2 of the illustrated flow references 3GPP TS 23.501 clause 6.3.2. A modified version of that clause, to support the techniques described herein, is provided below:
According to some embodiments of the presently disclosed techniques, the Access and Mobility Management Function (AMF) in the 5GCN uses the RedCap indication in establishing an Access and Mobility (AM) policy, with the Policy and Control Function (PCF). Below is a description of the 3GPP AM policy establishment procedure, as modified to take into account the RedCap indication:
In view of the several techniques and variants described above, any combinations of which may be used together, in some embodiments, it will be appreciated that
As shown at block 32, the illustrated method comprises the step of receiving, for a wireless device operating in the radio access network, an indication that the wireless device is a reduced capability device. As shown at block 34, the method further comprises controlling access to core network services by the wireless device and/or controlling session management for the wireless device, based on the indication.
In some embodiments, the core network node comprises an AMF, and the core network node/AM treats the indication that the wireless device is a reduced capability device as a Radio Access Technology (RAT) type, for purposes of making access control and session management decisions based on RAT type. In some embodiments, the core network node selects a Session Management Function (SMF) based on the indication that the wireless device is a reduced capability device.
In some of these and in some other embodiments, where the core network node comprises an AMF, the method may also comprise including the indication that the wireless device is a reduced capability device in a handover request to a target node for handover of the wireless device. This is shown generally at block 36 of
In some embodiments, the core network node comprises at least one of a Policy Control Function (PCF), Session Management Function (SMF), and User Plane Function (UPF), and the core network node treats the indication that the wireless device is a reduced capability device as a Radio Access Technology, RAT, type, for differentiating the wireless device for charging and/or quality-of-service.
In a variation of the method shown in
When configured as a RAN node, network node 30 may be an evolved Node B (eNodeB), Node B or gNB, for example. While a radio network node 30 is shown in
When configured as a RAN node, network node 30 facilitates communication between wireless terminals (e.g., UEs), other network access nodes and/or the core network. Whether configured as a RAN node or a CN node, network node 30 may include communication interface circuitry 38 that includes circuitry for communicating with other nodes in the core network, radio nodes, and/or other types of nodes in the network for the purposes of providing data and/or cellular communication services. Some embodiments of network node 30 communicate with wireless devices using antennas 34 and transceiver circuitry 36. Some of these and some other embodiments may communicate with one or more relay nodes using antennas 34 and transceiver circuitry 36, e.g., using antennas 34 and transceiver circuitry 36 to communicate with an MT part of a relay node. Transceiver circuitry 36 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of providing cellular communication services.
Network node 30 also includes one or more processing circuits 32 that are operatively associated with the transceiver circuitry 36 and, in some cases, the communication interface circuitry 38. Processing circuitry 32 comprises one or more digital processors 42, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), Application Specific Integrated Circuits (ASICs), or any mix thereof. More generally, processing circuitry 32 may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein, or some mix of fixed and programmed circuitry. Processor 42 may be multi-core, i.e., having two or more processor cores utilized for enhanced performance, reduced power consumption, and more efficient simultaneous processing of multiple tasks.
Processing circuitry 32 also includes a memory 44. Memory 44, in some embodiments, stores one or more computer programs 46 and, optionally, configuration data 48. Memory 44 provides non-transitory storage for the computer program 46 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. Here, “non-transitory” means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory, e.g., for program execution. By way of non-limiting example, memory 44 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 32 and/or separate from processing circuitry 32. Memory 44 may also store any configuration data 48 used by the network access node 30. Processing circuitry 32 may be configured, e.g., through the use of appropriate program code stored in memory 44, to carry out one or more of the methods and/or signaling processes detailed herein.
Processing circuitry 32 of the network node 30 is configured, according to some embodiments, to perform all or part of the techniques described herein for one or more network nodes of a wireless communication system, including, for example, the methods described in connection with
UE 50 is configured to communicate with a network node or base station in a wide-area cellular network via antennas 54 and transceiver circuitry 56. Transceiver circuitry 56 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to multiple radio access technologies, for the purposes of using cellular communication services. The radio access technologies can be NR and LTE for the purposes of this discussion.
UE 50 also includes one or more processing circuits 52 that are operatively associated with the radio transceiver circuitry 56. Processing circuitry 52 comprises one or more digital processing circuits, e.g., one or more microprocessors, microcontrollers, DSPs, FPGAs, CPLDs, ASICs, or any mix thereof. More generally, processing circuitry 52 may comprise fixed circuitry, or programmable circuitry that is specially adapted via the execution of program instructions implementing the functionality taught herein or may comprise some mix of fixed and programmed circuitry. Processing circuitry 52 may be multi-core.
Processing circuitry 52 also includes a memory 64. Memory 64, in some embodiments, stores one or more computer programs 66 and, optionally, configuration data 68. Memory 64 provides non-transitory storage for computer program 66 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. By way of non-limiting example, memory 64 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 52 and/or separate from processing circuitry 52. Memory 64 may also store any configuration data 68 used by UE 50. Processing circuitry 52 may be configured, e.g., through the use of appropriate program code stored in memory 64, to carry out one or more of the methods and/or signaling processes discussed above.
Processing circuitry 52 of the UE 50 is configured, according to some embodiments, to perform any methods that support or correspond with the techniques described herein for the network nodes or base station.
While the techniques described above relate to access control and session and policy management of RedCap devices, and thus do not apply directly to the handling of user data, such as application data transferred to and from an applications server in a data network, it will be appreciated that the presently disclosed techniques may be implemented to improve the speed and efficiency of system access by a wireless device, and thus will indirectly improve the operation and efficiency of the wireless device's operation with respect to user-driven applications, whether those applications are voice, video, or data-based applications or services.
The telecommunication network 610 is itself connected to a host computer 630, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 630 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. The connections 621, 622 between the telecommunication network 610 and the host computer 630 may extend directly from the core network 614 to the host computer 630 or may go via an optional intermediate network 620. The intermediate network 620 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 620, if any, may be a backbone network or the Internet; in particular, the intermediate network 620 may comprise two or more sub-networks (not shown).
The communication system of
Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to
In communication system 700, a host computer 710 comprises hardware 715 including a communication interface 716 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 700. The host computer 710 further comprises processing circuitry 718, which may have storage and/or processing capabilities. In particular, the processing circuitry 718 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 710 further comprises software 711, which is stored in or accessible by the host computer 710 and executable by the processing circuitry 718. The software 711 includes a host application 712. The host application 712 may be operable to provide a service to a remote user, such as a UE 730 connecting via an OTT connection 750 terminating at the UE 730 and the host computer 710. In providing the service to the remote user, the host application 712 may provide user data which is transmitted using the OTT connection 750.
The communication system 700 further includes a base station 720 provided in a telecommunication system and comprising hardware 725 enabling it to communicate with the host computer 710 and with the UE 730. The hardware 725 may include a communication interface 726 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 700, as well as a radio interface 727 for setting up and maintaining at least a wireless connection 770 with a UE 730 located in a coverage area (not shown in
The communication system 700 further includes the UE 730 already referred to. Its hardware 735 may include a radio interface 737 configured to set up and maintain a wireless connection 770 with a base station serving a coverage area in which the UE 730 is currently located. The hardware 735 of the UE 730 further includes processing circuitry 738, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 730 further comprises software 731, which is stored in or accessible by the UE 730 and executable by the processing circuitry 738. The software 731 includes a client application 732. The client application 732 may be operable to provide a service to a human or non-human user via the UE 730, with the support of the host computer 710. In the host computer 710, an executing host application 712 may communicate with the executing client application 732 via the OTT connection 750 terminating at the UE 730 and the host computer 717. In providing the service to the user, the client application 732 may receive request data from the host application 712 and provide user data in response to the request data. The OTT connection 750 may transfer both the request data and the user data. The client application 732 may interact with the user to generate the user data that it provides.
It is noted that the host computer 710, base station 720 and UE 730 illustrated in
In
The wireless connection 770 between the UE 730 and the base station 720 is in accordance with the teachings of the embodiments described throughout this disclosure, such as provided by nodes such as UE 50 and network node 30, along with the corresponding method illustrated in
A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 750 between the host computer 710 and UE 730, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 750 may be implemented in the software 711 of the host computer 710 or in the software 731 of the UE 730, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 750 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 711, 731 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 720, and it may be unknown or imperceptible to the base station 720. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer's 710 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 711, 731 causes messages to be transmitted, in particular, empty or ‘dummy’ messages, using the OTT connection 750 while it monitors propagation times, errors etc.
The communication system includes a host computer, a base station and a UE which may be those described with reference to
The communication system includes a host computer, a base station and a UE which may be those described with reference to
The communication system includes a host computer, a base station and a UE which may be those described with reference to
The communication system includes a host computer, a base station and a UE which may be those described with reference to
As discussed in detail above, the techniques described herein, e.g., as illustrated in the process flow diagram of
In view of the detailed examples and description above, it will be appreciated that embodiments of the presently disclosed inventive techniques and apparatuses may include, but are not necessarily limited to, the following enumerated examples:
Example 1. A method, in a core network node in a wireless communication network having a radio access network and a core network, the method comprising: receiving, for a wireless device operating in the radio access network, an indication that the wireless device is a reduced capability device; and controlling access to core network services by the wireless device and/or controlling session management for the wireless device, based on the indication.
Example 2. The method of example 1, wherein the core network node selects a Session Management Function, SMF, based on the indication that the wireless device is a reduced capability device.
Example 3. The method of example 1 or 2, wherein the core network node comprises an Access and Mobility Management Function, AMF, and wherein the core network node treats the indication that the wireless device is a reduced capability device as a Radio Access Technology, RAT, type, for purposes of making access control and session management decisions based on RAT type.
Example 4. The method of any of examples 1-3, wherein the core network node comprises an Access Mobility Function, AMF, and wherein the method comprises including the indication that the wireless device is a reduced capability device in a handover request to a target node for handover of the wireless device.
Example 5. The method of any of examples 1-3, wherein the core network node comprises an Access and Mobility Management Function, AMF, and wherein the method comprises including the indication that the wireless device is a reduced capability device in a path switch request to a target node for handover of the wireless device.
Example 6. The method of example 1, wherein the core network node comprises at least one of a Policy Control Function, PCF, Session Management Function, SMF, and User Plane Function (UPF), and wherein the core network node treats the indication that the wireless device is a reduced capability device as a Radio Access Technology, RAT, type, for differentiating the wireless device for charging and/or quality-of-service.
Example 7. A method, in a core network node in a wireless communication network having a radio access network and a core network, wherein the core network node comprises an Access and Mobility Management Function, AMF, the method comprising: receiving, for a wireless device operating in the radio access network, an indication that the wireless device is a reduced capability device; and including the indication that the wireless device is a reduced capability device in either a handover request to a target node for handover of the wireless device or a path switch request to a target node for handover of the wireless device.
Example 8. A core network node adapted to carry out a method according to any one of examples 1-7.
Example 9. A core network node, comprising: communications interface circuitry; and processing circuitry operatively associated with the communications interface circuitry and configured to: receive, for a wireless device operating in the radio access network, an indication that the wireless device is a reduced capability device; and control access to core network services by the wireless device and/or controlling session management for the wireless device, based on the indication.
Example 10. The core network node of example 9, wherein the core network node comprises an Access and Mobility Management Function, AMF, and wherein the processing circuitry is configured to treat the indication that the wireless device is a reduced capability device as a Radio Access Technology, RAT, type, for purposes of making access control and session management decisions based on RAT type.
Example 11. The core network node of any of examples 9-10, wherein the processing circuitry is configured to select a Session Management Function, SMF, based on the indication that the wireless device is a reduced capability device.
Example 12. The core network node of any of examples 9-11, wherein the core network node comprises an Access Mobility Function, AMF, and wherein the processing circuitry is configured to include the indication that the wireless device is a reduced capability device in a handover request to a target node for handover of the wireless device.
Example 13. The core network node of any of examples 9-11, wherein the core network node comprises an Access and Mobility Management Function, AMF, and wherein the processing circuitry is configured to include the indication that the wireless device is a reduced capability device in a path switch request to a target node for handover of the wireless device.
Example 14. The core network node of example 9, wherein the core network node comprises at least one of a Policy Control Function, PCF, Session Management Function, SMF, and User Plane Function (UPF), and wherein the processing circuitry is configured to treat the indication that the wireless device is a reduced capability device as a Radio Access Technology, RAT, type, for differentiating the wireless device for charging and/or quality-of-service.
Example 15. A core network node, comprising: communications interface circuitry; and processing circuitry operatively associated with the communications interface circuitry and configured to: receive, for a wireless device operating in the radio access network, an indication that the wireless device is a reduced capability device; and include the indication that the wireless device is a reduced capability device in either a handover request to a target node for handover of the wireless device or a path switch request to a target node for handover of the wireless device.
Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts is to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents and shall not be restricted or limited by the foregoing detailed description.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2022/058719 | 3/31/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63170124 | Apr 2021 | US |
