DETAILED ACTION
Claims 1-12 are pending.
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 06/26/2025 was filed. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Specification
The lengthy specification has not been checked to the extent necessary to determine the presence of all possible minor errors. Applicant's cooperation is requested in correcting any errors of which applicant may become aware in the specification.
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP §§ 706.02(l)(1) - 706.02(l)(3) for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp.
Claims 1-12 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 6-7, 12-13 and 18 of U.S. Patent No. 12206741. Although the claims at issue are not identical, they are not patentably distinct from each other because followings.
Pending Application
U.S. Patent Number 12,206,741
Claim 1. An apparatus for creating compatible messages between devices, the apparatus comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 1. An apparatus for a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the apparatus comprising circuitry configured to:
receive a first RESTful message comprising a profile for modifying messages in the service, wherein the profile indicates which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes;
store the profile in a resource that can be identified by uniform resource identifier (URI) in the service;
receive a second message from a client application for a target application;
determine a list of applicable profiles stored in one or more resources of the service for modifying the second message; and
apply the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or a new message that is compatible with the target application.
Claim 2. The apparatus according to claim 1, wherein the message is a service layer message.
Claims 6 &18. The apparatus of claim 5, wherein the service is defined as a service layer according to ETSI/oneM2M standards, and the profile is defined as part of the service layer according to the ETSI/oneM2M standards.
Claim 3. The apparatus according to claim 1, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to each profile in the list of profiles, the information associated with the message from the client device comprising one or more of an identifier of the client device, a release of software indicated in the message, a resource type indicated in the message, an operation indicated in the message, and a uniform resource identifier indicated in the message.
Claim 1. … determine a list of applicable profiles stored in one or more resources of the service for modifying the second message; and apply the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 4. A method for creating compatible messages between devices, the method comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 7. A method for a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the method comprising:
receiving a first RESTful message comprising a profile for modifying messages in the service, wherein the profile indicates which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes; storing the profile in a resource that can be identified by uniform resource identifier (URI) in the service; receiving a second message from a client application for a target application; determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and
applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or a new message that is compatible with the target application.
Claim 5. The method according to claim 4, wherein the message is a service layer message.
Claims 12 &18. The method of claim 11, wherein the service is defined as a service layer according to ETSI/oneM2M standards, and the profile is defined as part of the service layer according to the ETSI/oneM2M standards.
Claim 6. The method according to claim 4, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising one or more of an identifier of the client device, a release of software indicated in the message, a resource type indicated in the message, an operation indicated in the message, and a uniform resource identifier indicated in the message.
Claim 7. determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 7. A computer readable storage medium storing computer executable instructions that when executed by a computing device cause said computing device to effectuate operations comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 13. A computer readable storage medium for a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the computer readable storage medium storing computer executable instructions that when executed by one or more computing devices cause said one or more computing devices to effectuate operations comprising:
receiving a first RESTful message comprising a profile for modifying messages in the service, wherein the profile indicates which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes; storing the profile in a resource that can be identified by uniform resource identifier (URI) in the service; receiving a second message from a client application for a target application; determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and
applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or a new message that is compatible with the target application.
Claim 8. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an identifier of the client device.
Claim 13. … determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 9. The computer readable storage medium according to claim 7, wherein the determining the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a release of software indicated in the message.
Claim 13. … determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 10. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising a resource type indicated in the message.
Claim 13. … determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 11. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising an operation indicated in the message.
Claim 13. … determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 12. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising a uniform resource identifier indicated in the message.
Claim 1. … determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message … the profile in a resource that can be identified by uniform resource identifier (URI) in the service
Rationales:
The subject matter claimed in the pending application is fully disclosed in the patent and is covered by the patent since the patent and the application are claiming common subject matter. There are differences between the claims depicted in the bolded words and the underlined words. Pertaining the difference depicted in the bolded words, it appears to be using different wording but meaning is the same. It is therefore deemed obvious to those skilled in the art of claim drafting to draft claim in a later-filed patent application using different wording but same meaning from reading claims in an early-filed patent application issued into a patent. A reason for doing so is to seek a well-rounded protection for a disclose invention. Moreover and pertaining the difference depicted in the underlined words, it appears to be broadening claim by omitting limitations. Nevertheless, it has been held that the omission of an element and its function is an obvious expedient if the remaining elements perform the same function as before. In re Karlson, 186 USPQ 184(CCPA). Also note Ex Parte Rainu, 168 USPQ 375 (Bd. App. 1969); omission of a reference whose function is not needed would be an obvious variation.
Claims 1-12 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 6 and 11 of U.S. Patent No. 11831727. Although the claims at issue are not identical, they are not patentably distinct from each other because followings.
Pending Application
U.S. Patent Number 11831727
Claim 1. An apparatus for creating compatible messages between devices, the apparatus comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 1. An apparatus for modifying messages exchanged between devices, the apparatus comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
receiving a first message defining a profile for modifying messages, wherein the profile specifies which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes;
storing the profile in a resource;
receiving a second message from a client application for a target application; determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and
applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or new message that is compatible with the target application.
Claim 2. The apparatus according to claim 1, wherein the message is a service layer message.
Claim 1. … a first message.
Claim 3. The apparatus according to claim 1, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to each profile in the list of profiles, the information associated with the message from the client device comprising one or more of an identifier of the client device, a release of software indicated in the message, a resource type indicated in the message, an operation indicated in the message, and a uniform resource identifier indicated in the message.
Claim 1. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 4. A method for creating compatible messages between devices, the method comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 6. A method for modifying messages exchanged between devices, the method comprising:
receiving a first message defining a profile for modifying messages, wherein the profile specifies which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes; storing the profile in a resource; receiving a second message from a client application for a target application; determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and
applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or new message that is compatible with the target application.
Claim 5. The method according to claim 4, wherein the message is a service layer message.
Claim 6. … a first message.
Claim 6. The method according to claim 4, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising one or more of an identifier of the client device, a release of software indicated in the message, a resource type indicated in the message, an operation indicated in the message, and a uniform resource identifier indicated in the message.
Claim 6. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 7. A computer readable storage medium storing computer executable instructions that when executed by a computing device cause said computing device to effectuate operations comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 11. A computer readable storage medium storing computer executable instructions that when executed by one or more computing devices cause said one or more computing devices to effectuate operations comprising:
receiving a first message defining a profile for modifying messages, wherein the profile specifies which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes; storing the profile in a resource; receiving a second message from a client application for a target application; determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and
applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or new message that is compatible with the target application.
Claim 8. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an identifier of the client device.
Claim 11. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 9. The computer readable storage medium according to claim 7, wherein the determining the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a release of software indicated in the message.
Claim 11. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 10. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising a resource type indicated in the message.
Claim 11. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message ; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 11. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising an operation indicated in the message.
Claim 11. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Claim 12. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising a uniform resource identifier indicated in the message.
Claim 11. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message.
Rationales:
The subject matter claimed in the pending application is fully disclosed in the patent and is covered by the patent since the patent and the application are claiming common subject matter. There are differences between the claims depicted in the bolded words and the underlined words. Pertaining the difference depicted in the bolded words, it appears to be using different wording but meaning is the same. It is therefore deemed obvious to those skilled in the art of claim drafting to draft claim in a later-filed patent application using different wording but same meaning from reading claims in an early-filed patent application issued into a patent. A reason for doing so is to seek a well-rounded protection for a disclose invention. Moreover and pertaining the difference depicted in the underlined words, it appears to be broadening claim by omitting limitations. Nevertheless, it has been held that the omission of an element and its function is an obvious expedient if the remaining elements perform the same function as before. In re Karlson, 186 USPQ 184(CCPA). Also note Ex Parte Rainu, 168 USPQ 375 (Bd. App. 1969); omission of a reference whose function is not needed would be an obvious variation.
Claims 1-12 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 5 and 9 of U.S. Patent No. 11570258. Although the claims at issue are not identical, they are not patentably distinct from each other because followings.
Pending Application
U.S. Patent Number 11570258
Claim 1. An apparatus for creating compatible messages between devices, the apparatus comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 1. An apparatus for modifying messages exchanged between devices, the apparatus comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
receiving a first message defining a profile for modifying messages, wherein the profile specifies which types of messages the profile applies to, names of attributes in a message to be modified, and modifications to be performed on the attributes; storing the profile in a resource; receiving a second message from a client device for a target end device; determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and
applying the list of applicable profiles to the second message to modify attributes of the second message and create an updated or new message that is compatible with the target end device.
Claim 2. The apparatus according to claim 1, wherein the message is a service layer message.
Claim 1. … a first message.
Claim 3. The apparatus according to claim 1, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to each profile in the list of profiles, the information associated with the message from the client device comprising one or more of an identifier of the client device, a release of software indicated in the message, a resource type indicated in the message, an operation indicated in the message, and a uniform resource identifier indicated in the message.
Claim 1. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to modify attributes of the second message.
Claim 4. A method for creating compatible messages between devices, the method comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 5. A method for modifying messages exchanged between devices, the method comprising:
receiving a first message defining a profile for modifying messages, wherein the profile specifies which types of messages the profile applies to, names of attributes in a message to be modified, and modifications to be performed on the attributes; storing the profile in a resource; receiving a second message from a client device for a target end device; determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and
applying the list of applicable profiles to the second message to modify attributes of the second message and create an updated or new message that is compatible with the target end device.
Claim 5. The method according to claim 4, wherein the message is a service layer message.
Claim 5. … a first message.
Claim 6. The method according to claim 4, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising one or more of an identifier of the client device, a release of software indicated in the message, a resource type indicated in the message, an operation indicated in the message, and a uniform resource identifier indicated in the message.
Claim 5. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to modify attributes of the second message.
Claim 7. A computer readable storage medium storing computer executable instructions that when executed by a computing device cause said computing device to effectuate operations comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 9. A computer readable storage medium storing computer executable instructions that when executed by one or more computing devices cause said one or more computing devices to effectuate operations comprising:
receiving a first message defining a profile for modifying messages, wherein the profile specifies which types of messages the profile applies to, names of attributes in a message to be modified, and modifications to be performed on the attributes; storing the profile in a resource; receiving a second message from a client device for a target end device; determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and
applying the list of applicable profiles to the second message to modify attributes of the second message and create an updated or new message that is compatible with the target end device.
Claim 8. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an identifier of the client device.
Claim 9. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to modify attributes of the second message.
Claim 9. The computer readable storage medium according to claim 7, wherein the determining the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a release of software indicated in the message.
Claim 9. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to modify attributes of the second message.
Claim 10. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising a resource type indicated in the message.
Claim 9. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to modify attributes of the second message.
Claim 11. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising an operation indicated in the message.
Claim 9. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to modify attributes of the second message.
Claim 12. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising a uniform resource identifier indicated in the message.
Claim 9. … determining a list of applicable profiles stored in resources of a plurality of profiles for modifying the second message; and applying the list of applicable profiles to the second message to modify attributes of the second message.
Rationales:
The subject matter claimed in the pending application is fully disclosed in the patent and is covered by the patent since the patent and the application are claiming common subject matter. There are differences between the claims depicted in the bolded words and the underlined words. Pertaining the difference depicted in the bolded words, it appears to be using different wording but meaning is the same. It is therefore deemed obvious to those skilled in the art of claim drafting to draft claim in a later-filed patent application using different wording but same meaning from reading claims in an early-filed patent application issued into a patent. A reason for doing so is to seek a well-rounded protection for a disclose invention. Moreover and pertaining the difference depicted in the underlined words, it appears to be broadening claim by omitting limitations. Nevertheless, it has been held that the omission of an element and its function is an obvious expedient if the remaining elements perform the same function as before. In re Karlson, 186 USPQ 184(CCPA). Also note Ex Parte Rainu, 168 USPQ 375 (Bd. App. 1969); omission of a reference whose function is not needed would be an obvious variation.
Claims 1-12 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of U.S. Patent No. 10887420. Although the claims at issue are not identical, they are not patentably distinct from each other because followings.
Pending Application
U.S. Patent Number 10887420
Claim 1. An apparatus for creating compatible messages between devices, the apparatus comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 1. An apparatus for creating compatible messages between devices, the apparatus comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising: defining a plurality of profiles for modifying messages, wherein each respective profile of the plurality of profiles specifies which types of messages each respective profile applies to, the names of attributes in the message to be modified, and modifications to be performed on the attributes;
receiving a message from a client device for a target end device; determining a list of profiles of the plurality of profiles to apply to the message, the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create an updated or new message that is compatible with the target end device.
Claim 2. The apparatus according to claim 1, wherein the message is a service layer message.
Claim 2. The apparatus of claim 1, wherein the message is a service layer message.
Claim 3. The apparatus according to claim 1, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to each profile in the list of profiles, the information associated with the message from the client device comprising one or more of an identifier of the client device, a release of software indicated in the message, a resource type indicated in the message, an operation indicated in the message, and a uniform resource identifier indicated in the message.
Claim 3. The apparatus of claim 1, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an identifier of the client device.
Claim 4. The apparatus of claim 1, wherein the determining the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a release of software indicated in the message.
Claim 5. The apparatus of claim 1, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a resource type indicated in the message.
Claim 6. The apparatus of claim 1, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an operation indicated in the message.
Claim 7. The apparatus of claim 1, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a uniform resource identifier indicated in the message.
Claim 4. A method for creating compatible messages between devices, the method comprising:
receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 8. A method for creating compatible messages between devices, the method comprising: defining a plurality of profiles for modifying messages, wherein each respective profile of the plurality of profiles specifies which types of messages each respective profile applies to, the names of attributes in the message to be modified, and modifications to be performed on the attributes;
receiving a message from a client device for a target end device; determining a list of profiles of the plurality of profiles to apply to the message, the list of profiles associated with multiple versions of an implemented software of the target end device; and
applying the list of profiles to the message to create an updated or new message that is compatible with the target end device.
Claim 5. The method according to claim 4, wherein the message is a service layer message.
Claim 9. The method of claim 8, wherein the message is a service layer message.
Claim 6. The method according to claim 4, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising one or more of an identifier of the client device, a release of software indicated in the message, a resource type indicated in the message, an operation indicated in the message, and a uniform resource identifier indicated in the message.
Claim 10. The method of claim 8, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an identifier of the client device.
Claim 11. The method of claim 8, wherein the determining the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a release of software indicated in the message.
Claim 12. The method of claim 8, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a resource type indicated in the message.
Claim 13. The method of claim 8, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an operation indicated in the message.
Claim 14. The method of claim 8, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a uniform resource identifier indicated in the message.
Claim 7. A computer readable storage medium storing computer executable instructions that when executed by a computing device cause said computing device to effectuate operations comprising: receiving a message from a client device for a target end device; determining a version or release associated with the message; determining based on the version or release associated with the message, a list of profiles to apply to the message, each of the list of profiles associated with the version or release associated with the message and the list of profiles associated with multiple versions of an implemented software of the target end device; and applying the list of profiles to the message to create a new message that is compatible with the target end device.
Claim 15. A non-transitory computer readable storage medium storing computer executable instructions that when executed by a computing device cause said computing device to effectuate operations comprising: defining a plurality of profiles for modifying messages, wherein each respective profile of the plurality of profiles specifies which types of messages each respective profile applies to, the names of attributes in the message to be modified, and modifications to be performed on the attributes; receiving a message from a client device for a target end device; determining a list of profiles of the plurality of profiles to apply to the message, the list of profiles associated with multiple versions of an implemented software of the target end device; and applying the list of profiles to the message to create an updated or new message that is compatible with the target end device.
Claim 8. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an identifier of the client device.
Claim 16. The computer readable storage medium of claim 15, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an identifier of the client device.
Claim 9. The computer readable storage medium according to claim 7, wherein the determining the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a release of software indicated in the message.
Claim 17. The computer readable storage medium of claim 15, wherein the determining the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a release of software indicated in the message.
Claim 10. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising a resource type indicated in the message.
Claim 18. The computer readable storage medium of claim 15, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a resource type indicated in the message.
Claim 11. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising an operation indicated in the message.
Claim 19. The computer readable storage medium of claim 15, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising an operation indicated in the message.
Claim 12. The computer readable storage medium according to claim 7, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the profiles, the information associated with the message from the client device comprising a uniform resource identifier indicated in the message.
Claim 20. The computer readable storage medium of claim 15, wherein the determining of the list of profiles is based on matching information associated with the message from the client device to the list of profiles, the information associated with the message from the client device comprising a uniform resource identifier indicated in the message.
Rationales:
The subject matter claimed in the pending application is fully disclosed in the patent and is covered by the patent since the patent and the application are claiming common subject matter. There are differences between the claims depicted in the bolded words and the underlined words. Pertaining the difference depicted in the bolded words, it appears to be using different wording but meaning is the same. It is therefore deemed obvious to those skilled in the art of claim drafting to draft claim in a later-filed patent application using different wording but same meaning from reading claims in an early-filed patent application issued into a patent. A reason for doing so is to seek a well-rounded protection for a disclose invention. Moreover and pertaining the difference depicted in the underlined words, it appears to be broadening claim by omitting limitations. Nevertheless, it has been held that the omission of an element and its function is an obvious expedient if the remaining elements perform the same function as before. In re Karlson, 186 USPQ 184(CCPA). Also note Ex Parte Rainu, 168 USPQ 375 (Bd. App. 1969); omission of a reference whose function is not needed would be an obvious variation.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Dong et al. (US 20190253994) discloses service layer registration.
Lu et al. (US 20150029894) discloses Service Domain Charging Systems and Methods.
Jones et al. (US 20120285790) discloses Wireless Communication Parking Meter System and Method.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to KABIR U JAHANGIR whose telephone number is (571)272-0796. The examiner can normally be reached Mon-Fri 10am to 6:30pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ricky Ngo can be reached at (571)272-3139. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/K. J./
Examiner, Art Unit 2464
/RICKY Q NGO/Supervisory Patent Examiner, Art Unit 2464
Prosecution Insights