System and method for providing multipath access in a wireless network

Abstract

The present disclosure provides a system (108) and a method for providing multi-path access in a wireless network. The system (108) receives a request from a user equipment (UE) (104) for accessing a plurality of radio paths through single cell access of a Radio Access Network (RAN) node (110). The system (108) establishes a plurality of UE contexts based on a Radio Resource Control (RRC) connection between the UE (104) and the RAN node (110) for accessing the plurality of radio paths through the RAN node (110). The system (108) enables the UE (104) to support a plurality of Protocol Data Unit (PDU) sessions associated with a core network (112) through the plurality of radio paths based on the plurality of UE contexts. The system (108) facilitates data exchange between the UE (104) and the core network (112) through the plurality of radio paths.

Description

SYSTEM AND METHOD FOR PROVIDING MULTIPATH ACCESS IN A WIRELESS NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.FIELD OF INVENTION

[0002] The embodiments of the present disclosure relate to a field of wireless networks. More particularly, the present disclosure relates to a system and a method for providing multipath access in a wireless network.BACKGROUND

[0003] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0004] Today cellular networks support parallelism at the radio level and at the Internet Protocol (IP) level independent of each other i.e. at the radio level a single user equipment (UE) can have two parallel physical paths from the UE to the base station (Carrier aggregation) and at the IP level again a UE can be supported with multihoming techniques which means at the IP level there will be two separate paths to a UE but that is multiplexed into a single physical path. Existing cellular networks do not support multiple parallel separate connections for a single UE. Carrier aggregation is a temporary phenomenon that is triggered by a user buffer status and the availability of another overlapping cell and in a different frequency or on the same frequency. Carrier aggregation does not provide parallel paths because at the core network, data from the UE is identified through a single stream.Further, in multihoming scenarios, the availability of multiple Radio Access Technologies (RATs) implemented and IP addresses are provided per RAT so that some parallelism can be achieved. But, this requires two or more RATs to be available at the same time in the same premises which may not be a valid scenario for an enterprise, manufacturing floor, and other possible secure locations. However, multiple requirements are being defined for sixth generation (6G) wireless networks, as the device form factors for 6G vary from a conventional phone form factor.

[0005] There is, therefore, a need in the art to provide a system and a method that can mitigate the problems associated with conventional systems.OBJECTS OF THE INVENTION

[0006] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are listed herein below.

[0007] It is an object of the present disclosure to provide a system and a method for providing multipath access associated with Protocol Data Units (PDUs) in a wireless network. User equipments (UEs) support multiple radios for a single registered cell in a Radio Access Network (RAN) node, and the associated core network provides multiple paths of communication for the single registered cell in the RAN.

[0008] It is an object of the present disclosure to provide a system where the UE requesting parallel connections to support multiple parallel radio paths on a single registered cell / RAN node is supported through the core network. The core network provides multiple paths of communication for the single registered cell in the RAN.

[0009] It is an object of the present disclosure to provide a system where the core network identifies multiple connection requests from the same UE through the system and the core network provides resources, connections, quality of service (QoS), and security associated with the multiple connection requests.

[0010] It is an object of the present disclosure to provide a system where UEs having multi-path support receive scheduling opportunities through the system, and where each path receives separate opportunity from the scheduler.

[0011] It is an object of the present disclosure where the system establishes multiple UE contexts based on a Radio Resource Control (RRC) connection between the UE and the RAN node for accessing the multiple radio paths through the RAN node.

[0012] It is an object of the present disclosure where the system enables the UE to support multiple Protocol Data Unit (PDU) sessions associated with the core network through the multiple radio paths based on the established UE contexts.

[0013] It is an object of the present disclosure where the system facilitates data exchange between the UEs and the core network through the multiple radio paths.SUMMARY

[0014] This section is provided to introduce certain objects and aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0015] In an aspect, the present disclosure relates to a system for providing multi-path access in wireless network. The system includes a processor communicatively coupled to a Radio Access Network (RAN) node and a memory operatively coupled with the processor. The memory stores instructions which, when executed by the processor, cause the processor to receive a request from a user equipment (UE) for accessing a plurality of radio paths through single cell access of the RAN node upon the registration of the UE with the RAN node. The processor establishes a plurality of UE contexts based on a Radio Resource Control (RRC) connection between the UE and the RAN node for accessing the plurality of radio paths through the RAN node. The processor enables the UE to support a plurality of Protocol Data Unit (PDU) sessions associated with a core network through the plurality of radio paths based on the plurality of UE contexts. The processor facilitates data exchange between the UE and the core network through the plurality of radio paths.

[0016] In an embodiment, the processor may enable allocation of one or more radio resources to the UE based on the plurality of UE contexts by providing one or more scheduling opportunities per Transmission Time Interval (TTI).

[0017] In an embodiment, upon enablement of the UE to support the plurality of PDU sessions through the plurality of radio paths, the processor may facilitate transfer of application data between the UE and a Data Network Name (DNN) of the core network.

[0018] In an embodiment, the UE may transmit one or more information elements (IES) associated with the request to the core network through the processor and request the establishment of the plurality of radio paths for each of the plurality of PDU sessions, and the processor may enable the UE to support the plurality of PDU sessions based on an N2 message from the core network.

[0019] In an embodiment, the processor may allocate a particular Internet (IP) address associated with the request from the UE. The processor may transmit the request to the core network for enabling the UE to support the plurality of PDU sessions upon receiving one or more approval messages from the core network.

[0020] In an embodiment, upon receiving the one or more approval messages from the core network, the processor may enable the data exchange between the UE and the core network through the plurality of radio paths.

[0021] In an aspect, the present disclosure relates to a method for providing multipath access in a wireless network. The method includes receiving, by a processor associated with a system, a request from a UE for accessing a plurality of radio paths through single cell access of a RAN node upon the registration of the UE with the RAN node. The method includes establishing, by the processor, a plurality of UE contexts based on a RRC connection between the UE and the RAN node for accessing the plurality of radio paths through the RAN node. The method includes enabling, by the processor, the UE to support a plurality of PDU sessions associated with a core network through the plurality of radio paths based on the plurality of UE contexts. The method includes facilitating, by the processor, data exchange between the UE and the core network through the plurality of radio paths.

[0022] In an embodiment, the method may include enabling, by the processor, allocation of one or more radio resources to the UE based on the plurality of UE contexts by providing one or more scheduling opportunities per TTI.

[0023] In an embodiment, the method may include allocating, by the processor, an IP address associated with the request from the UE and transmitting the request to the core network for enabling the UE to support the plurality of PDU sessions upon receiving one or more approval messages from the core network.

[0024] In an embodiment, the method may include enabling, by the processor, upon receiving the one or more approval messages from the core network, the data exchange between the UE and the core network through the plurality of radio paths.

[0025] In an aspect, the present disclosure relates to a UE for sending requests. The UE includes one or more processors communicatively coupled to a processor associated with a system. The one or more processors are coupled with a memory, and where said memory stores instructions which, when executed by the one or more processors, cause the one or more processors to transmit a request to the processor for accessing a plurality of radio paths through single cell access of a RAN node upon registration of the UE with the RAN node. The processor is configured to establish a plurality of UE contexts based on a RRCconnection between the UE and the RAN node for accessing the plurality of radio paths through the RAN node. The processor is configured to enable the UE to support the plurality of PDU sessions associated with the core network through the plurality of radio paths based on the plurality of UE contexts. The processor is configured to facilitate data exchange between the UE and the core network through the plurality of radio paths.

[0026] In an aspect, the present disclosure relates to a non-transitory computer- readable medium comprising processor-executable instructions that cause a processor to receive a request from a UE for accessing a plurality of radio paths through single cell access of a RAN node upon registration of the UE with the RAN node, establish a plurality of UE contexts based on a RRC connection between the UE and the RAN node for accessing the plurality of radio paths through the RAN node, enable the UE to support a plurality of Protocol Data Unit (PDU) sessions associated with a core network through the plurality of radio paths based on the established plurality of UE contexts, and facilitate data exchange between the UE and the core network through the plurality of radio paths.BRIEF DESCRIPTION OF DRAWINGS

[0027] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.

[0028] FIG. 1 illustrates an example network architecture diagram (100) of the proposed system (108), in accordance with an embodiment of the present disclosure.

