DETAILED ACTION
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 .
Response to Arguments
Applicant's arguments filed April 29, 2026 have been fully considered but they are not persuasive.
Hu further teaches receiving, by the UE, a message comprising a second communication address of the selected service from the service controller in response to the request to access the selected service sent to the first communication address of the service controller (Cols. 17 lines 26 – 33, 18 lines 44 – 60, service policy info comprises network slice connection policy, performs a service based on network slice, access type is the address of the service, this happens as a result of session connection create request (Col. 15 lines 1 – 12)); and starting, by the UE, the selected service based on the UE requesting the selected service via the second communication address of the selected service (Col. 18 lines 44 – 60, establishing and initiating the connection for the service, which is starting the service).
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1, 2, 5 – 7, 10, 12, 14 – 16 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Hu et al. (US 11,265,226).
Regarding Claim 1, Hu teaches a method for providing and/or using services for a user equipment (UE), the services being provided at least indirectly by a network operator, the method comprising: after the UE has registered to a network of the network operator (in order to initiate an activation request message (Col. 13 lines 6 – 10) the UE would need to go through a handshaking or registration process with the network), communicating, by the UE, with the network or the network operator via a communication link between the network of the network operator and the UE (Figure 2, gateway, which comprises gateway control planes and gateway user planes enables a communication link between the UE network operator, which is the internet service provider (ISP)); receiving by the UE, a first communication address of a service controller of the network operator (Col. 13 lines 38 – 42, communication address of gateway), wherein the service controller manages access to services that can be used by the UE (Col. 18 lines 44 – 60, gateway provides the network slice information, which the services are based on, thus the gateway effectively manages access to the services), and wherein the service controller de-registers or updates available services; receiving, by the UE, a list of possible available services from the service controller; selecting, by the UE, a service from the list (Col. 18 lines 55 – 57, searching network slices thus there will be a list of available slices); sending, by the UE, a request to access the selected service to the first communication address of the service controller (Col. 15 lines 1 – 12, session connection create request); receiving, by the UE, a message comprising a second communication address of the selected service from the service controller in response to the request to access the selected service sent to the first communication address of the service controller (Cols. 17 lines 26 – 33, 18 lines 44 – 60, service policy info comprises network slice connection policy, performs a service based on network slice, access type is the address of the service, this happens as a result of session connection create request (Col. 15 lines 1 – 12)); and starting, by the UE, the selected service based on the UE requesting the selected service via the second communication address of the selected service (Col. 18 lines 44 – 60, establishing and initiating the connection for the service, which is starting the service).
Regarding Claim 14, Hu teaches a communication system, comprising: a service controller of a network operator (Figure 2, gateway, which comprises gateway control planes and gateway user planes); and a user equipment (UE) (Figure 2); wherein the service controller is configured to: after the UE has registered to a network of the network operator (in order to initiate an activation request message (Col. 13 lines 6 – 10) the UE would need to go through a handshaking or registration process with the network), provide a communication link between the network of the network operator and the UE (Figure 2, gateway, which comprises gateway control planes and gateway user planes enables a communication link between the UE network operator, which is the internet service provider (ISP)); transmit a first communication address of the service controller of the network operator to the UE (Col. 13 lines 38 – 42, communication address of gateway); manage access to services that can be used by the UE (Col. 18 lines 44 – 60, gateway provides the network slice information, which the services are based on, thus the gateway effectively manages access to the services); and de-register or update available services; wherein the UE is configured to receive a list of possible available services from the service controller; select a service from the list (Col. 18 lines 55 – 57, searching network slices thus there will be a list of available slices); and send a request to access the selected service to the first communication address of the service controller (Col. 15 lines 1 – 12, session connection create request); wherein the service controller is further configured to transmit a message comprising a second communication address of the selected service from the service controller to the UE in response to the request to access the selected service sent to the first communication address of the service controller (Cols. 17 lines 26 – 33, 18 lines 44 – 60, service policy info comprises network slice connection policy, performs a service based on network slice, access type is the address of the service, this happens as a result of session connection create request (Col. 15 lines 1 – 12)); and wherein the UE is further configured to start the selected service based on the UE requesting the selected service via the second communication address of the selected service (Col. 18 lines 44 – 60, establishing and initiating the connection for the service, which is starting the service).
Regarding Claim 16, A non-transitory computer-readable medium having processor-executable instructions stored thereon for providing and/or using services for a user equipment (UE), the services being provided at least indirectly by a network operator, wherein the processor- executable instructions (Figure 3, UE comprises a processor, typical processors run executable code stored in memory), when executed, facilitate performance of the following: after the UE has registered to a network of the network operator (in order to initiate an activation request message (Col. 13 lines 6 – 10) the UE would need to go through a handshaking or registration process with the network), communicating, by the UE, with the network of the network operator via a communication link between the network of the network operator and the UE (Figure 2, gateway, which comprises gateway control planes and gateway user planes enables a communication link between the UE network operator, which is the internet service provider (ISP)); receiving, by the UE, a first communication address of a service controller of the network operator (Col. 13 lines 38 – 42, communication address of gateway), wherein the service controller manages access to services that can be used by the UE (Col. 18 lines 44 – 60, gateway provides the network slice information, which the services are based on, thus the gateway effectively manages access to the services), and wherein the service controller de-registers or updates available services; receiving, by the UE, a list of possible available services from the service controller; selecting, by the UE, a service from the list (Col. 18 lines 55 – 57, searching network slices thus there will be a list of available slices); sending, by the UE, a request to access the selected service to the first communication address of the service controller(Col. 15 lines 1 – 12, session connection create request); receiving, by the UE, a message comprising a second communication address of the selected service from the service controller in response to the request to access the selected service sent to the first communication address of the service controller (Cols. 17 lines 26 – 33, 18 lines 44 – 60, service policy info comprises network slice connection policy, performs a service based on network slice, access type is the address of the service, this happens as a result of session connection create request (Col. 15 lines 1 – 12)); and starting, by the UE, the selected service based on the UE requesting the selected service via the second communication address of the selected service (Col. 18 lines 44 – 60, establishing and initiating the connection for the service, which is starting the service).
Regarding Claim 2, Hu teaches all of the claimed limitations recited in Claim 1. Hu further teaches wherein the first communication address of the service controller is transmitted upon a request by the UE and/or by a network controller upon the UE registering to the network (Col. 13 line 13, UE sends an attach request message).
Regarding Claim 5, Hu teaches all of the claimed limitations recited in Claim 1. Hu further teaches wherein the message comprises parameters characterizing the service (Col. 18 lines 44 – 60, network slice information characterizes the service).
Regarding Claim 6, Hu teaches all of the claimed limitations recited in Claim 5. Hu further teaches wherein the message comprises a list with respective second communication addresses of several different implementations of a respective service (Col. 18 lines 44 – 60, access types are the addresses, plurality of network slices thus there will be a list), wherein: the UE selects one of the implementations based on the parameters and/or the service controller performs a pre-selection of the implementations based on a second criteria (Col. 18 lines 44 – 60, selection based on the desired service).
Regarding Claim 7, Hu teaches all of the claimed limitations recited in Claim 1. Hu further teaches wherein a service provider registers the service, wherein the service is known to the service controller, and wherein the service controller keeps the service available for requests (Figure 2, Cols. 17 lines 26 – 33, 18 lines 44 – 60, typical ISPs register the services they offer, gateway provides network slice information, which is service information thus gateway keeps slices available).
Regarding Claim 10, Hu teaches all of the claimed limitations recited in Claim 1. Hu further teaches wherein the service is set up in the network of the network operator or in a further network of a further network operator (Col. 18 lines 44 – 60, the service will be set up in the network of the ISP (Figure 2)).
Regarding Claim 15, Hu combination teaches all of the claimed limitations recited in Claim 14. Hu further teaches a service handling engine; a service database; a service monitoring engine; a life cycle management engine; and/or a trust relation management engine (Col. 18 lines 44 – 60, gateway provides the network slice information, which the services are based on thus the entity of said gateway that handles the network slice information is the service handling engine).
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claim(s) 3 is/are rejected under 35 U.S.C. 103 as being unpatentable over Hu et al. (US 11,265,226) in view of Yoshizawa (US 2016/0044544).
Regarding Claim 3, Hu teaches all of the claimed limitations recited in Claim 2. Hu does not teach wherein the network controller selects, from among a plurality of service controllers, the service controller whose first communication address it transmits to the UE according to a first criterion.
Yoshizawa, which also teaches the use of gateways, teaches wherein the network controller selects, from among a plurality of service controllers, the service controller whose first communication address it transmits to the UE according to a first criterion (Sections 0017, 0018, appropriate gateway is selected to accommodate handoff based on a handoff request).
It would have been obvious to one of ordinary skill in the art prior to the effective filing date of the claimed invention to modify the system of Hu with the above features of Yoshizawa for the purpose of preserving calls when changing networks as taught by Yoshizawa.
Claim(s) 8, 9 is/are rejected under 35 U.S.C. 103 as being unpatentable over Hu et al. (US 11,265,226) in view of Agarwal et al. (US 2017/0171818)
Regarding Claim 8, Hu teaches all of the claimed limitations recited in Claim 1. Hu does not teach wherein in case that the service is not available yet, the service controller sets up the service.
Agarwal, which also teaches wireless communications, teaches wherein in case that the service is not available yet, the service controller sets up the service (Section 0090, in DRX the mobile can be sleep during inactive periods while remaining connected to the network, the connection has been established or set up).
It would have been obvious to one of ordinary skill in the art prior to the effective filing date of the claimed invention to modify the system of Hu with the above features of Agarwal for the purpose of providing an efficient use of power as taught by Agarwal.
Regarding Claim 9, Hu in view of Agarwal teaches all of the claimed limitations recited in Claim 8. Hu does not teach wherein the service controller for setting up the service obtains execution-relevant information from a provider of the service and/or an internal service database of the network operator.
Agarwal, which also teaches wireless communications, teaches wherein the service controller for setting up the service obtains execution-relevant information from a provider of the service and/or an internal service database of the network operator (Section 0090, device can wake up and monitor for activity which comprises execution relevant information).
It would have been obvious to one of ordinary skill in the art prior to the effective filing date of the claimed invention to modify the system of Hu with the above features of Agarwal for the purpose of providing an efficient use of power as taught by Agarwal.
Claim(s) 11 is/are rejected under 35 U.S.C. 103 as being unpatentable over Hu et al. (US 11,265,226) in view of Govindassamy (US 10,531,361)
Regarding Claim 11, Hu teaches all of the claimed limitations recited in Claim 1. Hu does not teach wherein the service is set up in a distributed manner in the network of the network operator and in a further network of a further network operator.
Govindassamy, which also teaches use of internet services, teaches wherein the service is set up in a distributed manner in the network of the network operator and in a further network of a further network operator (Col. 4 lines 18 – 36, distribution of internet services across access networks).
It would have been obvious to one of ordinary skill in the art prior to the effective filing date of the claimed invention to modify the system of Hu with the above features of Govindassamy for the purpose of enabling a client device to get internet service from multiple sources as taught by Govindassamy.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to RAYMOND S DEAN whose telephone number is (571)272-7877. The examiner can normally be reached Monday-Friday, 6:00-2:30, EST.
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, Anthony S Addy can be reached at 571-272-7795. 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.
/RAYMOND S DEAN/Primary Examiner, Art Unit 2645 Raymond S. Dean
July 6, 2026
Prosecution Insights