Wireless communication scheme for supporting connection to the Internet protocol

Abstract

A method of wireless communication is provided. The method includes transmitting, by a user device, a first message for requesting an Internet Protocol (IP) address to be used for wireless communication to an access network, and receiving, by the user device, IP address information including an IP address allocated to the user device from the access network. In one embodiment, the first message is an RRC uplink (UL) information transfer message including a Dynamic Host Configuration Protocol (DHCP) request message.

Description

Technical Field

[0001] This document relates to systems, devices, and techniques for wireless communication.

Background Art

[0002] Efforts are currently underway to define a next-generation wireless communication network that provides better deployment flexibility, support for a large number of devices and services, and different technologies for efficient system evolution.

Summary of the Invention

Means for Solving the Problems

[0003] Various methods and apparatuses for supporting a non-access stratum (NAS) protocol in a wireless communication system are provided.

[0004] In one exemplary aspect, a method of wireless communication is disclosed. The method includes transmitting, by a user device, a first message to an access network to request an Internet Protocol (IP) address to be used for wireless communication, and receiving, by the user device, from the access network, IP address information including an IP address allocated to the user device.

[0005] In another exemplary aspect, another method of wireless communication is disclosed. The method includes receiving, by an access network, a first message to request an Internet Protocol (IP) address to be used for wireless communication, allocating, by the access network, an IP address to a user device, and transmitting, by the access network, to the user device, IP address information including the IP address allocated to the user device.

[0006] In yet another exemplary aspect, a wireless communication device comprising a processor is disclosed. The processor is configured to implement the methods described herein.

[0007] In another exemplary aspect, the various techniques described herein may be embodied as processor-executable code and stored on a computer-readable program medium.

[0008] Details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

Brief Description of the Drawings

[0009]

Figure 1

[0010]

Figure 2

[0011]

Figure 3

[0012]

Figure 4

[0013]

Figure 5

[0014]

Figure 6

[0015]

Figure 7

[0016]

Figure 8

[0017]

Figure 9

Figure 10

DETAILED DESCRIPTION OF THE INVENTION

[0018] The section headings in this document are used only to improve readability and do not limit the scope of the disclosed embodiments and techniques within each section to that section only. Further, some embodiments are described with reference to the 3rd Generation Partnership Project (3GPP (registered trademark)) New Radio (NR) standard ("5G") for ease of understanding, and the described technology can be implemented in different wireless systems implementing protocols other than the 5G protocol.

[0019] FIG. 1 shows an exemplary architecture to which various embodiments of the disclosed technology may be applied. The exemplary architecture as shown in FIG. 1 corresponds to a 5G System (5GS) architecture that includes the following network functions (NFs).

[0020] 1) UE, i.e., user equipment.

[0021] 2) RAN, i.e., radio access network.

[0022] 3) AMF: Access and Mobility Management Function. This NF includes functionalities such as UE mobility management, reachability management, connection management, and registration management. AMF terminates the RAN control plane (CP) interface N2 and the NAS interface N1, NAS encryption, and integrity protection. AMF also distributes the SM NAS to the appropriate SMF via the N11 interface.

[0023] 4) UDM: Unified Data Management. This NF manages the subscription profile for the UE. The subscription data is stored in the Unified Data Repository (UDR). The subscription information includes network slice related subscription data used for mobility management and session management. AMF and SMF read the subscription data from UDM.

[0024] 5) NSSF: Network Slice Selection Function. This NF supports the following functionalities: selecting a set of network slice instances to provide services to the UE; determining the allowed NSSAI and mapping it to the HPLMN S-NSSAI if required; determining the configured NSSAI and mapping it to the HPLMN S-NSSAI if required; determining the set of AMFs to be used to provide services to the UE, or, based on the configuration, possibly determining a list of candidate AMFs by querying the Network Repository Function (NRF).

[0025] 6) SMF; Session Management Function. This NF includes the following functionalities: session establishment, modification, and release; UE IP address allocation and management; selection and control of the user plane (UP) function, etc.

[0026] 7) UPF: User Plane Function. This NF serves as an anchor point for radio intra- / inter-RAT mobility and as an external PDU session point for the interconnection to the Data Network (DN). The UPF also routes and forwards data packets according to instructions from the SMF. The UPF also buffers downlink (DL) data when the UE is in the idle mode.