[0029] FIG. 2 illustrates an example block diagram (200) of a proposed system (108), in accordance with an embodiment of the present disclosure.

[0030] FIG. 3 illustrates an example conventional cellular network connection allocation (300).

[0031] FIGs. 4A-4B illustrate example instances of the Medium Access Scheduling (MAC) scheduling operation (400A, 400B) with and without multi-path support within a cell, in accordance embodiments of the present disclosure.

[0032] FIG. 5 illustrates an example transmission (500) of a Protocol Data Unit (PDU) session on separate transport blocks, in accordance with an embodiment of the present disclosure.

[0033] FIG. 6 illustrates an example flow diagram (600) of Radio Resource Control (RRC) connection with the multiple user equipment (UE) contexts, in accordance with an embodiment of the present disclosure.

[0034] FIG. 7 illustrates an example diagram (700) representing allocation of radio resources by the proposed system (108) separately for the UE contexts, in accordance with an embodiment of the present disclosure.

[0035] FIG. 8 illustrates an example diagram (800) of a single access multi-path (SAMP) scenario using a Multi-path Transport Control Protocol (MPTCP) protocol, in accordance with an embodiment of the present disclosure.

[0036] FIG. 9 illustrates an example diagram (900) of a SAMP scenario using a Multi-path Quick User Datagram Protocol (UDP) Internet Connection (MPQUIC) protocol, in accordance with an embodiment of the present disclosure.

[0037] FIG. 10 illustrates an example diagram (1000) of a SAMP scenario using an Aggregator and Disaggregator Function (AgDg) Protocol, in accordance with an embodiment of the present disclosure.

[0038] FIG. 11 illustrates an example diagram (1100) of the SAMP scenario, realized with multi-path spanning across multiple cells, in accordance with an embodiment of the present disclosure.

[0039] FIG. 12 illustrates an example flow diagram (1200) of a UE triggered service request, in accordance with an embodiment of the present disclosure.

[0040] FIG. 13 illustrates an example flow diagram (1300) of a core network triggered service request, in accordance with an embodiment of the present disclosure.

[0041] FIG. 14 illustrates an example flow diagram (1400) of mobility registration update, in accordance with an embodiment of the present disclosure.

[0042] FIG. 15 illustrates an example flow diagram (1500) of multiple paths for the SAMP PDU session through multiple IP addresses from the core network, in accordance with an embodiment of the present disclosure.

[0043] FIG. 16 illustrates an example computer system (1600) in which or with which embodiments of the present disclosure may be implemented.

[0044] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0045] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0046] The ensuing description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0047] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.

[0048] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0049] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design describedherein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0050] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0051] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0052] The present disclosure describes mechanisms to achieve parallel connection (two or more) for a given user equipment (UE) with single credentials in a cellular network on the same registered cell. Further, a mechanism of the UE requesting parallel connections is described, where the UE advertises a capability to support multiple parallel radio paths on the registered cell / Radio Access Network (RAN) node and a core network subsequently supporting multiple requested connections for the same UE credentials. The present disclosure describes independent use of multiple antenna streams with the UE where applications associated with the UE is assigned a pair of physical antennas which in turn can allocate the appropriate L2 / L3 stack parts forming dedicated connectivity paths inside the UE. The application request can be accommodated via a multi-RAN mechanism and a dualInternet Protocol (IP) address mechanism. The core network further includes a mechanism that identifies multiple connection requests from the same device / UE and enables handling of resources, multiple connections, Quality of Service (QoS), and security associated with the multiple connections. Further, for a given device / UE multiple antennas are mounted at different locations for the single device / UE and including Intracell multi-channel aggregation. The UE supports multiple radios for a given radio technology, a single cell / RAN node and the associated core network elements provides multiple parallel paths of communication for a given radio access cell / network.

[0053] Further, device form factors for sixth generation (6G) wireless networks will change. Different form factor devices will need special provisions and one such provision is the availability of (or the possibility to provision) multiple antenna sets tor a given device which can accommodate simultaneous parallel connections to a given 6G cell (not across ceils / RATs, but the same cell). To take advantage of such a scenario for fixed wireless, vehicular mounted devices, industrial devices etc., procedures and mechanisms to accommodate parallel session access in a single cell may be required.

[0054] Various embodiments of the present disclosure will be explained in detail with reference to FIGs. 1-2 and FIGs. 4-16.

[0055] FIG. 1 illustrates an example network architecture diagram (100) of the proposed system (108), in accordance with an embodiment of the present disclosure.

[0056] As illustrated in FIG. 1, the network architecture (100) may include a system (108). The system (108) may be connected to one or more computing devices (104-1, 104- 2... 104-N) via a network (106). The one or more computing devices (104-1, 104-2... 104-N) may be interchangeably specified as a user equipment (UE) (104) and be operated by one or more users (102-1, 102-2...102-N). Further, the one or more users (102-1, 102-2... 102 -N) may be interchangeably referred as a user (102) or users (102). The system (108) may be configured with a RAN node (110). Further, the RAN node (110) may be communicatively coupled to a core network (112). In some embodiments, the RAN node (110) may include a 6gNB-distribution unit and a 6NB-control unit.

[0057] In an embodiment, the computing devices (104) may include, but not be limited to, a mobile, a laptop, etc. Further, the computing devices (104) may include a smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a general-purpose computer, desktop, personal digital assistant, tablet computer, and a mainframe computer. Additionally, input devices for receiving input from the user (102) such as a touch pad, touch-enabled screen, electronic pen, and the like may be used. A person of ordinary skill inthe art will appreciate that the computing devices (104) may not be restricted to the mentioned devices and various other devices may be used.

[0058] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0059] In an embodiment, the system (108) may receive a request from the UE (104) for accessing a plurality of radio paths through single cell access of the RAN node (110) upon the registration of the UE (104) with the RAN node (110). The system (108) may enable allocation of one or more radio resources to the UE (104) based on a plurality of UE contexts by providing one or more scheduling opportunities per Transmission Time Interval (TTI). Further, the UE (104) may transmit one or more information elements (IEs) associated with the request to the core network (112) through the system (108) and request the establishment of the plurality of radio paths for each of a plurality of PDU sessions. The system (108) may enable the UE (104) to support the plurality of PDU sessions based on an N2 message from the core network (112). Upon the enablement of the UE (104) to support the plurality of PDU sessions through the plurality of radio paths, the system (108) may facilitate transfer of application data between the UE (104) and a Data Network Name (DNN) of the core network (112).

[0060] In an embodiment, the system (108) may allocate a particular Internet Protocol (IP) address associated with the request from the UE (104). The system (108) may transmit the request to the core network (112) for enabling the UE (104) to support the plurality of PDU sessions upon receiving one or more approval messages from the core network (112). Upon receiving the one or more approval messages from the core network (112), the system (108) may enable the data exchange between the UE (104) and the core network (112) through the plurality of radio paths. Further, the system (108) may transmit the one or more approval messages from the core network (112) to enable the UE (104) to transmit uplink (UL) data to the core network (112) through the plurality of UE contexts. The system (108)may transmit DL data received from the core network (112) through the plurality of UE contexts, based on the transmitted UL data by the UE (104).

[0061] In an embodiment, the system (108) may establish the plurality of UE contexts based on a Radio Resource Control (RRC) connection between the UE (104) and the RAN node (110) for accessing the plurality of radio paths through the RAN node (110).

[0062] In an embodiment, the system (108) may enable the UE (104) to support the plurality of PDU sessions associated with the core network (112) through the plurality of radio paths based on the plurality of UE contexts. Further, the system (108) may facilitate data exchange between the UE (104) and the core network (112) through the plurality of radio paths.

[0063] In an embodiment, multiple antenna streams may be configured with the UEs (104) where any application can be assigned a pair of physical antennas which in turn can allocate the appropriate L2 / L3 stack parts forming dedicated connectivity paths inside the UE (104).

[0064] FIG. 2 illustrates an example block diagram (200) of a proposed system (106), in accordance with an embodiment of the present disclosure.

[0065] Referring to FIG. 2, the system (108) may comprise one or more processor(s) (202) that may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory 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, and the like.

