METHOD AND APPARATUS FOR RECEIVING DOWNLINK DATA PACKETS OVER N3GPP ACCESS
20230007705 ยท 2023-01-05
Inventors
- Lalith KUMAR (Bangalore, IN)
- Anikethan Ramakrishna Vijaya KUMAR (Bangalore, IN)
- Kundan TIWARI (Bangalore, IN)
Cpc classification
H04W48/02
ELECTRICITY
H04W88/06
ELECTRICITY
International classification
Abstract
Methods and apparatus for receiving downlink data packets over Non-Third Generation Partnership Project (N3GPP) access. A User Equipment (UE) is configured to manage the triggering of Service Request procedures for receiving N3GPP Mobile Terminating (MT) packets in a coverage area of N3GPP access from a 5th Generation (5G) network. A Service Request procedure is triggered by the UE if the UE detects that the UE is in the coverage area of N3GPP access and that the UE is in 5th Generation Mobility Management (5GMM)-IDLE mode over N3GPP access and the back-off timer has expired. The detection is based on the UE determining that an access stratum connection is established between the UE and the 5G network over N3GPP access.
Claims
1-13. (canceled)
14. A method of a User equipment (UE), the method comprising: identifying that the UE is in idle mode over non-3rd generation partnership project (non-3GPP) access; receiving, from lower layers of the non-3GPP access, an indication indicating that an access stratum connection has been established between the UE and a network; identifying that a T3346 timer is expired; and transmitting, to an access and mobility function (AMF), a service request message over the non-3GPP access.
15. The method of claim 14, further comprising: transmitting, to the AMF, an initial service request message before receiving the indication from lower layers of the non-3GPP access; and receiving, from the AMF, a service reject message if the initial service request message cannot be accepted.
16. The method of claim 15, wherein the service reject message includes first information indicating that the network is congested and second information on the T3346 timer.
17. The method of claim 16, further comprising starting the T3346 timer based on the second information on the T3346 timer.
18. The method of claim 14, wherein, if the UE is registered with same public land mobile network (PLMN) over both a 3GPP access and the non-3GPP access, the T3346 timer is applied to both the 3GPP access and the non-3GPP access.
19. The method of claim 14, wherein, if the UE is not registered with the same PLMN over both a 3GPP access and the non-3GPP access, the T3346 timer is not applied to the 3GPP access.
20. A User Equipment (UE), the UE comprising: a transceiver; and a processor configured to: identify that the UE is in idle mode over non-3rd generation partnership project (non-3GPP) access, receive, from lower layers of the non-3GPP access, an indication indicating that an access stratum connection has been established between the UE and a network, identify that a T3346 timer is expired, and transmit, to an access and mobility function (AMF), a service request message over the non-3GPP access.
21. The UE of claim 20, wherein the processor configured to: transmit, to the AMF, an initial service request message before receiving the indication from lower layers of the non-3GPP access, and receive, from the AMF, a service reject message if the initial service request message cannot be accepted.
22. The UE of claim 21, wherein the service reject message includes first information indicating that the network is congested and second information on the T3346 timer.
23. The UE of claim 22, wherein the processor configured to start the T3346 timer based on the second information on the T3346 timer.
24. The UE of claim 20, wherein, if the UE is registered with same public land mobile network (PLMN) over both a 3GPP access and the non-3GPP access, the T3346 timer is applied to both the 3GPP access and the non-3GPP access.
25. The UE of claim 20, wherein, if the UE is not registered with the same PLMN over both a 3GPP access and the non-3GPP access, the T3346 timer is not applied to the 3GPP access.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Embodiments herein are illustrated in the accompanying drawings, through out which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[0027]
[0028]
[0029]
[0030]
[0031]
DETAILED DESCRIPTION
[0032] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0033] Embodiments herein disclose methods and apparatus for managing the triggering of Service Request procedure, by a User Equipment (UE), for receiving Mobile Terminating (MT) packets in a service area of Non-Third Generation Partnership Project (N3GPP) access. The UE can be configured to trigger a Service Request procedure if the UE is in the coverage area of N3GPP access, and if the UE is in Fifth Generation Mobility Management (5GMM)-IDLE mode over N3GPP access.
[0034] Referring now to the drawings, and more particularly to
[0035]
[0036] As depicted in
[0037] The UE(301) can determine that the UE(301) is in the coverage area of 3GPP access. Therefore, the UE(301) can send a Service Request or Registration Request to the AMF over 3GPP access. The UE(301) sends the Service Request (a NAS signalling message) over 3GPP access(step 315). Consider that the 5G network is congested. The AMF(302) sends a Service Reject or Registration Reject message (a NAS signalling response message) over 3GPP access(step 320), which includes a cause of rejection of the Service Request with a cause value #22 and a timer T3346.
[0038] After receiving the NAS signalling response from the AMF(302), the UE(301) starts the timer T3346(step 325) and determine, based on the cause value, that the 5G network is congested and that the UE(301) needs to back-off from sending further Service Requests prior to the expiry of the timer T3346. When the UE(301) comes back to the service area of N3GPP access(step 330), the UE(301) receives an indication. The indication informs the UE(301) that an access stratum connection has been established between the UE(301) and the 5G network(302).
[0039] The UE(301) determines whether the timer T3346 has expired. When the timer T3346 expires(step 335), the UE(301) triggers a Service Request procedure over N3GPP access(step 340). The UE(301) can send Service Request to the AMF(302) (a NAS signalling message). This allows the UE(301) to switch from the 5GMM-IDLE state over N3GPP access to 5GMM-CONNECTED state over N3GPP access, if the Service Request is accepted by the AMF(302). The UE(301) can receive MT data packets from the AMF over N3GPP access.
[0040] The back-off timer in this embodiment is for example timer T3346. There is co-ordination between 3GPP access and N3GPP access. The UE(301) performs the co-ordination between 3GPP access and N3GPP access, when the UE(301) is registered with same Public Land Mobile Network (PLMN) over both 3GPP access and N3GPP access. Therefore, the back-off timer is applied to both 3GPP access and N3GPP access. Otherwise, the back-off timer of 3GPP access is not applied to N3GPP access, and the back-off timer of N3GPP access is not applied to 3GPP access.
[0041]
[0042] As depicted in
[0043] The processor(401) can detect the UE(400) has moved out of the service (coverage) area of the N3GPP access network. The processor(401) can determine that the UE(400) is in 5GMM-IDLE mode over N3GPP access. The processor(401) can send a Service Request or Registration Request, using the communication interface(402), to the 5G network through the 3GPP access network. In an embodiment, the processor(401) can send the Service Request (a Non-Access Stratum (NAS) signalling message), using the communication interface(402), over 3GPP access.
[0044] Consider that the 5G network is congested. As such, the processor(401) can receive, from the 5G network, a Service Reject or Registration Reject message (a NAS signalling response message) over 3GPP access using the communication interface(402). In an embodiment, the NAS signalling response message includes a cause of rejection of the Service Request in an Information Element (IE), which includes a cause value #22 (congestion) and a timer T3346. After receiving the NAS signalling response message, the processor(401) starts the timer T3346. The processor(401) can determine, based on the cause value, that the 5G network is congested and that the UE(400) needs to back-off from sending further Service Requests prior to the expiry of the timer T3346. The processor(401) refrains from sending Service Requests prior to the expiry of the timer T3346.
[0045] Consider that the UE(400) has come back within the coverage area of the N3GPP access network. The processor(401) can determine that the UE(400) is in the coverage area of the N3GPP access network (such as Wi-Fi network) on receiving an indication. The indication informs that an access stratum connection has been established between the UE(400) and the 5G network. The UE(400), in the 5GMM-IDLE mode, through the communication interface(402), receives the indication from the lower layers of N3GPP access.
[0046] The processor(401) can determine whether the timer T3346 has expired. The UE(400) does not trigger a service request procedure over N3GPP access prior to the expiry of the timer T3346. The processor(401) of the UE(400) triggers a Service Request procedure over N3GPP access, once the timer T3346 expires. The processor(401) sends the Service Request (a NAS signalling message) to the 5G network over using the communication interface(402). This allows the UE(400) to switch from the 5GMM-IDLE state over N3GPP access to 5GMM-CONNECTED state over N3GPP access, if the Service Request is accepted by the 5G network. The UE(400) can receive MT data packets over N3GPP access.
[0047]
[0048]
[0049] As depicted in
[0050] If the UE has moved out of the service (coverage) area of the N3GPP access network and the UE is in 5GMM-IDLE mode over N3GPP access, the processor(501) can receive a Service Request or Registration Request, using the communication interface(502), from the UE the 3GPP access network. In an embodiment, the processor(501) can receive the Service Request (a Non-Access Stratum (NAS) signalling message), using the communication interface(502), over 3GPP access.
[0051] Consider that the 5G network is congested. As such, the processor(501) can send, to the UE, a Service Reject or Registration Reject message (a NAS signalling response message) over 3GPP access using the communication interface(502). In an embodiment, the NAS signalling response message includes a cause of rejection of the Service Request in an Information Element (IE), which includes a cause value #22 (congestion) and a timer T3346.
[0052] Consider that the UE has come back within the coverage area of the N3GPP access network(such as Wi-Fi network) on receiving an indication. The indication informs that an access stratum connection has been established between the UE and the 5G network. The UE, in the 5GMM-IDLE mode, receives the indication from the lower layers of N3GPP access.
[0053] If the timer T3346 has expired, the UE(400) triggers a Service Request procedure over N3GPP access. The processor(501) receives the Service Request (a NAS signalling message) from the UE over using the communication interface(502). The processor(501) determines whether to accept the Service Request from the UE. If the Service Request is accepted by the AMF, this allows the UE to switch from the 5GMM-IDLE state over N3GPP access to 5GMM-CONNECTED state over N3GPP access. The processor(501) can send MT data packets over N3GPP access.
[0054]
[0055] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in
[0056] The embodiments disclosed herein describe methods and apparatus for managing the triggering of Service Request procedures by the UE for receiving MT packets over N3GPP access. The UE is configured to trigger a Service Request procedure if the UE detects that the UE is in N3GPP access coverage area, and if the UE detects that the UE is in 5GMM-IDLE mode over N3GPP access. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment through or together with a software program written in example Very high speed integrated circuit Hardware Description Language (VHDL), or any other programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means, which could be, for example, a hardware means, for example, an Application-specific Integrated Circuit (ASIC), or a combination of hardware and software means, for example, an ASIC and a Field Programmable Gate Array (FPGA), or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of Central Processing Units (CPUs).
[0057] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.