[0027] 8) PCF: Policy Control Function. This NF supports an integrated policy framework to control network behavior. The PCF provides access management policies to the AMF, session management policies to the SMF, or UE policies to the UE. The PCF can access the UDR to obtain relevant subscription information for policy decision-making.

[0028] Figure 2 shows an example of the control plane protocol stack between the UE and the AMF.

[0029] The following description can be applied to the NAS-MM and 5G-AN protocol layers as shown in Figure 2.

[0030] NAS-MM: The NAS protocol related to the MM (Mobility Management) functionality supports registration management functionality, connection management functionality, and activation and deactivation of the user plane connection. NAS-MM is also involved in the encryption and integrity protection of NAS signaling. The 5G NAS protocol is defined in 3GPP (registered trademark) TS24.501.

[0031] 5G-AN protocol layer: This protocol / layer set depends on 5G-AN (Access Network). In the case of NG-RAN (Next Generation Radio Access Network), the radio protocol between the UE and the NG-RAN node (eNodeB or gNodeB) includes the Access Stratum (AS) layer and lower layers, as defined in 3GPP (Registered Trademark) TS36.300 and 3GPP (Registered Trademark) TS38.300.

[0032] The NAS protocol is adopted to establish a NAS signaling connection between the UE and the core network. The internal system structure of the terminal includes an Operating System (OS) and a modem. Currently, the NAS layer is supported in the modem, which means that the modem needs to be upgraded whenever new features are added to the NAS layer. However, modem upgrades are complex and require long-term evolution.

[0033] Recognizing the above problems, various implementations of the disclosed technology provide a method for supporting NAS via IP (Internet Protocol). Using the implementation of the disclosed technology, the NAS layer can be supported in the operating system, and it is easier to upgrade the operating system to support new features in NAS.

[0034] (Exemplary Implementation 1: Control Plane Protocol Stack between UE and AN)

[0035] Figure 3 shows an example of a control plane protocol stack between a UE and an AN. As shown in Figure 3, the implementation of the disclosed technology provides a control plane protocol stack between the UE and the AN, and the UE and the AN include an Internet layer and a transport layer. In Figure 3, the Internet layer and the transport layer are inserted between the AN protocol layer and the NAS layer. The Internet layer and the transport layer are supported in an operating system (OS). The protocol for the Internet layer is IP. The protocol for the transport layer can be TCP (Transmission Control Protocol), UDP (User Datagram Protocol), QUIC (Quick UDP Internet Connections), or others. The AN protocol layer includes an AS layer and a lower layer.

[0036] (Exemplary Implementation 2: IP Address Allocation during RRC Connection Establishment Procedure)

[0037] Figure 4 shows an exemplary procedure for IP address allocation during the RRC connection establishment procedure. In the example of Figure 4, the UE is divided into UE-NAS, UE-OS, and UE-AS to explicitly illustrate the interaction between the UE NAS layer, the UE OS layer, and the UE AS layer.

[0038] There are two options for allocating an IP address to the UE in the example of Figure 4. Therefore, one of Option 1 or Option 2 is implemented to allocate an IP address to the UE.

[0039] (Option 1 Regarding IP Address Allocation)

[0040] Operation 1. From UE-NAS to UE-OS: The UE NAS layer sends an initial NAS message to the UE OS layer.

[0041] Operation 2. From UE-OS to UE-AS: The UE OS layer transfers the initial NAS message with an IP address request indication to the UE AS layer.

[0042] Action 3. From UE-AS to RAN: The UE AS layer starts the RRC connection establishment procedure by transmitting an RRC setup request message to the RAN. The RRC setup request message includes an IP address request indication or an indication for indicating UE capabilities that support NAS via IP.

[0043] Action 4. RAN: The RAN allocates an IP address for the UE.

[0044] Action 5. From RAN to UE-AS: The RAN transmits an RRC setup response message to the UE AS layer. The RRC setup response message includes the IP address information allocated to the UE. The IP address information can include an IP address, a port number, a subnet mask, a default gateway, a DNS (Domain Name System) server, etc.