[0066] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output (I / O) devices, storage devices, and the like. The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, processing engine(s) (208) and a database (210), where the processing engine(s) (208) may include, but not be limited to, adata ingestion engine (212) and other engine(s) (214). In an embodiment, the other engine(s) (214) may include, but not limited to, a data management engine, an input / output engine, or the like.

[0067] In an embodiment, the processing engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (108) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine -readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.

[0068] In an embodiment, the processor (202) may receive a request through the data ingestion engine (212). The request may be received from a UE (104) for accessing a plurality of radio paths through single cell access of the RAN node upon the registration of the UE (104) with the RAN node (110). The processor (202) may store the request in the database (210). The processor (202) may enable allocation of one or more radio resources to the UE (104) based on a plurality of UE contexts by providing one or more scheduling opportunities per TTI. Further, the UE (104) may transmit one or more IES associated with the request to the core network (112) through the processor (202) and request the establishment of the plurality of radio paths for each of the plurality of PDU sessions. The processor (202) may enable the UE (104) to support the plurality of PDU sessions based on an N2 message from the core network (112). Upon the enablement of the UE (104) to support the plurality of PDU sessions through the plurality of radio paths, the processor (202) may facilitate transfer of application data between the UE (104) and a DNN of the core network (112).

[0069] In an embodiment, the processor (202) may allocate a particular IP address associated with the request from the UE (104). The processor (202) may transmit the request to the core network (112) for enabling the UE (104) to support the plurality of PDU sessionsupon receiving one or more approval messages from the core network (112). Upon receiving the one or more approval messages from the core network (112), the processor (202) may enable the data exchange between the UE (104) and the core network (112) through the plurality of radio paths. Further, the processor (202) may transmit the one or more approval messages from the core network to enable the UE (104) to transmit uplink (UL) data to the core network (112) through the plurality of UE contexts. The processor (202) may transmit DL data received from the core network (112) through the plurality of UE contexts, based on the transmitted UL data by the UE (104).

[0070] In an embodiment, the processor (202) may establish the plurality of UE contexts based on a RRC connection between the UE (104) and the RAN node (110) for accessing the plurality of radio paths through the RAN node (110).

[0071] In an embodiment, the processor (202) may enable the UE (104) to support the plurality of PDU sessions associated with the core network (112) through the plurality of radio paths based on the plurality of UE contexts. Further, the processor (202) may facilitate data exchange between the UE (104) and the core network (112) through the plurality of radio paths.

[0072] FIG. 3 illustrates an example conventional cellular network connection allocation (300).

[0073] As illustrated in FIG. 3, a UE (302) can support multiple PDU sessions (304-1, 304-N) in a cellular network. But, a physical transport layer in the RAN node (306) multiplexes the data into a single physical channel. Conventional cellular networks do not support any mechanism that enables the UE (302) to request for either a single physical transport path or multiple physical transport paths for a given set of PDU paths / PDU sessions (304-1, 304-N) from the core network (308) through the single cell on the RAN node (306). The UE (302) and the RAN node (306) may communicate using a Physical Uplink Shared Channel (PUSCH)ZPhysical Downlink Shared Channel (PDSCH) combination (314). Applications data transfer may occur between the UE (302) and a Data Network Name (DNN) (310) through an AS1 (312) server.

[0074] FIGs. 4A-4B illustrate example instances of the Medium Access Scheduling (MAC) scheduling operation (400A, 400B) with and without multi-path support within a cell, in accordance with embodiments of the present disclosure.

[0075] As illustrated in FIG. 4A, in an embodiment, a multi-path support is not provided to the UE (104). Here, every UE (104) gets mostly one opportunity in every cycle of scheduling operation per TTI. In that opportunity, the scheduler in the RAN node (110) mayallocate maximum configured radio resources per TTI per UE (104), based on the type of scheduler utilized. The allocation may vary with respect to round robin scheduling, proportional fairness scheduling, QoS aware scheduling, and hybrid forms of scheduling.

[0076] FIG. 4B illustrates the instance with multi-path support to the UEs (104). UEs (104) having multi-path support may receive more scheduling opportunities, where each path may receive separate opportunities from the scheduler. Here, UE1 (402) and UEla (404) may be two paths that receive scheduler opportunities and hence the radio resource allocation may be twice when compared to the instance in FIG. 4A. This may enhance the UE’s (402, 404) overall throughput and also improve the performance during reduced latencies.

[0077] FIG. 5 illustrates an example transmission (500) of a Protocol Data Unit (PDU) session on separate transport blocks, in accordance with an embodiment of the present disclosure.

[0078] As illustrated in FIG. 5, in an embodiment, the UE (502) may be enabled to support multiple PDU session paths (504-1, 504-N) within the same cell access in a sixth generation (6G) system. The 6G core network (506) may also support the multiple PDU session paths (514-1, 514-N) towards the UE (502). This Single Access Multi-path (SAMP) PDU session may support one or many applications data transfer between the UE (104) and the DNN (508). The UE (502) may support ‘N’ paths within a PDU session through the single cell access. The 6G system may also support the plurality of PDU sessions per UE (502). Whereas in 6G, multiple PDU sessions may be established, where each PDU session may be transmitted on separate Transport Blocks (510-1, 510-N) over the air interface. The UE (502) may support N Transport blocks. The UE (502) may be enabled to indicate to the RAN node (512), during the RRC connection establishment, regarding the need of creating multiple UE contexts. This request enables the RAN node (512) to create multiple UE contexts for the UE (502) and allocate multiple Radio Network Temporary Identifiers (RNTIs) associated with each UE context respectively. Applications data transfer may occur between the UE (502) and a Data Network Name (DNN) (508) through an AS 1 (510) server.

[0079] FIG. 6 illustrates an example flow diagram (600) of Radio Resource Control (RRC) connection with the multiple user equipment (UE) contexts, in accordance with an embodiment of the present disclosure.

[0080] As illustrated in FIG. 6, the flow diagram (600) may include the following steps.

[0081] At step 608: The UE (602) may transmit a MSG1 RACH preamble 6G-gNB- DU (604).

[0082] At step 610: The 6G-gNB-DU (604) may provide L2 admission control.

[0083] At step 612: The 6G-gNB-DU (604) may create UE CP context with C-RNT 1-01.

[0084] At step 614: The 6G-gNB-DU (604) may transmit MSG2 RAR (temporary C- RNTI) to the UE (602).

[0085] At step 616: The UE (602) may transmit MSG3, RRC setup request (Multi UE Ctx Req Flag = True, Num of CTx = 2)

[0086] At step 618: Contention may be resolved between the UE (602) and the 6G- gNB-DU (604).

[0087] At step 620: The 6G-gNB-DU (604) may transmit a F1AP initial UL RRC Message Transfer (RRC Setup Request, C-RNTI-01) to the 6G-gNB-CU (606).

[0088] At step 622: The 6G-gNB-CU (606) may provide L3 admission control and create UE CP context with C-RNTI-01.

[0089] At step 624: The 6G-gNB-CU (606) may transmit F1AP Additional CRNTI A1OC REQ (C-RNTI-01) to the 6G-gNB-DU (604).

[0090] At step 626: The 6G-gNB-DU (604) may allocate additional C-RNT1-02, create UP UE Ctx for C-RNT 1-01, and create UP UE Ctx for C-RNT1-02.

[0091] At step 628: The 6G-gNB-DU (604) may transmit F1AP Additional CRNTI A1OC RSP (C-RNTI-01, C-RNT1-02) to the 6G-gNB-CU (606).

[0092] At step 630: The 6G-gNB-CU (606) may create UP UE Ctx for C-RNTI-01 and create UP UE Ctx for C-RNT 1-02.

[0093] At step 632: The 6G-gNB-CU (606) may transmit F1AP DL RRC MESSAGE TRANSFER (RRC SETUP (C-RNT1-02)) to the 6G-gNB-DU (604).

[0094] At step 634: The 6G-gNB-DU (604) may transmit the MSG4 RRC setup to the UE (602).

[0095] At step 636: The UE (602) may create CP UE Ctx for C-RNT 1-01, create UP UE Ctx for C-RNT 1-01, and create UP UE Ctx for C-RNT 1-02.

[0096] At step 638: The UE (602) may transmit the RRC STEUP COMPLETE message to the 6G-gNB-DU (604).

[0097] At step 640: The 6G-gNB-DU (604) may transmit the F1AP UL RRC MESSAGE TRANSFER (RRC SETUP COMPLETE) message to the 6G-gNB-CU (606).

