US20070261029A1 - Methods and systems for testing a software program - Google Patents
Methods and systems for testing a software program Download PDFInfo
- Publication number
- US20070261029A1 US20070261029A1 US11/506,102 US50610206A US2007261029A1 US 20070261029 A1 US20070261029 A1 US 20070261029A1 US 50610206 A US50610206 A US 50610206A US 2007261029 A1 US2007261029 A1 US 2007261029A1
- Authority
- US
- United States
- Prior art keywords
- software program
- type
- testing
- textual input
- static
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
- G06F9/4491—Optimising based on receiver type
Definitions
- the software program generally supports one or more types (data types).
- a type contains a set of values and some operations that may be performed on the set of values. Examples of the types may include, but are not limited to, char, signed char, unsigned char, int, long, double, float, struct, and union.
- types used by the software program are tested. In addition to testing the types, algorithms used by the software program, correctiveness of the software program and ability of the software program to complete within a deadline are also tested. A software program is tested using a test tool.
- a test tool used for testing the software program may not be able to communicate directly with the software program. Therefore, for testing each type used by the software program an adaptation layer has to be created.
- the adaptation layer is created manually to enable compatibility and communication between the test tool and the software program.
- conventional systems of testing are used for protocol programs, like, for example, the 802.11 protocol program.
- An embodiment provides a method and system for testing 802.16 protocol software programs.
- Embodiments described below include methods and systems for testing a software program.
- the method of an embodiment includes receiving a textual input for testing at least one type used by the software program.
- the textual input is pre-linked to the at least one static type.
- the method includes creating a dynamic type based on the textual input in a dynamically typed language.
- the dynamic type is then populated with a predefined set of test vectors and is passed on to the software program. Thereafter, the software program is executed by using the dynamic type.
- the at least one static type is invoked when the software program is executed using the dynamic type.
- FIG. 1 is a flowchart for testing a software program, in accordance with an embodiment.
- FIG. 2 is a flowchart for testing a software program, in accordance with another embodiment.
- FIG. 3 is a block diagram showing a device for testing a software program, in accordance with an embodiment of the invention.
- Various embodiments described below provide methods and systems of testing a software program using a dynamically typed language.
- types in the software program are tested and the constraints for each type are applied.
- algorithms used in the software program may also be tested.
- Types that are created before compilation are called static types and the types that are created during the runtime are called dynamic types.
- the static types are created in statically typed languages. Examples of the statically typed language may include, but are not limited to, C, C++, Java, ML and Haskell.
- the dynamic types are created in dynamically typed languages. Examples of the dynamically typed language may include, but are not limited to, Python, Ruby, Smalltalk, Perl, and Lisp.
- FIG. 1 is a flowchart for testing a software program, in accordance with an embodiment.
- the software program is written in a statically typed language. Therefore, the software program uses one or more static types.
- the software program may be a protocol software program.
- a protocol software program enables a standard format for data exchange between data processing systems in a communication network.
- the standard format for example, may include a predetermined format for error checking, and a method used for compression of data.
- the protocol software program is an 802.16 protocol software program, but the embodiment is not so limited.
- a textual input is received for testing the software program using one or more static types.
- the textual input is received in a dynamically type language.
- the textual input is pre-linked to one or more static types, such that a static type can be invoked by using a corresponding textual input.
- the textual input is pre-linked to a static type through an import definition of the static type. This is further explained below in conjunction with FIG. 2 .
- a dynamic type is created based on the textual input in the dynamically typed language.
- the dynamic type language may be a scripting language. Examples of the scripting language may include, but are not limited to, ColdFusion, Hypertext Preprocessor (PHP), Pike, Python, Ruby and scheme.
- the software program is executed using the dynamic type as input.
- the dynamic type is created based on the textual input that is pre-linked to a static type, therefore, the static type is invoked when the software program is executed using the dynamic type.
- the invoking of the static type enables it's testing. As a result, one or more static types are tested without creating an adaptation layer.
- a software program is tested by using Python as the dynamically typed language.
- the software program includes two static types, i.e., static type ‘T1’ and static type ‘T2’.
- static type ‘T1’ i.e., static type ‘T1’
- static type ‘T2’ i.e., static type ‘T1’
- T2 static type
- TypeToTest ‘T1’
- This textual input is pre-linked to the static type T 1 through an import definition of the static type T 1 , such that this textual input can be used to invoke the static type T 1 .
- a dynamic type P is created based on the textual input in the dynamic type language.
- the dynamic type P is:
- the dynamic type P is populated with a predefined set of test vectors and passed on to the software program.
- the software program is then executed using the dynamic type P.
- the static type T 1 is invoked when the software program is executed.
- FIG. 2 is a flowchart for testing a software program, in accordance with another embodiment.
- an import definition of one or more static types used by the software program is created.
- the import definition of an embodiment is created in the dynamically typed language.
- the import definition created on the dynamic type language provides a reference/pointer to the at least one static type.
- the import definition is pre-linked to a textual input by predefining textual input for the import definition in the system.
- the import definition is created by a Simplified Wrapper and Interface Generator (SWIG).
- SWIG creates bindings (import definitions) on a scripting language from a software program written in static typed languages. These bindings can then be used from the scripting language to use the software program written in static typed languages.
- a textual input is received. As the textual input is pre-linked to the import definition, it can be used to access one or more static type through the import definition.
- a dynamic type is created based on the textual input at 206 .
- the software program is executed using the dynamic type.
- the dynamic type is created based on the textual input that is pre-linked to the import definition. Further, the import definition provides a reference or pointer to the at least one static type. Therefore, executing the software program by using the dynamic type invokes one or more static types and enables testing of one or more static types.
- FIG. 3 is a block diagram showing components of a device 300 for testing a software program, in accordance with an embodiment.
- Device 300 for testing a software program includes may be a test tool, but is not limited to a test tool.
- Device 300 includes an input receiver 302 and a type generator 304 .
- Input receiver 302 receives a textual input for testing the software program using the at least one static type. This has been explained in detail in conjunction with FIG. 1 and FIG. 2 above.
- the textual input is pre-linked to one or more static types.
- the textual input may be entered in a markup language.
- the markup language is Extensible Markup Language (XML) but is not limited to XML.
- XML Extensible Markup Language
- Examples of the markup language other than XML may include, but are not limited to, Extensible Binary Meta Language (EBML), Generalized Markup language (GML), Standard Generalized Markup Language (SGML), and (Hyper Text Markup Language) HTML.
- EBML Extensible Binary Meta Language
- GML Generalized Markup language
- SGML Standard Generalized Markup Language
- HTML Hyper Text Markup Language
- the textual input may also be entered in a text file or an excel worksheet. Thereafter, a dynamic type is created based on the textual input in a dynamically typed language by type generator 304 . This has been explained in conjunction with FIG. 1 .
- device 300 includes a binder 306 .
- the SWIG includes binder 306 .
- Binder 306 creates an import definition of the at least one static type on the dynamically typed language.
- the textual input received by input receiver 302 is pre-linked to the import definition by binder 306 .
- the textual input can be used to invoke the at least one static type and test them.
- the input receiver 302 , type generator 304 , and/or binder 306 of device 300 can be coupled and/or connected in any of a variety of combinations as appropriate to a system that includes device 300 , and are thus not limited to the configuration shown in FIG. 3 .
Abstract
Description
- This application claims priority to and incorporates by reference India provisional application serial number 695/MUM/2006 filed on May 4, 2006, titled “Dynamic Typing”
- The invention generally relates to testing software programs. More specifically, the invention relates to methods and systems for testing a software program using a language that supports dynamic typing.
- The software program generally supports one or more types (data types). A type contains a set of values and some operations that may be performed on the set of values. Examples of the types may include, but are not limited to, char, signed char, unsigned char, int, long, double, float, struct, and union. To test the software program, types used by the software program are tested. In addition to testing the types, algorithms used by the software program, correctiveness of the software program and ability of the software program to complete within a deadline are also tested. A software program is tested using a test tool.
- In commercial third party testing tools, a test tool used for testing the software program may not be able to communicate directly with the software program. Therefore, for testing each type used by the software program an adaptation layer has to be created. The adaptation layer is created manually to enable compatibility and communication between the test tool and the software program. Additionally, conventional systems of testing are used for protocol programs, like, for example, the 802.11 protocol program.
- There is therefore a need for methods and systems for testing a software program that does not require creating an adaptation layer for each type used by the software program. Further, there is a need for methods and systems for testing protocol programs, like, for example, 802.16 protocol software programs.
- An embodiment provides a method and system of testing a software program that does not require an adaptation layer.
- An embodiment provides a method and system for testing 802.16 protocol software programs.
- Embodiments described below include methods and systems for testing a software program. The method of an embodiment includes receiving a textual input for testing at least one type used by the software program. The textual input is pre-linked to the at least one static type. The method includes creating a dynamic type based on the textual input in a dynamically typed language. The dynamic type is then populated with a predefined set of test vectors and is passed on to the software program. Thereafter, the software program is executed by using the dynamic type. The at least one static type is invoked when the software program is executed using the dynamic type.
- A more complete appreciation of the present invention is provided by reference to the following detailed description when considered in conjunction with the accompanying drawings in which reference symbols indicate the same or similar components, wherein:
-
FIG. 1 is a flowchart for testing a software program, in accordance with an embodiment. -
FIG. 2 is a flowchart for testing a software program, in accordance with another embodiment. -
FIG. 3 is a block diagram showing a device for testing a software program, in accordance with an embodiment of the invention. - Various embodiments described below provide methods and systems of testing a software program using a dynamically typed language. To test a software program, types in the software program are tested and the constraints for each type are applied. In addition to testing types in the software program, algorithms used in the software program may also be tested. Types that are created before compilation are called static types and the types that are created during the runtime are called dynamic types. The static types are created in statically typed languages. Examples of the statically typed language may include, but are not limited to, C, C++, Java, ML and Haskell. The dynamic types are created in dynamically typed languages. Examples of the dynamically typed language may include, but are not limited to, Python, Ruby, Smalltalk, Perl, and Lisp. Methods of testing a software program using a dynamically typed language in accordance with various embodiments are explained hereinafter.
-
FIG. 1 is a flowchart for testing a software program, in accordance with an embodiment. The software program is written in a statically typed language. Therefore, the software program uses one or more static types. The software program may be a protocol software program. A protocol software program enables a standard format for data exchange between data processing systems in a communication network. The standard format, for example, may include a predetermined format for error checking, and a method used for compression of data. In an embodiment, the protocol software program is an 802.16 protocol software program, but the embodiment is not so limited. - At 102, a textual input is received for testing the software program using one or more static types. The textual input is received in a dynamically type language. The textual input is pre-linked to one or more static types, such that a static type can be invoked by using a corresponding textual input. The textual input is pre-linked to a static type through an import definition of the static type. This is further explained below in conjunction with
FIG. 2 . - At 104, a dynamic type is created based on the textual input in the dynamically typed language. The dynamic type language may be a scripting language. Examples of the scripting language may include, but are not limited to, ColdFusion, Hypertext Preprocessor (PHP), Pike, Python, Ruby and scheme. As a result of the creation of the dynamic type based on the textual input, corresponding static type can be directly accessed from the dynamically typed language. The dynamic type is then populated with a predefined set of test vectors and is passed on to the software program.
- At 106, the software program is executed using the dynamic type as input. As the dynamic type is created based on the textual input that is pre-linked to a static type, therefore, the static type is invoked when the software program is executed using the dynamic type. The invoking of the static type enables it's testing. As a result, one or more static types are tested without creating an adaptation layer.
- As an example of the method described above, a software program is tested by using Python as the dynamically typed language. The software program includes two static types, i.e., static type ‘T1’ and static type ‘T2’. To test these static types a textual input is received in Python. In this example, the textual input is:
- TypeToTest=‘T1’;
- This textual input is pre-linked to the static type T1 through an import definition of the static type T1, such that this textual input can be used to invoke the static type T1. Further, a dynamic type P is created based on the textual input in the dynamic type language. The dynamic type P is:
- P=eval (TypeToTest)( );
- Thereafter, the dynamic type P is populated with a predefined set of test vectors and passed on to the software program. The software program is then executed using the dynamic type P. Thereafter, the static type T1 is invoked when the software program is executed.
-
FIG. 2 is a flowchart for testing a software program, in accordance with another embodiment. At 202, an import definition of one or more static types used by the software program is created. The import definition of an embodiment is created in the dynamically typed language. The import definition created on the dynamic type language provides a reference/pointer to the at least one static type. The import definition is pre-linked to a textual input by predefining textual input for the import definition in the system. The import definition is created by a Simplified Wrapper and Interface Generator (SWIG). The SWIG creates bindings (import definitions) on a scripting language from a software program written in static typed languages. These bindings can then be used from the scripting language to use the software program written in static typed languages. At 204, a textual input is received. As the textual input is pre-linked to the import definition, it can be used to access one or more static type through the import definition. - Further, a dynamic type is created based on the textual input at 206. At 208, the software program is executed using the dynamic type. The dynamic type is created based on the textual input that is pre-linked to the import definition. Further, the import definition provides a reference or pointer to the at least one static type. Therefore, executing the software program by using the dynamic type invokes one or more static types and enables testing of one or more static types.
-
FIG. 3 is a block diagram showing components of adevice 300 for testing a software program, in accordance with an embodiment.Device 300 for testing a software program includes may be a test tool, but is not limited to a test tool.Device 300 includes aninput receiver 302 and atype generator 304.Input receiver 302 receives a textual input for testing the software program using the at least one static type. This has been explained in detail in conjunction withFIG. 1 andFIG. 2 above. The textual input is pre-linked to one or more static types. The textual input may be entered in a markup language. In an embodiment the markup language is Extensible Markup Language (XML) but is not limited to XML. Examples of the markup language other than XML, may include, but are not limited to, Extensible Binary Meta Language (EBML), Generalized Markup language (GML), Standard Generalized Markup Language (SGML), and (Hyper Text Markup Language) HTML. The textual input may also be entered in a text file or an excel worksheet. Thereafter, a dynamic type is created based on the textual input in a dynamically typed language bytype generator 304. This has been explained in conjunction withFIG. 1 . - In an embodiment,
device 300 includes abinder 306. In various embodiments, the SWIG includesbinder 306.Binder 306 creates an import definition of the at least one static type on the dynamically typed language. Further, the textual input received byinput receiver 302 is pre-linked to the import definition bybinder 306. As a result of which, the textual input can be used to invoke the at least one static type and test them. Theinput receiver 302,type generator 304, and/orbinder 306 ofdevice 300 can be coupled and/or connected in any of a variety of combinations as appropriate to a system that includesdevice 300, and are thus not limited to the configuration shown inFIG. 3 . - Various embodiments provide methods and systems for testing software programs without creating adaptation layer for each type used by it. Further, the various embodiments provide methods and systems for testing 802.16 protocol software program.
Claims (11)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/917,414 US8291385B2 (en) | 2006-05-04 | 2010-11-01 | Method and system for testing a software program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
IN695/MUM/2006 | 2006-05-04 | ||
IN695MU2006 | 2006-05-04 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/917,414 Continuation US8291385B2 (en) | 2006-05-04 | 2010-11-01 | Method and system for testing a software program |
Publications (2)
Publication Number | Publication Date |
---|---|
US20070261029A1 true US20070261029A1 (en) | 2007-11-08 |
US7827530B2 US7827530B2 (en) | 2010-11-02 |
Family
ID=38662588
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/506,102 Expired - Fee Related US7827530B2 (en) | 2006-05-04 | 2006-08-17 | Methods and systems for testing a software program |
US12/917,414 Active 2026-12-26 US8291385B2 (en) | 2006-05-04 | 2010-11-01 | Method and system for testing a software program |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/917,414 Active 2026-12-26 US8291385B2 (en) | 2006-05-04 | 2010-11-01 | Method and system for testing a software program |
Country Status (1)
Country | Link |
---|---|
US (2) | US7827530B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8387020B1 (en) * | 2007-07-25 | 2013-02-26 | Google Inc. | Verifying that a method has been implemented for a program written in a dynamic programming language |
US8918772B1 (en) | 2007-07-25 | 2014-12-23 | Google Inc. | Statically analyzing program correctness for a dynamic programming language |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8533689B2 (en) * | 2008-10-10 | 2013-09-10 | The Boeing Company | Method, apparatus and computer program product for creating inter-language interface |
US9075667B2 (en) * | 2009-05-21 | 2015-07-07 | Microsoft Technology Licensing, Llc | Dynamic binding directed by static types |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020072830A1 (en) * | 1998-10-02 | 2002-06-13 | Microsoft Corporation | Dynamic classification of sections of software |
US20050183094A1 (en) * | 1998-10-02 | 2005-08-18 | Microsoft Corporation | Tools and techniques for instrumenting interfaces of units of a software program |
US20050289125A1 (en) * | 2004-06-23 | 2005-12-29 | Oracle International Corporation | Efficient evaluation of queries using translation |
US20060075387A1 (en) * | 2004-10-01 | 2006-04-06 | Brixlogic, Inc. | Graphical XML programming system and engine where XML processing programs are built and represented in a graphical fashion |
US20060242115A1 (en) * | 2005-04-25 | 2006-10-26 | Microsoft Corporation | System and method for an improved type inference |
US20070104130A1 (en) * | 2005-11-04 | 2007-05-10 | Muthaiah Venkatachalam | Uplink throughput for wireless network interfaces |
US20070115951A1 (en) * | 2005-11-22 | 2007-05-24 | Jeyhan Karaoguz | System and method providing location based wireless resource identification |
-
2006
- 2006-08-17 US US11/506,102 patent/US7827530B2/en not_active Expired - Fee Related
-
2010
- 2010-11-01 US US12/917,414 patent/US8291385B2/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020072830A1 (en) * | 1998-10-02 | 2002-06-13 | Microsoft Corporation | Dynamic classification of sections of software |
US20050183094A1 (en) * | 1998-10-02 | 2005-08-18 | Microsoft Corporation | Tools and techniques for instrumenting interfaces of units of a software program |
US20050289125A1 (en) * | 2004-06-23 | 2005-12-29 | Oracle International Corporation | Efficient evaluation of queries using translation |
US20060075387A1 (en) * | 2004-10-01 | 2006-04-06 | Brixlogic, Inc. | Graphical XML programming system and engine where XML processing programs are built and represented in a graphical fashion |
US20060242115A1 (en) * | 2005-04-25 | 2006-10-26 | Microsoft Corporation | System and method for an improved type inference |
US20070104130A1 (en) * | 2005-11-04 | 2007-05-10 | Muthaiah Venkatachalam | Uplink throughput for wireless network interfaces |
US20070115951A1 (en) * | 2005-11-22 | 2007-05-24 | Jeyhan Karaoguz | System and method providing location based wireless resource identification |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8387020B1 (en) * | 2007-07-25 | 2013-02-26 | Google Inc. | Verifying that a method has been implemented for a program written in a dynamic programming language |
US8918772B1 (en) | 2007-07-25 | 2014-12-23 | Google Inc. | Statically analyzing program correctness for a dynamic programming language |
Also Published As
Publication number | Publication date |
---|---|
US20110047530A1 (en) | 2011-02-24 |
US7827530B2 (en) | 2010-11-02 |
US8291385B2 (en) | 2012-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN100483419C (en) | Data format verification method and device | |
CN1794296B (en) | System and method for creating web services from an existing web site | |
US8239839B2 (en) | Asynchrony debugging using web services interface | |
US8479283B2 (en) | Generating security validation code automatically | |
US7278132B2 (en) | Mechanism for automatic synchronization of scripting variables | |
US9471282B2 (en) | System and method for using annotations to automatically generate a framework for a custom javaserver faces (JSF) component | |
US8615750B1 (en) | Optimizing application compiling | |
US8776024B2 (en) | Software application fine-tuning method, system, and corresponding computer program product | |
US20050193291A1 (en) | Application functionality for a test tool for application programming interfaces | |
CN106412086B (en) | Method and system for automatically generating communication code by using protocol description file | |
US20060150200A1 (en) | Interface infrastructure for creating and interacting with web services | |
US7644184B2 (en) | Universal adapter | |
US20080209395A1 (en) | Automatic code replacement | |
US8291385B2 (en) | Method and system for testing a software program | |
US9934029B2 (en) | Annotation driven representational state transfer (REST) web services | |
US20100023644A1 (en) | Inspecting web browser state information from a synchronously-invoked service | |
US8291432B2 (en) | Providing invocation context to IMS service provider applications | |
US20060090155A1 (en) | Methods and apparatus for message oriented invocation | |
US20100318574A1 (en) | Generating references to reusable code in a schema | |
CN113641354A (en) | Service data processing method and device, electronic equipment and storage medium | |
US8156506B2 (en) | Methods and apparatus for message oriented invocation | |
US20050172263A1 (en) | Methods, systems, and computer program products for integrating legacy applications into a platform-independent environment | |
Cok et al. | Practical methods for reasoning about java 8’s functional programming features | |
Kiraly et al. | Analysing RPC and testing the performance of solutions | |
US10606569B2 (en) | Declarative configuration elements |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BECEEM COMMUNICATIONS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IYER, SRIRAM V.;REEL/FRAME:018195/0195 Effective date: 20060810 |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BECEEM COMMUNICATIONS, INC.;REEL/FRAME:025473/0591 Effective date: 20101119 |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees | ||
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20141102 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD., SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 |
|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041712/0001 Effective date: 20170119 |