[0045] Action 6. From UE-AS to UE-OS: The UE AS layer transfers the allocated IP address information to the UE OS layer. After Action 6, Action 9 is carried out.

[0046] (Option 2 regarding IP address allocation:)

[0047] Action 1. From UE-NAS to UE-OS: The UE NAS layer transmits an initial NAS message to the UE OS layer.

[0048] Action 2. From UE-OS to UE-AS: The UE OS layer transfers the initial NAS message to the UE AS layer.

[0049] Action 3. From UE-AS to RAN: The UE AS layer starts the RRC connection establishment procedure by transmitting an RRC setup request message to the RAN.

[0050] Action 4. From RAN to UE-AS: The RAN transmits an RRC setup response message to the UE AS layer.

[0051] Action 5. From UE-AS to UE-OS: The UE AS layer sends an RRC successful configuration indication to the UE OS layer, whereby the UE OS layer can request IP address allocation.

[0052] Action 6a. From UE-OS to UE-AS: The UE OS layer transmits an IP address request to the UE AS layer. The IP address request can be, for example, a DHCP (Dynamic Host Configuration Protocol) request message.

[0053] Action 6b. From UE-AS to RAN: The IP address request received from the UE OS layer can be included, for example, in an RRC UL (Uplink) information transfer message. In some implementations, the IP address request can be included in a UL information transfer message with an indication, for example, that the request is for an RRC connection and does not include any NAS payload.

[0054] Action 7. RAN: The RAN allocates an IP address for the UE.

[0055] Action 8a. From RAN to UE-AS: The RAN sends the allocated IP address information to the UE AS layer. The allocated IP address information can be, for example, a DHCP response message. The allocated IP address information can be included, for example, in an RRC DL (Downlink) information transfer message. In some implementations, the allocated IP address information can be included in a DL information transfer message with an indication, for example, that the response is for an RRC connection and does not include any NAS payload. The IP address information can include at least one of an IP address, port number, subnet mask, default gateway, DNS (Domain Name System) server, etc.

[0056] Action 8b. From UE-AS to UE-OS: The UE AS layer transfers the allocated IP address information to the UE OS layer. After Action 8b, Action 9 is performed.

[0057] After successful IP address allocation, a transport layer connection can be established. There are many transport layer protocols that can be employed, but TCP is described as an example in the following explanation. However, other implementations are also possible.

[0058] (TCP Connection Establishment:)

[0059] Operation 9a. From UE-OS to UE-AS: The UE OS layer starts the TCP connection establishment procedure by transmitting a TCP connection establishment request to the UE AS layer.

[0060] Operation 9b. From UE-AS to RAN: The TCP connection establishment request can be included, for example, in an RRC UL information transfer message, or in a UL information transfer message with an indication, for example, that the request is for an RRC connection and does not contain any NAS payload.

[0061] Operation 10a. From RAN to UE-AS: The RAN transmits a TCP connection establishment response message to the UE AS layer indicating that a new TCP connection can be established. The TCP connection establishment response message can be included, for example, in an RRC DL information transfer message, or in a DL information transfer message with an indication, for example, that the response is for an RRC connection and does not contain any NAS payload.

[0062] Operation 10b. From UE-AS to UE-OS: The UE AS layer transfers the received TCP connection establishment response message to the UE OS layer.

[0063] Operation 11a. From UE-OS to UE-AS: The UE OS layer transmits a TCP connection establishment positive acknowledgement message to confirm the successful reception of the TCP connection establishment response message from the RAN.

[0064] Action 11b. From UE-AS to RAN: The TCP connection establishment positive acknowledgment message can be included, for example, in the RRC UL information transfer message, or, for example, in a UL information transfer message that indicates that the request is for an RRC connection and contains no NAS payload.

[0065] After successful IP address allocation and TCP connection establishment, the following actions are performed.

[0066] Action 12. From UE-AS to RAN: The UE AS layer sends an RRC setup complete message to the RAN to confirm the successful completion of the RRC connection establishment. The initial NAS message can be piggybacked within the RRC setup complete message and sent to the AMF.

[0067] Action 13a. From UE-AS to UE-OS: The UE AS layer sends an RRC setup complete indication to the UE OS layer.