[0098] At step 642: The UE (602) may create CP UE Ctx for CRNTI-01.

[0099] At step 644: The UE (602) may create UP UE Ctx for CRNTI-01.

[0100] At step 646: The UE (602) may create UP UE Ctx for CRNTI-01.

[0101] At step 648: The UE (602) may transmit RRC Setup complete message to the6G-gNB-DU (604).

[0102] At step 650: The 6G-gNB-DU (604) may transmit F1AP UL RRC Message Transfer (RRC Setup Complete) to the6G-gNB-CU (606).

[0103] FIG. 7 illustrates an example diagram (700) representing allocation of radio resources by the proposed system (108) separately for the UE contexts, in accordance with an embodiment of the present disclosure.

[0104] In an embodiment, after the establishment of the RRC connection with the multiple UE contexts (708-1, 708-N) requirement, the UE contexts (708-1, 708-N) created may be across UE (702), 6gNB-DU (704), and 6gNB-CU (706) as illustrated in FIG. 7. The base station in the RAN node (including the 6gNB-DU (704), and 6gNB-CU (706)) may allocate the radio resources separately for each of the UE contexts (708-1, 708-N) based on the PDU sessions received from the 6G core network (714). So, for any TTI, the UEs (702) may include multiple physical resources, which can be used simultaneously. Applications data transfer may occur between the UE (702) and a DNN (710) through an AS1 (712) server.

[0105] FIG. 8 illustrates an example diagram (800) of a single access multi-path (SAMP) scenario using a Multi-path Transport Control Protocol (MPTCP) protocol, in accordance with an embodiment of the present disclosure.

[0106] As illustrated in FIG. 8, in an embodiment, the SAMP scenario may use the MPTCP protocol to support multiple TCP sub flows. MPTCP may provide a Multipath TCP service through the RAN node (808), which enables a transport connection to operate across multiple paths (810-1 to 810-N) from the 6G core network (804) to the UE (802). The MPTCP protocol may operate at the transport layer and aim to be transparent to both higher and lower layers. TCP based applications communicate between an application client at the UE (802) and the DNN (806) across these multiple paths simultaneously. Further, there may be a one-to-one mapping between a connection and an application socket.

[0107] FIG. 9 illustrates an example diagram (900) of a SAMP scenario using a Multi-path Quick User Datagram Protocol (UDP) Internet Connection (MPQUIC) protocol, in accordance with an embodiment of the present disclosure.

[0108] As illustrated in FIG. 9, in an embodiment, the SAMP scenario may use the MPQUIC protocol to support multiple UDP sub flows. MPQUIC may be an encrypted, multiplexed low-latency transport protocol providing reliable in-order data transfer on eachpath. Further, UDP based applications may communicate between an application client at the UE (902) and the DNN (906) across these multiple paths from the 6G core network (904) to the UE (902).

[0109] FIG. 10 illustrates an example diagram (1000) of a SAMP scenario using an Aggregator and Disaggregator Function (AgDg) Protocol, in accordance with an embodiment of the present disclosure.

[0110] As illustrated in FIG. 10, in an embodiment, the SAMP scenario may use the generic AgDg protocol to support multiple sub flows or paths from the 6G core network (1004) to the UE (1002). The AgDg protocol may detect an incoming application data stream, maps the data to the available paths or subflows towards the UE (1002) and vice versa. The AgDg protocol may handle both TCP and UDP based application data streams simultaneously. Applications may communicate between an application client at the UE (1002) and the DNN (1006) across these multiple paths from the 6G core network (1004) to the UE (1002).[oni] FIG. 11 illustrates an example diagram (1100) of the SAMP scenario, realized with multi-path spanning across multiple cells, in accordance with an embodiment of the present disclosure.

[0112] In an embodiment, the SAMP scenario may be realized with multi-path spanning across multiple cells. Multiple cells belonging to Intra-Radio Access Technology (RAT), Inter-RAT, Intra-Frequency, Inter-Frequency, Intra-Public Land Mobile (PLMN), Inter-PLMN, Intra-Third Generation Partnership Project (3GPP), Inter-3GPP, etc., access technology scenarios may be applicable. Applications may communicate between an application client at the UE (1102) and the DNN (1106) across these multiple paths from the 6G core network (1104) to the UE (1102).

[0113] FIG. 12 illustrates an example flow diagram (1200) of a UE triggered service request, in accordance with an embodiment of the present disclosure.

[0114] As illustrated in FIG. 12, the flow diagram (1200) may include the following steps.

[0115] At step 1208: The UE (1202) may successfully register with the network.

[0116] At step 1210: The UE (1202) may decide to establish reactive PDU sessions.

