1. A method for facilitating operations in an unlicensed mobile access network (UMAN), comprising:
establishing a dedicated connection between a mobile station (MS) and the UMAN via a UMA network controller (UNC);
establishing a TCP (transmission control protocol) session between the MS and the UNC;
sending unlicensed mobile access (UMA) radio link control (URLC) messages between the MS and the UNC to facilitate corresponding operations, each URLC message including,
a protocol discriminator; and
a message type via which the message may be identified.
2. The method of claim 1, further comprising:
transferring GPRS (general packet radio service) signaling and SMS (short message service) messages between the MS and UNC using a URCL DATA message, the URLC DATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing data to be transferred.
3. The method of claim 2, wherein the URLC DATA message includes:
a required quality of service IE defining a throughput level used to perform the data transfer operation.
4. The method of claim 2, wherein the URLC DATA message includes:
a requested radio priority IE to request a relative prioritization of the message..
5. The method of claim 2, wherein the URLC DATA message includes:
a temporary logical link identifier (TLLI) IE.
6. The method of claim 2, wherein the URLC DATA message includes:
a packet flow identifier IE containing information identifying a packet flow corresponding to the data transfer.
7. The method of claim 1, wherein the operations include paging the MS for GPRS PS services from the UNC using a URLC-PS-PAGE message, the URLC-PS-PAGE message including a Mobile Identity IE from which the MS can be identified.
8. The method of claim 1, wherein the operations include initiating suspension of GPRS (General Packet Radio Service) by performing operations including:
sending a URLC-SUSPEND-REQ message from the MS to the UNC; and
initiating, at the UNC, GPRS Suspend operations with a core GPRS network supporting GPRS services that is communicatively-coupled to the UNC.
9. The method of claim 1, wherein the operations include resuming GPRS (General Packet Radio Service) for the MS by:
initiating, at the UNC, a GPRS resume procedure with a core GPRS network; and
sending a URR (UMA Radio Resource)-RELEASE message from the UNC to the MS including a GPRS Resumption IE identifying GPRS is to be resumed.
10. The method of claim 1, wherein the operations include performing a downlink flow control procedure between the UNC and the MS by:
detecting downlink flow control conditions for downlink data transfer from the UNC to the MS;
calculating a downlink data rate that may be supported by the downlink flow control conditions; and
sending a URLC-DFC (Downlink Flow Control)-REQ message from the MS to the UNC including an information element specifying a downlink data rate to be employed for the downlink.
11. The method of claim 1, further comprising:
detecting an error in a URLC message sent from a UNC to the MS; and
returning a URLC-STATUS message including a URLC Cause information element containing a code identifying the error.
12. The method of claim 1, further comprising:
wherein the operations include transferring GPRS user data between the MS and the UNC using a URLC UNITDATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the GPRS user data and sent over a UDP (User Datagram Protocol) transport.
13. The method of claim 12, wherein the URLC UNITDATA message is transferred from the MS to the UNC.
14. The method of claim 12, wherein the URLC UNITDATA message includes:
a required quality of service IE defining a throughput level used to perform the data transfer operation.
15. The method of claim 12, wherein the URLC UNITDATA message includes:
a requested radio priority IE to request a relative prioritization of the message.
16. The method of claim 12, wherein the URLC DATA message includes:
a temporary logical link identifier (TLLI) IE.
17. The method of claim 12, wherein the URLC DATA message includes:
a packet flow identifier IE containing information identifying a packet flow corresponding to the data transfer.
18. An unlicensed mobile access (UMA) network controller (UNC) to operate in a UMA network (UMAN) comprising a first radio access network, comprising:
a first network interface comprising an IP (Internet Protocol) Network interface;
a second network interface comprising an Up interface, via which UMA messages are to be transmitted to and received from a mobile station (MS) via an access point communicatively coupled between the MS and the UNC, the Up interface including a plurality of layers implemented over the IP network interface;
a third network interface, via which the UNC may be connected to a core network that is accessible to a second radio access network; and
means for generating andor processing a plurality of UMA radio link control (URLC) messages transmitted over the Up interface to perform corresponding operations,
wherein each of the URLC messages includes a set of basic information elements (IEs) including,
a protocol discriminator;
a skip indicator; and
a message type via which the message may be identified.
19. The UNC of claim 18, further comprising:
means for processing a URCL DATA message sent from an MS to the UNC, the URLC DATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing data to be transferred to the core network via the UNC.
20. The UNC of claim 18, further comprising:
means for generating a URCL DATA message via which data is to be sent to the MS, the URLC DATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the data.
21. The UNC of claim 18, further comprising:
means for processing a URCL UNITDATA message sent from an MS to the UNC, the URLC UNITDATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing data to be transferred to the core network via the UNC and being sent over a UDP (User Datagram Protocol) transport.
22. The UNC of claim 18, further comprising:
means for generating a URCL UNITDATA message via which data is to be sent to the MS, the URLC UNITDATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the data and to be sent over a UDP (User Datagram Protocol) transport.
23. The UNC of claim 18, further comprising:
means for interacting with the core network to process a GPRS PS page request received from the core network; and
means for generating a URLC-PS-PAGE message to page the MS, the URLC-PS-PAGE message including a Mobile Identity identifying the MS.
24. The UNC of claim 18, further comprising:
means for processing a URLC-SUSPEND-REQ message sent from an MS requesting suspension of a URLC transport channel between the UNC and the MS; and
means for interacting with the core network to suspend GPRS (General Packet Radio Service) with the core network.
25. The UNC of claim 18, further comprising:
means for resuming GPRS for the MS by,
initiating, at the UNC, a GPRS resume procedure with a core GPRS network; and
generating and sending a URR (UMA Radio Resource)-RELEASE message from the UNC to the MS including a GPRS Resumption information element identifying GPRS is to be resumed.
26. The UNC of claim 18, further comprising:
means for processing a URLC-DFC (Downlink Flow Control)-REQ message from an MS including an information element specifying a downlink data rate to be employed for a downlink portion of a URLC transport channel between the MS and the UNC; and
means for adjusting the downlink data rate to correspond to the downlink data rate specified in the URLC-DFC-REQ message.
27. The UNC of claim 18, further comprising:
means for detecting an error in a URLC message received from an MS; and
means for generating a URLC-STATUS message including a URLC Cause information element containing a code identifying the error, the URLC-STATUS message to be returned to the MS.
28. A mobile station (MS), comprising:
a first wireless interface, to access a first radio access network;
a second wireless interface, to access a second radio access network comprising an unlicensed mobile access network (UMAN) via an access point (AP) using an unlicensed radio frequency;
an Up interface to communicate with the UMAN via a UMA network controller (UNC) communicatively coupled to the AP via an Internet Protocol (IP) network; and
means for generating andor processing a plurality of UMA radio link control (URLC) messages transmitted over the Up interface to perform corresponding operations,
wherein each of the URLC messages includes a set of basic information elements (IEs) including,
a protocol discriminator;
a skip indicator; and
a message type via which the message may be identified.
29. The mobile station of claim 28, further comprising:
means for processing a URCL DATA message sent to the MS from a UNC, the URLC DATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing data transferred from the core network via the UNC.
30. The mobile station of claim 28, further comprising:
means for generating a URCL DATA message via which data is to be sent to the core network via a UNC, the URLC DATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the data.
31. The mobile station of claim 28, further comprising:
means for processing a URCL UNITDATA message sent to the MS from a UNC, the URLC UNITDATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing data transferred from the core network via the UNC and being sent over a UDP (User Datagram Protocol) transport.
32. The mobile station of claim 28, further comprising:
means for generating a URCL UNITDATA message via which data is to be sent to the core network via a UNC, the URLC UNITDATA message including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the data and to be sent over a UDP (User Datagram Protocol) transport.
33. The mobile station of claim 28, further comprising:
means for generating a URLC-SUSPEND-REQ message to be sent to a UNC requesting suspension of a GPRS service while in dedicated mode.
34. The mobile station of claim 28, further comprising:
means for detecting downlink flow control conditions for downlink data transfer from a UNC to the MS;
means for calculating a downlink data rate that may be supported by the downlink flow control conditions; and
means for generating a URLC-DFC (Downlink Flow Control)-REQ message including an information element specifying a downlink data rate to be employed for the downlink.
35. The mobile station of claim 28, further comprising:
means for detecting an error in a URLC message received from a UNC; and
means for generating a URLC-STATUS message including a URLC Cause information element containing a code identifying the error, the URLC-STATUS message to be returned to the UNC.
36. A machine-readable medium, to provide respective portions of instructions to be executed on a mobile station (MS) and an unlicensed mobile access (UMA) network controller (UNC) to perform operations including:
generating and processing a plurality of unlicensed mobile access (UMA) radio link control (URLC) messages to be transmitted between the MS and the UNC via an access point (AP) communicatively coupled between the MS and the UNC,
wherein each of the URLC messages includes a set of basic information elements (IEs) including,
a protocol discriminator;
a skip indicator; and
a message type via which the message may be identified.
37. The machine-readable medium of claim 36, further providing additional respective portions of instructions to be executed on the MS and the UNC to perform operations including:
sending data from the MS to the UNC using a URCL DATA message, the URLC DATA message generated at the MS and including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the data, the LLC PDU being extracted from the URLC DATA message at the UNC to obtain the data.
38. The machine-readable medium of claim 36, further providing additional respective portions of instructions to be executed on the MS and the UNC to perform operations including:
sending data from the UNC to the MS using a URCL DATA message, the URLC DATA message generated at the UNC and including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the data, the LLC PDU being extracted from the URLC DATA message at the MS to obtain the data.
39. The machine-readable medium of claim 36, further providing additional respective portions of instructions to be executed on the MS and the UNC to perform operations including:
sending data from the MS to the UNC using a URCL UNITDATA message, the URLC UNITDATA message generated at the MS and including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the data and sent over a UDP (User Datagram Protocol) transport, the LLC PDU being extracted from the URLC UNITDATA message at the UNC to obtain the data.
40. The machine-readable medium of claim 36, further providing additional respective portions of instructions to be executed on the MS and the UNC to perform operations including:
sending data from the UNC to the MS using a URCL UNITDATA message, the URLC UNITDATA message generated at the UNC and including an encapsulated Logical Link Control Packet Data Unit (LLC PDU) containing the data and sent over a UDP (User Datagram Protocol) transport, the LLC PDU being extracted from the URLC UNITDATA message at the MS to obtain the data.
41. The machine-readable medium of claim 36, further providing additional instructions to be executed on the UNC to perform operations including:
generating a URLC-PS-PAGE message including a Mobile Identity identifying an MS to be paged; and
sending the URLC-PS-PAGE message to that MS.
42. The machine-readable medium of claim 36, further providing additional respective portions of instructions to be executed on the MS and the UNC to perform operations including:
initiating suspension of GPRS service from the MS by generating a URLC-SUSPEND-REQ message and sending it to the UNC; and
initiating, at the UNC, GPRS (General Packet Radio Service) Suspend operations with a core network.
43. The machine-readable medium of claim 36, further providing additional respective portions of instructions to be executed on the MS and the UNC to perform operations including:
resuming GPRS (General Packet Radio Service) for the MS by,
initiating, at the UNC, a GPRS resume procedure with a core GPRS network; and
generating a URR (UMA Radio Resource)-RELEASE message at the UNC and sending it to the MS, the URR-RELEASE message including a GPRS Resumption information element identifying GPRS is to be resumed.
44. The machine-readable medium of claim 36, further providing additional respective portions of instructions to be executed on the MS and the UNC to perform operations including:
detecting downlink flow control conditions for downlink data transfer from the UNC to the MS;
calculating a downlink data rate that may be supported by the downlink flow control conditions;
sending a URLC-DFC (Downlink Flow Control)-REQ message from the MS to the UNC including an information element specifying a downlink data rate to be employed for the downlink; and
employing the downlink data rate that is specified for the downlink.
45. The machine-readable medium of claim 36, further providing additional respective portions of instructions to be executed on the MS to perform operations including:
detecting an error in a URLC message sent from a UNC to the MS; and
generating a URLC-STATUS message including a URLC Cause information element containing a code identifying the error, the URLC-STATUS message being returned to the UNC.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A device, comprising:
a first substrate with circuitry formed thereon;
a photodiode bonded to the first substrate and electrically connected to the circuitry; and
a contact plug at a pixel border and electrically connected with the circuitry and the photodiode,
wherein the photodiode comprises a first conductive type ion implantation region selectively provided in a crystalline semiconductor layer, and a second conductive type ion implantation region in contact with one side surface of the first conductive type ion implantation region.
2. The device of claim 1, wherein the circuitry comprises one of a 1 transistor CMOS image sensor, a 2 transistor CMOS image sensor, a 3 transistor CMOS image sensor, and a 4 transistor CMOS image sensor.
3. The device of claim 1, wherein a first side surface of the contact plug is electrically contacted with the first conductive type ion implantation region, and a second side surface of the contact plug is insulated by a dielectric.
4. The device of claim 3, comprising an upper electrode electrically contacting the second conductive type ion implantation region.
5. The device of claim 3, comprising a high concentration first conductive type ion implantation region between the first conductive type ion implantation region and the contact plug.
6. The device of claim 1, comprising a high concentration first conductive type ion implantation region between the first conductive type ion implantation region and the contact plug.
7. The device of claim 1, wherein the contact plug comprises at least one of tungsten, a single layer of titanium, and a titaniumtitanium nitride (TiTiN) multilayer structure.
8. A method, comprising:
preparing a first substrate including circuitry and wiring;
preparing a second substrate including a photodiode;
bonding the first substrate and the second substrate to contact the photodiode and a first dielectric;
exposing the photodiode by removing a lower side of the second substrate; and
electrically connecting the wiring to the photodiode,
wherein the photodiode comprises a first conductive type ion implantation region selectively provided in a crystalline semiconductor layer, and a second conductive type ion implantation region in contact with one side surface of the first conductive type ion implantation region.
9. The method of claim 8, wherein the crystalline semiconductor layer comprises a monocrystalline semiconductor layer.
10. The method of claim 8, wherein electrically connecting the wiring to the photodiode comprises forming a contact plug at a pixel boundary.
11. The method of claim 10, wherein a first side surface of the contact plug is electrically contacted with the first conductive type ion implantation region of the photodiode, and a second side surface of the contact plug is insulated by a second dielectric.
12. The method of claim 8, wherein the circuitry comprises one of a 1 transistor CMOS image sensor, a 2 transistor CMOS image sensor, a 3 transistor CMOS image sensor, and a 4 transistor CMOS image sensor.
13. The method of claim 8, comprising providing an upper electrode electrically coupled to the second conductive type ion implantation region.
14. The method of claim 8, comprising forming the first dielectric on the first substrate to selectively contact the wiring, after preparing the first substrate.
15. The method of claim 14, wherein the wiring is electrically coupled to the photodiode by a contact plug formed at a pixel boundary, and a first side surface of the contact plug is electrically coupled to the first conductive type ion implantation region, and a second side surface of the contact plug is insulated by a second dielectric.
16. The method of claim 14, wherein electrically connecting the wiring and the photodiode comprises:
defining a first contact hole to selectively expose the wiring by removing the photodiode and the first dielectric at a pixel boundary;
forming a barrier layer over the first contact hole and the photodiode;
providing a second dielectric over the barrier layer to fill the first contact hole;
defining a second contact hole by removing the second dielectric to expose the barrier layer at a side surface and a side at a bottom surface of the first contact hole;
defining a third contact hole by removing the exposed barrier layer and selectively exposing a side surface of the photodiode and the wiring; and
forming a contact plug to fill the third contact hole.
17. The method of claim 16, wherein the barrier layer comprises a silicon nitride (SiN) layer.
18. The method of claim 16, wherein removing the photodiode and the first dielectric at the pixel boundary comprises performing a wet etch.
19. The method of claim 16, wherein defining the first, second, and third contact holes comprises performing a wet etch.
20. The method of claim 16, wherein the contact plug comprises at least one of tungsten, a single layer of titanium, and a titaniumtitanium nitride (TiTiN) multilayer structure.