[0068] Action 13b. From UE-OS to UE-NAS: The UE OS layer transfers the RRC setup complete indication to the UE NAS layer.

[0069] Action 14a. From UE-NAS to UE-OS: The UE NAS layer sends a NAS message to the UE OS layer.

[0070] Action 14b. From UE-OS to UE-AS: The UE OS layer transfers the NAS message to the UE AS layer via the allocated IP address.

[0071] Action 14c. From UE-AS to RAN: The UE AS layer transfers the NAS message to the RAN via the allocated IP address.

[0072] Action 14d. From RAN to AMF: The RAN transfers the received NAS message to the AMF.

[0073] (Exemplary Implementation 3: IP Address Allocation during RRC Connection Resume Procedure)

[0074] This implementation discusses allocating IP addresses during the RRC connection reestablishment procedure. In this implementation for the RRC connection reestablishment procedure, IP address allocation and transport layer connection establishment are similar to those discussed in Exemplary Implementation 2. Specifically, regarding IP address allocation during the RRC connection reestablishment procedure, Operations 1 - 14d as described in Exemplary Implementation 2 are implemented, while the following differences 1) - 4) are applied. The same explanations are omitted, and only differences 1) - 4) are discussed in the following explanations.

[0075] 1) The initial NAS message is replaced by the NAS message.

[0076] 2) The RRC setup request message is replaced by the RRC resume request message.

[0077] 3) The RRC setup message can be replaced by the RRC resume message.

[0078] 4) The RRC setup complete message can be replaced by the RRC resume complete message.

[0079] (Exemplary Implementation 4: IP Address Allocation during Handover Procedure)

[0080] Figure 5 shows an exemplary procedure for IP address allocation during the handover procedure based on some implementations of the disclosed technology.

[0081] Operation 1. From Source RAN to Target RAN: The source RAN determines to hand over the UE to the target RAN based on measurement reports and RRM (Radio Resource Management) information. The source RAN issues a handover request message to the target RAN and passes a transparent RRC container with the information necessary to prepare for the handover on the target side. The information includes an IP address request indication or an indication showing the UE capability to support NAS over IP.

[0082] Operation 2. Target RAN: The target RAN allocates an IP address for the UE.

[0083] Operation 3. From the target RAN to the source RAN: The target RAN prepares for the handover, sends a handover request positive response to the source RAN, and the handover request positive response shall include a transparent container to be sent to the UE as an RRC message for performing the handover. The information includes the IP address information allocated to the UE. The IP address information can include an IP address, a port number, a subnet mask, a default gateway, a DNS (Domain Name System) server, etc.

[0084] Operation 4. From the source RAN to the UE: The source RAN sends an RRC reconfiguration message to the UE that includes information required to access the target access network. The information includes the target access network information and the allocated IP address information.

[0085] Similarly, as in Example 2, here, TCP is taken as an example of the transport layer protocol.

[0086] Operation 5. A TCP connection is established between the UE and the target RAN. In this implementation, TCP is described as an example of a transport layer protocol, but other implementations are also possible. Operation 5 can proceed here in the same way as Operations 9a - 11b of Exemplary Implementation 2.

[0087] Operation 6. The UE synchronizes with the target access network and completes the RRC handover procedure by sending an RRC reconfiguration complete message to the target RAN.

[0088] Operation 7. The UE sends NAS messages to the target RAN via the allocated IP address.

[0089] (Exemplary Implementation 5: IP Address Release during the RRC Connection Release Procedure)

[0090] Figure 6 shows an exemplary procedure for IP address release during an RRC connection release procedure based on some implementations of the disclosed technology. In this implementation, TCP is described as an example of a transport layer protocol, although other implementations are possible.

[0091] Operation 1. The TCP connection established between the UE and the RAN is released. Steps 9a - 11b in Example 2 are the three-way handshake for TCP connection establishment. In this example, four waves are used for TCP connection release.

[0092] Operation 2. From the RAN to the UE-AS: The RAN initiates an RRC connection release procedure to release the RRC connection between the UE and the RAN. The RAN sends an RRC release message to the UE AS layer. The RRC release message includes an IP address release indication. The RAN releases the IP address allocated for the UE.