[0117] At step 1212: The UE (1202) may transmit the service request (allowed PDU session status primary (PS 1-01), allowed PDU session status secondary (PS 1-01) to 6G core network (1206).

[0118] At step 1214: The 6G core network (1206) may determine T3S rules.

[0119] At step 1216: The 6G core network (1206) may allocate IP# 1, IP#2.

[0120] At step 1218: The 6G core network (1206) may allocate MPTCP / MPQUIC link specific multipath addresses.

[0121] At step 1220: The 6G core network (1206) may and set up primary and secondary paths for requested PDU sessions.

[0122] At step 1222: The N2 initial context setup request may be set across the UE (1202), the 6gNB (1204), and the 6G core network (1206).

[0123] At step 1224: The 6gNB (1204) may establish the radio data bearers for the UE context associated with CRNTI-01 and the primary PDU session path.

[0124] At step 1226: The 6gNB (1204) may establish the radio data bearers for the UE context associated with CRNTI-02 and the secondary PDU session path.

[0125] At step 1228: The RRC connection reconfiguration may be triggered for both UE contexts associated with both CRNTI-01 and CRNTI-02 and service accept Non-Access Stratum (NAS) PDU may be conveyed to the UE (1202).

[0126] At step 1230: The UE (1202) may setup primary path for requested PDU session associated with UE CP CTx with CRNTI-01.

[0127] At step 1232: The UE (1202) may setup secondary path for requested PDU session associated with UE CP CTx with CRNTI-02.

[0128] At step 1234: The UE (1202) may transmit UL data (on PUSCH with CRNTI- 01) to the 6gNB (1204).

[0129] At step 1236: The 6gNB (1204) may transmit N3 UL data on primary path towards the 6G core network (1206).

[0130] At step 1238: The UE (1202) may transmit UL data (on PUSCH with CRNTI- 02) to the 6gNB (1204).

[0131] At step 1240: The 6gNB (1204) may transmit N3 UL data on secondary path towards the 6G core network (1206).

[0132] At step 1242: The 6gNB (1204) may allocate PDU session DL TEID for primary path.

[0133] At step 1244: The 6gNB (1204) may allocate PDU session DL TEID for secondary path.

[0134] At step 1246: The 6gNB (1204) may transmit N2 initial context setup response (PDU session DL TEID for both primary and secondary paths).

[0135] At step 1248: The 6G core network (1206) may configure user plane function (UPF) with DL TEID for primary and secondary paths.

[0136] At step 1250: The 6G core network (1206) may transmit N3 DL data on primary path to the 6gNB (1204).

[0137] At step 1252: The 6gNB (1204) may transmit DL data on PDSCH with (CRNTI-01) to the UE (1202).

[0138] At step 1254: The 6G core network (1206) may transmit N3 DL data on secondary path to the 6gNB (1204).

[0139] At step 1256: The 6gNB (1204) may transmit DL data on PDSCH with (CRNTI-02) to the UE (1202).

[0140] When the UE (1202) has some data to send towards the 6G core network (1206), the UE (1202) may decide to establish a connection with the Access and MobilityManagement Function (AMF) and further establish or activate the required PDU sessions (the plurality of PDU sessions). Further, the UE (1202) may prepare the SESSION REQUEST message with the following changes in its message contents as shown in Table 1.Table 1

[0141] In an embodiment, the “Allowed PDU session status Primary” IE may indicate the list of PDU sessions which needs to be established or activated. When the IE is included and set to bit ‘ 1 it indicates that the corresponding PDU session needs to be established or activated. There can be up to 15 PSI as illustrated in Table 2. Here, the PSI-1 bit is set as an example, which indicates to the network that, it has to establish or activate the PDU Session- 1 as shown in Table 2. Hence, the 6G core network (1206) triggers the establishment or activation of a PDU session (among the plurality of PDU sessions) for PSI-1 with all user plane resources and allocates a single IP address, as normal, post the verification of the UE’s subscription data and the operator’s policies.Table 2

[0142] But, when the UE (1202) includes both “Allowed PDU session status primary” IE and the “Allowed PDU session status secondary” IE with the corresponding PSI bit set to ‘1’, here PSI-1 is set to ‘1’in both the IES as an example, then it indicates to the 6G core network (1206) that, it has to establish two paths for the same UE (1202). Hence, the 6G core network (1206) may trigger the establishment or activation of a PDU session (among the plurality of PDU sessions) for PSI-1 with two separate paths with all the necessary user plane resources and allocates two IP addresses, for each path. This is illustrated in Tables 3 and 4.

[0143] As a further extension, to support more than two paths, the “Allowed PDU session status secondary” IE may range from 1 to N, where, ‘N’ represents the number of additional parallel paths for the same UE (1202). Once the service request is accepted, the UE (1202) prepares the N2 message INITIAL CONTEXT SETUP REQUEST message with the following changes in the IE “PDU Session Resource Setup Request List.” Normally the IE “PDU Session Resource Setup Request List” is having the range from “0...1”. But, the IE will be updated to “0...N” to support the establishment of multiple paths, at the 6G-RAN for the same UE (1202). When the IE is included and has only one entry, then it is considered as “PDU Session Resource Setup Request List primary” and triggers the establishment of only one path for the UE (1202) at the RAN (1204). When the IE is included and has more than one entry, let us say two entries as an example, then it is considered first entry as “PDU Session Resource Setup Request List Primary” and second entry as “PDU Session Resource Setup Request List Secondary”. This triggers the establishment of two paths for the UE (1202) at the RAN (1204). Thus, the RAN (1204) establishes one set of data radio bearers for primary and maps it to the UE’s UP context associated with C-RNTI-01 and another set of data radio bearers for secondary and maps it to the UE’s UP context associated with C-RNTI-02. Similarly, the RAN (1204) supports ‘N’ such paths, if the 6G core network (1206) indicates by including ‘N’ number of entries of the IE “PDU Session Resource Setup Request List” in the N2 message INITIAL CONTEXT SETUP REQUEST message.

[0144] Further in an embodiment, the 6gNB (1204) allocates the PDU session TEIs for each established paths and shares the TEIs to the 6G core network (1206) via the N2 message INITIAL CONTEXT SETUP RESPONSE message. The IE “PDU Session Resource Setup Response List” shall be changed as per requirement. Normally the IE “PDU Session Resource Setup Response List” is having the range from “0...1”. But, the list may be updated to “0...N” to support the indication of the successful establishment of each paths, at the 6G-RAN (1204) for the same UE (1202). When the IE is included and has only one entry, then it is considered as “PDU Session Resource Setup Response List Primary” and includes the allocated Terminal Endpoint Identifier’s (TEIs) for the single path.

[0145] When the IE is included and has more than one entry, let us say two entries as an example, then it is considered first entry as “PDU Session Resource Setup Response List Primary” and second entry as “PDU Session Resource Setup Response List Secondary”. This enables the 6gNB (1204) to indicate the successful establishment of two paths for the UE (1202) at the RAN (1204) and also enables the 6gNB (1204) to convey the allocated TEIs for each path separately. Once the 6G core network (1206) receives the DL TEIs from the 6gNB (1204), then the 6G core network (1206) may start forwarding the DL data towards the DL TEIs on both the paths. The 6gNB (1204) may trigger the establishment of the radio data bearers at the UE (1202) by initiating the RRC reconfiguration procedures for both the paths. In this case, the 6gNB (1204) may indicate to the UE (1202) to apply the same RRC reconfiguration-IEs for both the paths by including only one IE or the 6gNB (1204) may indicate to the UE (1202) to apply different RRC reconfigurations for each path, by including different RRC reconfiguration-IEs in the RRC Reconfiguration message. This enables the UE (1202) to establish the radio data bearers associated to each of the paths, corresponding to the each of the UE’s UP contexts (the plurality of UE contexts). This RRC message also carries the NAS message service accept as part of the NAS-PDU to the UE (1202). In the message service accept, the IE “PDU session reactivation list” shall be supported from the range 0 to N, where ‘N’ represents the number of paths established or activated, as illustrated in the below Tables 5 and 6.Table 5

[0146] As an example scenario, the IE “PDU session reactivation list” may include two entries, and include two paths with PSI-1, viz., PDU session reactivation list[l] and PDU session reactivation list[2], as shown in Tables 7 and 8.Table 7Table 8

[0147] When the UE (1202) receives the service accept message with this IE “PDU session reactivation list” as illustrated in Tables 7 and 8, the UE (1202) maps the contents associated with “PDU session reactivation result[l]” with its user plane context associated with C-RNTI-01 and the maps the contents associated with “PDU session reactivationresult[2]” with its user plane context associated with C-RNTI-02. Similarly, the UE (1202) may map the IP#1 and IP#2 to the UE’s UP contexts associated with C-RNTI-01 and C- RNTI-02 respectively. Thus an end to end multipath may be established between the UE (1202) and the 6G core network (1206) and the UE (1202), the 6G core network (1206) may start exchanging the DL and UL data across these multiple paths, utilizing the radio resources optimally and enhancing the chances of increasing the resource allocation for the UE (1202) by the MAC scheduler.

[0148] FIG. 13 illustrates an example flow diagram (1300) of a core network triggered service request, in accordance with an embodiment of the present disclosure.

[0149] As illustrated in FIG. 13, the flow diagram (1300) may include the following steps.

[0150] At step 1308: The UE (1302) may successfully register with the network.

[0151] At step 1310: The 6G core network (1306) may transmit N2 paging information to the 6gNB (1304).

[0152] At step 1312: The 6gNB (1304) may transmit the Uu paging information to the UE (1302).

[0153] At step 1314: The UE (1302) may decide to respond to the paging.

[0154] At step 1316: The UE (1302) may transmit the service request (allowed PDU session status primary (PS1-01), allowed PDU session status secondary (PS1-01) to 6G core network (1306).

[0155] At step 1318: The 6G core network (1306) may determine T3S rules.

[0156] At step 1320: The 6G core network (1306) may allocate IP# 1, IP#2.

[0157] At step 1322: The 6G core network (1306) may allocate MPTCP / MPQUIC link specific multipath addresses.

[0158] At step 1324: The 6G core network (1306) may and set up primary and secondary paths for requested PDU sessions.

[0159] At step 1326: The N2 initial context setup request may be set across the UE (1302), the 6gNB (1304), and the 6G core network (1306).

[0160] At step 1328: The 6gNB (1304) may establish the radio data bearers for the UE context associated with CRNTI-01 and the primary PDU session path.

[0161] At step 1330: The 6gNB (1304) may establish the radio data bearers for the UE context associated with CRNTI-02 and the secondary PDU session path.

[0162] At step 1332: The RRC connection reconfiguration may be triggered for both UE contexts associated with both CRNTI-01 and CRNTI-02 and service accept NAS PDU may be conveyed to the UE (1302).

[0163] At step 1334: The UE (1302) may setup primary path for requested PDU session associated with UE CP CTx with CRNTI-01.

[0164] At step 1336: The UE (1302) may setup secondary path for requested PDU session associated with UE CP CTx with CRNTI-02.

[0165] At step 1338: The UE (1302) may transmit UL data (on PUSCH with CRNTI- 01) to the 6gNB (1304).

[0166] At step 1340: The 6gNB (1304) may transmit N3 UL data on primary path towards the 6G core network (1306).

[0167] At step 1342: The UE (1302) may transmit UL data (on PUSCH with CRNTI- 02) to the 6gNB (1304).

[0168] At step 1344: The 6gNB (1304) may transmit N3 UL data on secondary path towards the 6G core network (1306).

[0169] At step 1346: The 6gNB (1304) may allocate PDU session DL TEID for primary path.

[0170] At step 1348: The 6gNB (1304) may allocate PDU session DL TEID for secondary path.

[0171] At step 1350: The 6gNB (1304) may transmit N2 initial context setup response (PDU session DL TEID for both primary and secondary paths).

[0172] At step 1352: The 6G core network (1306) may configure user plane function (UPF) with DL TEID for primary and secondary paths.

[0173] At step 1354: The 6G core network (1306) may transmit N3 DL data on primary path to the 6gNB (1304).

[0174] At step 1356: The 6gNB (1304) may transmit DL data on PDSCH with (CRNTI-01) to the UE (1302).

[0175] At step 1358: The 6G core network (1306) may transmit N3 DL data on secondary path to the 6gNB (1304).

[0176] At step 1360: The 6gNB (1304) may transmit DL data on PDSCH with (CRNTI-02) to the UE (1302).

[0177] FIG. 14 illustrates an example flow diagram (1400) of mobility registration update, in accordance with an embodiment of the present disclosure.

[0178] As illustrated in FIG. 14, the flow diagram (1400) may include the following steps.

[0179] At step 1408: The UE (1402) may successfully register with the 6G core network (1406).

[0180] At step 1410: The UE (1402) may decide to update the mobility based registration to the 6G core network (1406).

[0181] At step 1412: The UE (1402) may send a registration request (Allowed PDU session status Primary PS-01, Allowed PDU session status Secondary PS-01).

[0182] At step 1414: The 6G core network (1406) may determine T3S rules.

[0183] At step 1416: The 6G core network (1406) may allocate IP# 1, IP#2.

[0184] At step 1418: The 6G core network (1406) may allocate MPTCP / MPQUIC link specific multipath addresses.

[0185] At step 1420: The 6G core network (1406) may and set up primary and secondary paths for requested PDU sessions (of the plurality of PDU sessions).

[0186] At step 1422: The N2 initial context setup request may be set across the UE (1402), the 6gNB (1404), and the 6G core network (1406).

[0187] At step 1424: The 6gNB (1404) may establish the radio data bearers for the UE context associated with CRNTI-01 and the primary PDU session path.

[0188] At step 1426: The 6gNB (1404) may establish the radio data bearers for the UE context associated with CRNTI-02 and the secondary PDU session path.

[0189] At step 1428: The RRC connection reconfiguration may be triggered for both UE contexts (of the plurality of UE contexts) associated with both CRNTI-01 and CRNTI-02 and service accept NAS PDU may be conveyed to the UE (1402).

[0190] At step 1430: The UE (1402) may setup primary path for requested PDU session associated with UE CP CTx with CRNTI-01.

[0191] At step 1432: The UE (1402) may setup secondary path for requested PDU session (of the plurality of PDU sessions) associated with UE CP CTx with CRNTI-02.

[0192] At step 1434: The UE (1402) may transmit UL data (on PUSCH with CRNTI- 01) to the 6gNB (1404).

[0193] At step 1436: The 6gNB (1404) may transmit N3 UL data on primary path towards the 6G core network (1406).

[0194] At step 1438: The UE (1202) may transmit UL data (on PUSCH with CRNTI- 02) to the 6gNB (1404).

[0195] At step 1440: The 6gNB (1404) may transmit N3 UL data on secondary path towards the 6G core network (1406).

[0196] At step 1442: The 6gNB (1404) may allocate PDU session DL TEID for primary path.

[0197] At step 1444: The 6gNB (1404) may allocate PDU session DL TEID for secondary path.

[0198] At step 1446: The 6gNB (1404) may transmit N2 initial context setup response (PDU session DL TEID for both primary and secondary paths).

[0199] At step 1448: The 6G core network (1406) may configure user plane function (UPF) with DL TEID for primary and secondary paths.

[0200] At step 1450: The 6G core network (1406) may transmit N3 DL data on primary path to the 6gNB (1404).

[0201] At step 1452: The 6gNB (1404) may transmit DL data on PDSCH with (CRNTI-01) to the UE (1402).

[0202] At step 1454: The 6G core network (1406) may transmit N3 DL data on secondary path to the 6gNB (1404).

[0203] At step 1456: The 6gNB (1404) may transmit DL data on PDSCH with (CRNTI-02) to the UE (1402).

[0204] At step 1458: The UE (1402) may transmit UL INFORMATION TRANSFER (REGISTRATION COMPLETE) to the 6gNB (1404).

[0205] At step 1460: The 6gNB (1404) may transmit UL NAS TRANSPORT (registration complete) to the 6G core network (1406).

[0206] In an embodiment, the UE (1402) may be enabled to support multiple paths for the same SAMP PDU session, by acquiring multiple IP addresses from the 6G core network (1406). When the UE (1402) decides to establish SAMP PDU session, the UE (1402) first allocates a PDU session ID, PDU Session ID-01 as an example. The UE (1402) then prepares and sends a PDU SESSION ESTABLISHMENT REQUEST containing PDU Session ID-01 to the 6GC. If it is a new request, the session manager creates a new SM context for the UE (1402) and allocates an IP Address, IP# 1 as an example. If the UE (1402) requested for the MPTCP and / or MPQUIC functionality, then the session manager allocates the MPTCP / MCQUIC link specific multipath addresses. Further, the UE (1402) prepares and sends PDU SESSION ESTABLISHMENT ACCEPT through the N2 PDU SESSION REQUEST towards the 6gNB (1404). Now, the 6gNB (1404) initiates the establishment of the data radio bearers towards the UE (1402). Here, the 6gNB (1404) activates the UE’s UP contextassociated with C-RNTI-01. Also, the 6gNB (1404) forwards the PDU SESSION ESTABLISHMENT ACCEPT NAS message to the UE (1402) via its CP UE context. Then the UE (1402) starts sending the UL Data on UE’s UP context associated radio resources like PUSCH scrambled with C-RNTI-01. When the UPF receives the DL Tunnel end point identifiers, the UPF starts sending the data towards the 6gNB (1404) which in turn forwards the DL data on UE’s UP context associated radio resources like PDSCH scrambled with C- RNTI-01. This completes one path creation. Now, the UE (1402) decides to add another UP path. The UE (1402) prepares the PDU SESSION ESTABLISHMENT REQUEST message with Request type set to MA PDU and also includes the same PDU Session Identifier [PDU Session ID-01], which it allocated earlier. Then the UE (1402) sends this message to 6G core network (1406). When the 6G core network (1406) determines that, SM context is already available for this UE (1402), the 6G core network (1406) reuses the same SM context, rather than rejecting the request. The 6G core network (1406) allocates additional IP address for the same UE [IP#2] and also if the UE requested for the MPTCP and / or MPQUIC functionality, then the session manager allocates the MPTCP / MCQUIC link specific multipath addresses. Then it prepares and sends PDU SESSION ESTABLISHMENT ACCEPT through the N2 PDU SESSION REQUEST towards the 6gNB (1404). Now, the 6gNB (1404) initiates the establishment of additional data radio bearers towards the same UE (1402). Here, the 6gNB (1404) activates the UE’s UP context associated with C-RNTI-02. Also, the 6gNB (1404) forwards the PDU SESSION ESTABLISHMENT ACCEPT NAS message to the UE (1402) via its CP UE context. Then the UE (1402) starts sending the UL Data on UE’s UP context associated radio resources like PUSCH scrambled with C-RNTI-02. When the UPF receives the new set of DL Tunnel end point identifiers, the UPF starts sending the data towards the 6gNB (1404) which in turn forwards the DL data on UE’s UP context associated radio resources like PDSCH scrambled with C-RNTI-02. This completes additional path creation.

[0207] FIG. 15 illustrates an example flow diagram (1500) of multiple paths for the SAMP PDU session through multiple IP addresses from the core network, in accordance with an embodiment of the present disclosure.

[0208] As illustrated in FIG. 15, the flow diagram (1500) may include the following steps.

[0209] At step 1508: The UE (1502) may be successfully registered with the 6G core network (1506).

[0210] At step 1510: The UE (1502) may transmit a PDU session establishment request [PDU session ID-01] to the 6G core network (1506).

[0211] At step 1512: The 6G core network (1506) may determine T3 rules.

[0212] At step 1514: The 6G core network (1506) may allocate IP#1.

[0213] At step 1516: The 6G core network (1506) may allocate MPTCP / MPQUIC link specific multipath addresses.

[0214] At step 1518: The 6G core network (1506) may transmit the N@ PDU session request (NAS message) to the 6gNB (1504).

[0215] At step 1520: Radio resource setup (PDU session establishment accept) for PDSCH / PUSCH with CRNTI-01 may be applied across the 6gNB (1504) and the UE (1502).

[0216] At step 1522: The UE (1502) may activate UP context for CRNTI-01.

[0217] At step 1524: The 6gNB (1504) may transmit N2 PDU session response (NAS message) to the 6G core network (1506).

[0218] At step 1526: The UE (1502) may transmit the PUSCH (CRNTI-01) to the 6gNB (1504).

[0219] At step 1528: The 6gNB (1504) may transmit the N3 UL UP data to the 6G core network (1506).

[0220] At step 1530: The 6G core network (1506) may transmit N3 UL UP data to the 6gNB (1504).

[0221] At step 1532: The 6gNB (1504) may transmit the PDSCH (CRNTI-01) to the UE (1502).

[0222] At step 1534: The UE (1502) may decide to an additional UP path for the established PDU session with ID-01.

[0223] At step 1536: The UE (1502) may transmit the PDU session establishment request (MA PDU Request type, Same PDU session ID-01) to the 6G core network (1506).

[0224] At step 1538: The 6G core network (1506) may use the same SM context.

[0225] At step 1540: The 6G core network (1506) may update T3S rules.

[0226] At step 1542: The 6G core network (1506) may allocate IP#2.

[0227] At step 1544: The 6G core network (1506) may MPTCP / MPUIC link specific multipath addresses.

[0228] At step 1546: The 6G core network (1506) may transmit the N2 PDU session request (NAS message) to the 6gNB (1504).

[0229] At step 1548: Radio resource setup (PDU session establishment accept) for PDSCH / PUSCH with CRNTI-01 may be applied across the 6gNB (1504) and the UE (1502).

[0230] At step 1550: The UE (1502) may setup the UP context for CRNTI-02.

[0231] At step 1552: The 6gNB (1504) may transmit the N2 PDU session response (NAS message) to the 6G core network (1506).

[0232] At step 1554: The UE (1502) may transmit the PUSCH (CRNTI-02) to the 6gNB (1504).

[0233] At step 1556: The 6gNB (1504) may transmit the N3 UL UP data to the 6G core network (1506).

[0234] At step 1558: The 6G core network (1506) may transmit the N3 UL UP data to the 6gNB (1504).

[0235] At step 1560: The 6gNB (1504) may transmit the PDSCH (CRNTI-02) to the UE (1502).

[0236] In an embodiment, the UE (1502) provides Request Type as “MA PDU Request” in UL NAS Transport message and ATSSS Capabilities in PDU Session Establishment Request message. The “MA PDU Request” Request Type in the UL NAS Transport message indicates to the 6G core network (1506) that this PDU Session Establishment Request is to establish a new MA PDU Session and to apply one or more steering functionalities for steering the traffic of this MA PDU session over multiple accesses. If the AMF supports MA PDU sessions, then the AMF selects a Session Management Function (SMF), which supports MA PDU sessions. The AMF informs the SMF that the request is for a MA PDU Session by including “MA PDU Request” indication and in addition, it indicates to SMF whether the UE (1502) is registered over both accesses. The SMF retrieves, via Session Management subscription data, the information whether the MA PDU session is allowed or not. If the SMF received Nsmf_PDUSession_CreateSMContext Request and the SMF is able to process the PDU Session establishment request, the SMF creates an SM context and responds to the AMF by providing an SM Context ID. If dynamic PCC is to be used for the MA PDU Session, the SMF sends an “MA PDU Request” indication to the PCF in the SM Policy Control Create message and the ATSSS Capabilities of the MA PDU session. The SMF provides the currently used Access Type(s) and RAT Type(s) to the PCF. The PCF decides whether the MA PDU session is allowed or not based on operator policy and subscription data. The PCF provides PCC rules that include MA PDU session control information. From the received PCC rules, the SMF derives ATSSS rules, which will be sent to the UE (1502) for controlling the traffic steering, switching and splitting in the uplink direction and N4 rules, which will be sent to UPF for controlling the traffic steering, switching and splitting in the downlink direction. If the UE (1502) indicates the support of “ATSSS-LL Capability,” the SMF mayderive the Measurement Assistance Information. If the Request Type indicates “Initial request,” the SMF selects an SSC mode for the PDU Session. The SMF also selects one or more UPFs as needed. In the case of PDU Session Type IPv4 or IPv6 or IPv4v6, the SMF allocates an IP address / prefix for the PDU Session (unless configured otherwise). In the case of PDU Session Type IPv6 or IPv4v6, the SMF also allocates an interface identifier to the UE (1502) for the UE (1502) to build its link-local address. For Unstructured PDU Session Type the SMF may allocate an IPv6 prefix for the PDU Session and N6 point-to-point tunnelling (based on UDP / IPv6). The SMF may perform an SMF initiated SM Policy Association Modification procedure to provide information on the Policy Control Request Trigger condition(s) that have been met. If Request Type is “initial request” and dynamic PCC is deployed and PDU Session Type is IPv4 or IPv6 or IPv4v6, SMF notifies the PCF (if the Policy Control Request Trigger condition is met) with the allocated UE IP address / prefix(es). The PCF may provide updated policies to the SMF. The PCF for PDU Session may generate PCC rule based on the URSP rule (e.g.: Connection Capability). The N4 rules derived by SMF for the MA PDU session are sent to UPF and two N3 UL CN tunnels info are allocated by the UPF. If the ATSSS LL functionality is supported for MA PDU Session, the SMF may instruct the UPF to initiate performance measurement for this MA PDU Session. If the MPTCP functionality and / or the MPQUIC functionality is supported for the MA PDU Session, the SMF may instruct the UPF to activate the MPTCP functionality and / or the MPQUIC functionality for this MA PDU Session. The UPF allocates addressing information for the Performance Measurement Function (PMF) in the UPF. If the UPF receives from the SMF a list of QoS flows over which access performance measurements may be performed, the UPF allocates different UDP ports or different MAC addresses per QoS flow per access. The UPF sends the addressing information for the PMF in the UPF to the SMF. If UDP ports or MAC addresses are allocated per QoS flow and per access, the UPF sends the PMF IP address information and UDP ports with the related QFI to the SMF in the case of IP PDU sessions and sends the MAC addresses with the related QFI to the SMF in the case of Ethernet PDU sessions. If the message from the SMF instructs the UPF to activate MPTCP functionality, the UPF allocates the UE “MPTCP link-specific multipath” addresses / prefixes. Further, the UPF sends the “MPTCP link-specific multipath” addresses / prefixes and MPTCP proxy information to the SMF. If the message from the SMF instructs the UPF to activate MPQUIC functionality, the UPF allocates the UE “MPQUIC link-specific multipath” addresses / prefixes. The UPF sends the “MPQUIC link-specific multipath” addresses / prefixes and MPQUIC proxy information to the SMF. The “MPTCP link-specific multipath”addresses / prefixes and the “MPQUIC link-specific multipath” addresses / prefixes may be the same. For the MA PDU session, the SMF includes an “MA PDU session Accepted” indication in the Namf_Communication_NlN2MessageTransfer message to the AMF and indicates to AMF that the N2 SM Information included in this message should be sent over 3GPP access. The AMF marks this PDU session as MA PDU session based on the received “MA PDU session Accepted” indication. Further, the AMF to RAN N2 PDU Session Request (N2 SM information, NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept)), CN assisted RAN parameters tuning). If the N2 SM information is not included, an N2 Downlink NAS Transport message is used instead. The AMF sends the NAS message containing PDU Session ID and PDU Session Establishment Accept targeted to the UE and the N2 SM information received from the SMF within the N2 PDU Session Request to the RAN. If the SMF derived CN assisted RAN parameters tuning are stored for the activated PDU Session(s), the AMF may derive updated CN assisted RAN parameters tuning and provide them the RAN.

[0237] In an embodiment, the UE (1502) receives a PDU Session Establishment Accept message, which indicates to UE (1502) that the requested MA PDU session was successfully established. This message includes the ATSSS rules for the MA PDU session, which were derived by SMF. If the ATSSS -LL functionality is supported for the PDU Session, the SMF may include the addressing information of PMF in the UPF into the Measurement Assistance Information. If the MPTCP functionality is supported for the MA PDU Session, the SMF shall include the “MPTCP link-specific multipath” addresses / prefixes of the UE (1502) and the MPTCP proxy information. If the MPQUIC functionality is supported for the MA PDU Session, the SMF shall include the "MPQUIC link-specific multipath" addresses / prefixes of the UE and the MPQUIC proxy information. If the SMF was informed that the UE (1502) is registered for multipath on same access, then the SMF initiates the establishment of user-plane resources for other paths on the same 3GPP access too. The SMF sends an Namf_Communication_NlN2MessageTransfer to the AMF including N2 SM Information and indicates to AMF that the N2 SM Information should be sent over non-3GPP access. Further, Namf_Communication_NlN2MessageTransfer does not include an N1 SM Container for the UE (1502). After this step, the two N3 tunnels between the PSA and RAN are established.

[0238] FIG. 16 illustrates an exemplary computer system (1600) in which or with which embodiments of the present disclosure may be implemented.