[0093] Operation 3. From the UE-AS to the UE-OS: The UE AS layer transfers the IP address release indication to the UE OS layer. The UE releases the IP address allocated for the UE.

[0094] FIG. 7 is a block diagram of an exemplary implementation of a wireless communication device 1200. The methods described herein may be implemented by the device 1200. In some embodiments, the device 1200 can be a base station or a network device of a wireless network. In some embodiments, the device 1200 can be a user device (e.g., a wireless device or a user equipment UE). The device 1200 includes one or more processors, such as a processor electronics 1210, a transceiver circuitry 1215, and one or more antennas 1220 for transmitting and receiving wireless signals. The device 1200 may include a memory 1205 that can be used to store data and instructions used by the processor electronics 1210. The device 1200 may also include an additional network interface to one or more core networks or additional equipment of a network operator. This additional network interface, not explicitly shown in the figure, can be wired (e.g., fiber or Ethernet (registered trademark)) or wireless.

[0095] FIG. 8 depicts an example of a wireless communication system 1300 in which various techniques described herein may be implemented. The system 1300 includes a base station 1302 that can have a communication connection to a core network (1312) and a communication connection to a wireless communication medium 1304 for communicating with one or more user devices 1306. The user devices 1306 can be smartphones, tablets, machine-to-machine communication devices, Internet of Things (IoT) devices, etc.

[0096] Some preferred embodiments may include the following solutions.

[0097] 1. A method of wireless communication (e.g., method 900 as shown in FIG. 9), the method comprising: transmitting, by a user device, a first message to an access network to request an Internet Protocol (IP) address to be used for wireless communication (910); and receiving, by the user device, from the access network, IP address information including the IP address allocated to the user device (920).

[0098] 2. After receiving the IP address information, the method according to solution 1 further comprising: transmitting, by the user device, a second message to the access network to request establishment of a transport layer connection; and receiving, by the user device, from the access network, a connection establishment response message indicating establishment of the transport layer connection.

[0099] 3. The method according to solution 1, wherein the first message is a Radio Resource Control (RRC) setup request message or an RRC resume request message including a first indication for requesting an IP address or a second indication for indicating device capabilities supporting a non-access stratum (NAS) via IP.

[0100] 4. The method according to solution 1, wherein the first message is an RRC uplink (UL) information transfer message including a Dynamic Host Configuration Protocol (DHCP) request message.

[0101] 5. The method according to solution 1, wherein the first message is an uplink (UL) information transfer message including a Dynamic Host Configuration Protocol (DHCP) request and an indication indicating that the request is for an RRC connection and does not include any non-access stratum (NAS) payload.

[0102] 6. The method according to solution 1, wherein the IP address information is included in an RRC setup response message, an RRC resume response message, or an RRC reconfiguration message.

[0103] 7. The IP address information is included in the DHCP response message included in the RRC downlink (DL) information transfer message, or the IP address information is included in the DHCP response message included in the DL information transfer message that indicates that the response is for an RRC connection and does not include any NAS payload, as described in Solution 1.

[0104] 8. The IP address information further includes a port number, a subnet mask, a default gateway, and DNS server information, as described in any of Solutions 1-7.

[0105] 9. The second message is included in the RRC UL information transfer message, or is included in the UL information transfer message with an indication that the request is for an RRC connection and does not include any NAS payload, as described in Solution 2.

[0106] 10. The connection establishment response message is included in the RRC downlink (DL) information transfer message, or is included in the DL information transfer message that includes an indication that the response is for an RRC connection and does not include any NAS payload, as described in Solution 2.

[0107] 11. Further includes transmitting a connection establishment positive response message to the access network in response to receiving the connection establishment response message, and the connection establishment positive response message is included in the RRC UL information transfer message, or is included in the UL information transfer message with an indication that the corresponding request is for an RRC connection and does not include any NAS payload, as described in Solution 2.

[0108] 12. Further includes transmitting a NAS message to the access network via the IP address, as described in Solution 1.

[0109] 13. Further comprising receiving a reconfiguration message including target access network information, wherein the target access network information enables the user device to access a target access network and another IP address information allocated by the target access network, the method according to Solution 1.

[0110] 14. Further comprising establishing a target access network with the transport layer connection and transmitting a NAS message to the target access network via another IP address allocated by the target access network, the method according to Solution 13.