[0239] As shown in FIG. 16, the computer system (1600) may include an external storage device (1610), a bus (1620), a main memory (1630), a read-only memory (1640), a mass storage device (1650), a communication port(s) (1660), and a processor (1670). A person skilled in the art will appreciate that the computer system (1600) may include more than one processor and communication ports. The processor (1670) may include various modules associated with embodiments of the present disclosure. The communication port(s) (1660) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (1660) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (1600) connects.

[0240] In an embodiment, the main memory (1630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (1640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (1670). The mass storage device (1650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

[0241] In an embodiment, the bus (1620) may communicatively couple the processor(s) (1670) with the other memory, storage, and communication blocks. The bus (1620) may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (1670) to the computer system (1600).

[0242] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (1620) to support direct operator interaction with the computer system (1600). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (1660). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (1600) limit the scope of the present disclosure.

[0243] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.ADVANTAGES OF THE INVENTION

[0244] The present disclosure provides multipath access for Protocol Data Units (PDUs) in a wireless network. The user equipments (UEs) support multiple radios for a single registered cell in a Radio Access Network (RAN) node, and the associated core network provides multiple paths of communication for the single registered cell in the RAN.

[0245] The present disclosure provides a system where the UE requesting parallel connections to support multiple parallel radio paths on a single registered cell / RAN node is supported through the core network. The core network provides multiple paths of communication for the single registered cell in the RAN.

[0246] The present disclosure provides a system where the core network identifies multiple connection requests from the same UE through the system and provides resources, connections, quality of service (QoS), and security associated with the multiple connection requests.

[0247] The present disclosure provides a system where UEs having multi-path support receive scheduling opportunities through the system, and where each path receives separate opportunity from the scheduler.

[0248] The present disclosure provides a system where multiple UE contexts are established based on a Radio Resource Control (RRC) connection between the UE and the RAN node for accessing the multiple radio paths through the RAN node.

[0249] The present disclosure provides a system that enables the UE to support the multiple Protocol Data Unit (PDU) sessions associated with the core network through the multiple radio paths based on the established UE contexts.

[0250] The present disclosure provides a system that facilitates data exchange between the UEs and the core network through the multiple radio paths.

Claims

We Claim:

1. A system (108) for providing multi-path access in wireless network, the system (108) comprising: a processor (202) communicatively coupled to a Radio Access Network (RAN) node (110); a memory (204) operatively coupled with the processor (202), wherein said memory (204) stores instructions which, when executed by the processor (202), cause the processor (202) to: receive a request from a user equipment (UE) (104) for accessing a plurality of radio paths through single cell access of the RAN node (110) upon the registration of the UE with the RAN node (110); establish a plurality of UE contexts based on a Radio Resource Control (RRC) connection between the UE (104) and the RAN node (110) for accessing the plurality of radio paths through the RAN node (110); enable the UE (104) to support a plurality of Protocol Data Unit (PDU) sessions associated with a core network (112) through the plurality of radio paths based on the established plurality of UE contexts; and facilitate data exchange between the UE (104) and the core network (112) through the plurality of radio paths.

2. The system (108) as claimed in claim 1, wherein the processor (202) is to enable allocation of one or more radio resources to the UE (104) based on the plurality of UE contexts by providing one or more scheduling opportunities per Transmission Time Interval (TTI).

3. The system (108) as claimed in claim 1, wherein upon enablement of the UE (104) to support the plurality of PDU sessions through the plurality of radio paths, the processor (202) is to facilitate transfer of application data between the UE (104) and a Data Network Name (DNN) of the core network (112).

4. The system (108) as claimed in claim 1, wherein the UE (104) is to transmit one or more information elements (IES) associated with the request to the core network (112) through the processor (202) and request the establishment of the plurality of radio paths for each of the plurality of PDU sessions, and wherein the processor (202) is to enable the UE (104) to support the plurality of PDU sessions based on an N2 message from the core network (112).

5. The system (108) as claimed in claim 4, wherein the processor (202) is to: allocate a particular Internet (IP) address associated with the request from the UE (104); and transmit the request to the core network (112) for enabling the UE (104) to support the plurality of PDU sessions upon receiving one or more approval messages from the core network (112).

6. The system (108) as claimed in claim 5, wherein upon receiving the one or more approval messages from the core network (112), the processor (202) is to enable the data exchange between the UE (104) and the core network (112) through the plurality of radio paths.

7. A method for providing multi-path access in a wireless network, the method comprising: receiving, by a processor (202) associated with a system (108), a request from a user equipment (UE) (104) for accessing a plurality of radio paths through single cell access of a Radio Access Network (RAN) node (110) upon registration of the UE (104) with the RAN node (110); establishing, by the processor (202), a plurality of UE contexts based on a Radio Resource Control (RRC) connection between the UE (104) and the RAN node (110) for accessing the plurality of radio paths through the RAN node (110); enabling, by the processor (202), the UE (104) to support a plurality of Protocol Data Unit (PDU) sessions associated with a core network through the plurality of radio paths based on the plurality of UE contexts; and facilitating, by the processor (202), data exchange between the UE (104) and the core network through the plurality of radio paths.

8. The method as claimed in claim 7, comprising enabling, by the processor (202), allocation of one or more radio resources to the UE (104) based on the plurality of UE contexts by providing one or more scheduling opportunities per Transmission Time Interval (TTI).

9. The method as claimed in claim 7, comprising allocating, by the processor (202), an Internet Protocol (IP) address associated with the request from the UE (104) and transmitting the request to the core network for enabling the UE to support the plurality of PDU sessions upon receiving one or more approval messages from the core network.

10. The method as claimed in claim 9, comprising enabling, by the processor (202), upon receiving the one or more approval messages from the core network, the data exchange between the UE (104) and the core network (112) through the plurality of radio paths.

11. A user equipment (UE) (104) for sending requests, the UE (104) comprising: one or more processors communicatively coupled to a processor (202) associated with a system (108), wherein the one or more processors are coupled with a memory, and wherein said memory stores instructions which, when executed by the one or more processors, cause the one or more processors to: transmit a request to the processor (202) for accessing a plurality of radio paths through single cell access of a Radio Access Network (RAN) node (110) upon registration of the UE (104) with the RAN node (110); wherein the processor (202) is configured to: establish a plurality of UE contexts based on a Radio Resource Control (RRC) connection between the UE (104) and the RAN node (110) for accessing the plurality of radio paths through the RAN node (110); enable the UE (104) to support a plurality of Protocol Data Unit (PDU) sessions associated with the core network (112) through the plurality of radio paths based on the plurality of UE contexts; and facilitate data exchange between the UE (104) and the core network (112) through the plurality of radio paths.

12. A non-transitory computer-readable medium comprising processor-executable instructions that cause a processor to: receive a request from a user equipment (UE) (104) for accessing a plurality of radio paths through single cell access of a RAN node (110) upon registration of the UE with the RAN node (110); establish a plurality of UE contexts based on a Radio Resource Control (RRC) connection between the UE (104) and the RAN node (110) for accessing the plurality of radio paths through the RAN node (110); enable the UE (104) to support a plurality of Protocol Data Unit (PDU) sessions associated with a core network (112) through the plurality of radio paths based on the established plurality of UE contexts; and facilitate data exchange between the UE (104) and the core network (112) through the plurality of radio paths.

Images