[0111] 15. Further comprising receiving an RRC release message including an instruction for releasing an IP address from an access network and releasing the IP address in response to the reception of the RRC release message, the method according to Solution 1.

[0112] 16. A method of wireless communication (e.g., Method 1000 as shown in FIG. 10), the method comprising receiving (1010) by an access network a first message for requesting an Internet Protocol (IP) address to be used for wireless communication, allocating (1020) by the access network an IP address to the user device, and transmitting (1030) by the access network to the user device IP address information including the IP address allocated to the user device.

[0113] 17. After transmitting the IP address information, further comprising receiving by the access network from the user device a second message for requesting establishment of a transport layer connection and transmitting by the access network to the user device a connection establishment response message indicating establishment of the transport layer connection, the method according to Solution 16.

[0114] 18. The method according to Solution 16, wherein the first message is an RRC setup request message or an RRC resume request message including a first instruction for requesting an IP address or a second instruction for indicating device capabilities to support the NAS via the IP.

[0115] 19. The method according to Solution 16, wherein the first message is an RRC uplink (UL) information transfer message including a Dynamic Host Configuration Protocol (DHCP) request message.

[0116] 20. The method according to Solution 16, wherein the first message is an uplink (UL) information transfer message including a Dynamic Host Configuration Protocol (DHCP) request and an instruction indicating that the request is for an RRC connection and does not include any NAS payload.

[0117] 21. The method according to Solution 16, wherein the IP address information is included in an RRC setup response message, an RRC resume response message, or an RRC reconfiguration message.

[0118] 22. The method according to Solution 16, wherein the IP address information is included in a DHCP response message included in an RRC downlink (DL) information transfer message, or the IP address information is included in a DHCP response message included in a DL information transfer message including an instruction indicating that the response is for an RRC connection and does not include any NAS payload.

[0119] 23. The method according to any one of Solutions 16-22, wherein the IP address information further includes a port number, a subnet mask, a default gateway, and DNS server information.

[0120] 24. The method according to Solution 17, wherein the second message is included in an RRC UL information transfer message, or is included in a UL information transfer message accompanied by an instruction indicating that the request is for an RRC connection and does not include any NAS payload.

[0121] 25. The connection establishment response message is included in the RRC downlink (DL) information transfer message, or the method described in Solution 17, which is included in the DL information transfer message containing an indication that the response is for the RRC connection and does not contain any NAS payload.

[0122] 26. Further including receiving, from the user device, a connection establishment positive response message in response to transmitting the connection establishment response message, where the connection establishment positive response message is included in the RRC UL information transfer message, or the method described in Solution 17, which is included in the UL information transfer message accompanied by an indication that the corresponding message is for the RRC connection and does not contain any NAS payload.

[0123] 27. The method described in Solution 16, further including receiving, from the user device, a NAS message via an IP address.

[0124] 28. The method described in Solution 16, further including transmitting, by the access network, to the user device, a reconfiguration message including target access network information that enables the user device to access the target access network and another IP address information allocated by the target access network.

[0125] 29. The first message corresponds to a handover request message from the source access network. The method further includes transmitting, by the access network, to the source access network, a handover request positive response message including the target access network information and the IP address information allocated for the user device; establishing a transport layer connection between the user device and the access network; and receiving, by the access network, from the user device, a NAS message via the IP address allocated by the access network. This is the method described in Solution 16.

[0126] The method according to Solution 16, further comprising transmitting, by an access network, an RRC release message including an instruction for releasing an IP address to a user device.

[0127] 31. A wireless communication device, comprising a processor configured to implement the method shown in any of the above solutions.

[0128] 32. A computer storage medium storing code, wherein the code causes a processor to implement the method shown in any of the above solutions when executed by the processor.

[0129] The disclosed and other embodiments, modules, and functional operations described in this book can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware including the structures disclosed in this book and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., as one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, a data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that generates a machine-readable propagated signal, or a combination of one or more of them. The term "data processing apparatus" includes, by way of example, all apparatus, devices, and machines for processing data, including programmable processors, computers, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program, e.g., code comprising processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal generated to encode information for transmission to a suitable receiver device

[0130] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiler-type or interpreter-type languages, and it can be deployed in any form, as a stand-alone program or as modules, components, subroutines, or other units suitable for use within a computer environment. A computer program does not necessarily correspond to a file in a file system. The program can be stored in a part of a file that holds other programs or data (such as one or more scripts stored in a markup language document), in a single file dedicated to the program, or in multiple integrated files (such as files that store one or more modules, subprograms, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers located on one site or distributed across multiple sites and interconnected by a communication network.

[0131] The processes and logical flows described in this specification can be implemented by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logical flows can also be implemented by, and the apparatus can also be implemented as, special purpose logic circuitry, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit).

[0132] Processors suitable for the execution of a computer program include, by way of example, both general and special microprocessors, as well as any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory, or both. Essential elements of a computer are a processor for executing the instructions, and one or more memory devices for storing the instructions and data. Generally, a computer will also include, or be operatively coupled to receive from and transfer data to, one or more mass storage devices for storing data, such as magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include, by way of example, all forms of non-volatile memory, media, and memory devices including semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices, magnetic disks, such as internal hard disks or removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0133] This book contains many details, but these should be construed as descriptions of features specific to particular embodiments rather than as limitations to the scope of the claimed invention or what may be claimed. Certain features described in the context of separate embodiments herein can also be implemented in a combination in a single embodiment. Conversely, the various features described in the context of a single embodiment can also be implemented separately in multiple embodiments or in any suitable sub-combination. Further, although a feature may be described above as acting in a certain combination and may even be initially claimed as such, one or more features from the claimed combination can in some cases be deleted, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination. Similarly, although operations are depicted in the drawings in a particular order, that should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all of the illustrated operations be performed, to achieve a desirable result.

[0134] Only some examples and implementations are disclosed. Variations, modifications, and extensions to the disclosed examples and implementations and other implementations can be made based on what is disclosed.

Claims

Claim 1 A method of wireless communication, the method comprising: transmitting, by a user device, a first message to an access network to request an Internet Protocol (IP) address to be used for the wireless communication; receiving, by the user device, from the access network, IP address information including the IP address allocated to the user device; A method comprising the above. Claim 2 After receiving the IP address information, transmitting, by the user device, a second message to the access network to request establishment of a transport layer connection; receiving, by the user device, from the access network, a connection establishment response message indicating establishment of the transport layer connection; The method according to claim 1, further comprising the above. Claim 3 The first message is a Radio Resource Control (RRC) setup request message or an RRC resume request message, and the RRC setup request message or the RRC resume request message includes a first indication for requesting the IP address or a second indication for indicating device capabilities for supporting a non-access stratum (NAS) via the IP. The method according to claim 1. Claim 4 The first message is an RRC uplink (UL) information transfer message including a Dynamic Host Configuration Protocol (DHCP) request message. The method according to claim 1. Claim 5 The first message is an uplink (UL) information transfer message, and the UL information transfer message includes a Dynamic Host Configuration Protocol (DHCP) request and an indication indicating that the request is for an RRC connection and does not include any non-access stratum (NAS) payload. The method according to claim 1. Claim 6 The IP address information is included in an RRC setup response message, an RRC resume response message, or an RRC reconfiguration message. The method according to claim 1. Claim 7 The IP address information is included in a DHCP response message included in an RRC downlink (DL) information transfer message, or the IP address information is included in a DHCP response message included in a DL information transfer message that also includes an indication indicating that the response is for an RRC connection and does not include any NAS payload. The method according to claim 1. Claim 8 The method according to any one of claims 1-7, wherein the IP address information further includes a port number, a subnet mask, a default gateway, and DNS server information. Claim 9 The method according to claim 2, wherein the second message is included in an RRC UL information transfer message or is included in a UL information transfer message accompanied by an indication indicating that the request is for an RRC connection and does not include any NAS payload. Claim 10 The method according to claim 2, wherein the connection establishment response message is included in an RRC downlink (DL) information transfer message or is included in a DL information transfer message including an indication indicating that the response is for an RRC connection and does not include any NAS payload. Claim 11 The method according to claim 2, further comprising transmitting a connection establishment positive response message to the access network in response to receiving the connection establishment response message, wherein the connection establishment positive response message is included in an RRC UL information transfer message or is included in a UL information transfer message accompanied by an indication indicating that the corresponding request is for an RRC connection and does not include any NAS payload. Claim 12 The method according to claim 1, further comprising transmitting a NAS message to the access network via the IP address. Claim 13 The method according to claim 1, further comprising receiving a reconfiguration message including target access network information, wherein the target access network information enables the user device to access a target access network and another IP address information allocated by the target access network. Claim 14 establishing a transport layer connection with the target access network; transmitting a NAS message to the target access network via the other IP address allocated by the target access network; The method according to claim 13, further comprising. Claim 15 receiving an RRC release message including an indication for releasing the IP address from the access network; releasing the IP address in response to receiving the RRC release message; The method according to claim 1, further comprising. Claim 16 A method of wireless communication, the method comprising: Receiving, by an access network, a first message for requesting an Internet Protocol (IP) address to be used for the wireless communication; Allocating, by the access network, the IP address to the user device; Transmitting, by the access network, to the user device, IP address information including the IP address allocated to the user device A method comprising the above.

17. After transmitting the IP address information, Receiving, by the access network, from the user device, a second message for requesting establishment of a transport layer connection; Transmitting, by the access network, to the user device, a connection establishment response message indicating establishment of a transport layer connection The method according to claim 16, further comprising the above.

18. The first message is an RRC setup request message or an RRC resume request message, and the RRC setup request message or the RRC resume request message includes a first indication for requesting the IP address, or a second indication for indicating device capabilities for supporting NAS via IP. The method according to claim 16.

19. The first message is an RRC uplink (UL) information transfer message including a Dynamic Host Configuration Protocol (DHCP) request message. The method according to claim 16.

20. The first message is an uplink (UL) information transfer message, and the UL information transfer message includes a Dynamic Host Configuration Protocol (DHCP) request and an indication indicating that the request is for an RRC connection and does not include any NAS payload. The method according to claim 16.

21. The IP address information is included in an RRC setup response message, an RRC resume response message, or an RRC reconfiguration message. The method according to claim 16.

22. The method according to claim 16, wherein the IP address information is included in a DHCP response message included in an RRC downlink (DL) information transfer message, or the IP address information is included in a DHCP response message included in a DL information transfer message including an indication indicating that the response is for an RRC connection and does not include any NAS payload.

23. The method according to any one of claims 16 - 22, wherein the IP address information further includes a port number, a subnet mask, a default gateway, and DNS server information.

24. The method according to claim 17, wherein the second message is included in an RRC UL information transfer message, or is included in a UL information transfer message accompanied by an indication indicating that the request is for an RRC connection and does not include any NAS payload.

25. The method according to claim 17, wherein the connection establishment response message is included in an RRC downlink (DL) information transfer message, or is included in a DL information transfer message including an indication indicating that the response is for an RRC connection and does not include any NAS payload.

26. The method according to claim 17, further comprising receiving, from the user device, a connection establishment positive response message in response to transmitting the connection establishment response message, wherein the connection establishment positive response message is included in an RRC UL information transfer message, or is included in a UL information transfer message accompanied by an indication indicating that the corresponding message is for an RRC connection and does not include any NAS payload.

27. The method according to claim 16, further comprising receiving, from the user device, a NAS message via the IP address.

28. The method according to claim 16, further comprising transmitting, by the access network, a reconfiguration message to the user device, wherein the reconfiguration message includes target access network information that enables the user device to access a target access network and another IP address information allocated by the target access network.

29. The first message corresponds to a handover request message from a source access network, and the method Transmitting, by the access network, a handover request positive response message including the target access network information and the IP address information allocated for the user device to the source access network; Establishing a transport layer connection between the user device and the access network; Receiving, by the access network, a NAS message from the user device via the IP address allocated by the access network; The method according to claim 16, further comprising the steps of:

30. The method according to claim 16, further comprising transmitting, by the access network, an RRC release message including an instruction for releasing the IP address to the user device.

31. A wireless communication device comprising a processor configured to implement the method according to any of the above claims.

32. A computer storage medium storing code, which, when executed by a processor, causes the processor to implement the method according to any of the above claims.

Images