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 .
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)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 1-6, 8-14, 16 and 20-25 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by U.S. Patent Application Publication 2021/0250411 to Cakulev et al.
As concerns claim 1, a method performed by a first network node, comprising: sending a register request (Fig. 4, 404-1 Register; 0038-registration request) comprising a network function profile (Fig. 5A-504 NF profile) of the first network node (Fig. 3; 0035-0036) to a network repository function (NRF) (Fig. 1, 104 NRF; Fig. 4, 410), wherein the network function profile of the first network node comprises one or more default notification subscriptions (Fig. 4, 404-3 Subscribe) for one or more services for the first network node as network function (NF) service consumer (Fig. 1, 106-Network Function Service Consumer);
wherein the one or more default notification subscriptions for the one or more services comprise one default notification subscription (0040-subscribe operation; 0044-subscription data; 0065-have subscribed; BRI: “default” is just a label) used to receive notification (Fig. 4, 404-6 Notify; 0040-subscribe operation, to subscribe to the notification service; 0041; 0065) for the one or more services (0065);
wherein the one default notification subscription comprises a map (0048-list; 0053; 0066-list of service versions) of service specific information per service, indicating a mapping of a service name (Fig. 5B-530 NF Services; Fig. 5C service name, versions; 0049; 0056-list or array of information, describe a service; 0058-Service Name) of the service to service specific information (Fig. 5C versions; 0014-supported API features; 0015-API version; 0037; 0059; 0066);
wherein the service specific information comprises at least one application programming interface (API) version (Fig. 5C versions; 0014-supported API features; 0015-API version; 0037; 0059; 0066) of the service supported by the first network node as NF service consumer (Fig. 1, 106), and at least one feature of the service supported by the first network node as NF service consumer (0066; 0067-supported versions; 0068-supported features); and
receiving a register response (0043-response 408 from NRF) from the NRF.
As concerns claim 9, a method performed by a second network node, comprising: sending a first discovery request (Fig. 4, 406) to a third network node (Fig. 4; Fig. 3; 0035-0036); and receiving a first discovery response (Fig. 4, 408) from the third network node, wherein the first discovery response comprises at least one default notification subscription (0043; 0044-subscription) for at least one service (0043; 0044) for at least one first network node as network function (NF) service consumer (Fig. 1, 106-Network Function Service Consumer);
wherein the at least one default notification subscription for the at least one service comprises one default notification subscription used to receive notification (Fig. 4, 404-6 Notify; 0040-subscribe operation, to subscribe to the notification service; 0041; 0065) of the at least one service;
wherein the one default notification subscription comprises a map of service specific information per service, indicating a mapping of a service name (Fig. 5B-530 NF Services; Fig. 5C service name, versions; 0049; 0056-list or array of information, describe a service; 0058-Service Name) of the service to service specific information (Fig. 5C versions; 0014-supported API features; 0015-API version; 0037; 0059; 0066);
wherein the service specific information comprises at least one application programming interface (API) version (Fig. 5C versions; 0014-supported API features; 0015-API version; 0037; 0059; 0066) of the service supported by the first network node as NF service consumer, and at least one feature of the service supported by the first network node as NF service consumer (0066; 0067-supported versions; 0068-supported features).
As concerns claim 20, a method performed by a third network node, comprising:
receiving a first discovery request (Fig. 4, 406) from a second network node (Fig. 4; Fig. 3; 0035-0036); and
sending a first discovery response (Fig. 4, 408) to the second network node, wherein the first discovery response comprises at least one default notification subscription (0043; 0044-subscription) for at least one service (0043; 0044) for at least one first network node (Fig. 4; Fig. 3; 0035-0036) as network function (NF) service consumer (Fig. 1, 106-Network Function Service Consumer);
wherein the at least one default notification subscription for the at least one service comprises one default notification subscription used to receive notification (Fig. 4, 404-6 Notify; 0040-subscribe operation, to subscribe to the notification service; 0041; 0065) of the at least one service;
wherein the one default notification subscription comprises a map (0048-list; 0053; 0066-list of service versions) of service specific information per service, indicating a mapping of a service name (Fig. 5B-530 NF Services; Fig. 5C service name, versions; 0049; 0056-list or array of information, describe a service; 0058-Service Name) of the service to service specific information (Fig. 5C versions; 0014-supported API features; 0015-API version; 0037; 0059; 0066);
wherein the service specific information comprises at least one application programming interface (API) version (Fig. 5C versions; 0014-supported API features; 0015-API version; 0037; 0059; 0066) of the service supported by the first network node as NF service consumer, and at least one feature of the service supported by the first network node as NF service consumer (0066; 0067-supported versions; 0068-supported features).
As concerns claim 2, the method according to claim 1, wherein each of the one or more default notification subscriptions for the one or more services is used to receive notification of a corresponding service (Fig. 4, 404-6 Notify; 0040-subscribe operation, to subscribe to the notification service; 0041; 0065).
As concerns claim 10, the method according to claim 9, wherein each of the at least one default notification subscription for the at least one service is used to receive notification of a corresponding service (Fig. 4, 404-6 Notify; 0040-subscribe operation, to subscribe to the notification service; 0041; 0065).
As concerns claim 21, the method according to claim 20, wherein each of the at least one default notification subscription for the at least one service is used to receive notification of a corresponding service (Fig. 4, 404-6 Notify; 0040-subscribe operation, to subscribe to the notification service; 0041; 0065).
As concerns claim 3, the method according to claim 2, wherein each of the one or more default notification subscriptions for the one or more services comprises information indicating a specific service (0040; 0046; 0057).
As concerns claim 11, the method according to claim 10, wherein each of the at least one default notification subscription for the at least one service comprises information indicating a specific service (0040; 0046; 0057).
As concerns claim 22, the method according to claim 21, wherein each of the at least one default notification subscription for the at least one service comprises information indicating a specific service (0040; 0046; 0057).
As concerns claim 4, the method according to claim 3, wherein the information indicating a specific service comprises a name of the specific service (0040; 0046-name of the service; 0057-service name).
As concerns claim 12, the method according to claim 11, wherein the information indicating the specific service comprises a name of the specific service (0040; 0046-name of the service; 0057-service name).
As concerns claim 23, the method according to claim 22, wherein the information indicating a specific service comprises a name of the specific service (0040; 0046-name of the service; 0057-service name).
As concerns claim 5, the method according to claim 1,wherein the one or more default notification subscriptions for the one or more services comprises service specific information (0066; 0067-supported versions; 0068-supported features) per service.
As concerns claim 13, the method according to claim 9, wherein the at least one default notification subscription for the at least one service comprises service specific information (0066; 0067-supported versions; 0068-supported features) per service.
As concerns claim 24, the method according to claim 20, wherein the at least one default notification subscription for the at least one service comprises service specific information per service (0066; 0067-supported versions; 0068-supported features).
As concerns claim 6, the method according to claim 1, wherein: the first network node is a network function service consumer (Fig. 1, 106) of the one or more services; and/or wherein the first network node comprises a Gateway Mobile Location Centre (GMLC).
As concerns claim 8, the method according to claim 1, further comprising: sending a register update request (Fig. 4, 404-2) comprising an updated network function profile of the first network node to a network repository function (NRF), wherein the updated network function profile of the first network node comprises one or more updated default notification subscriptions for one or more services for the first network node as NF service consumer (0039); and receiving a register update response from the NRF (Fig. 4, 404-6, 408).
As concerns claim 14, the method according to claim 9, further comprising:
determining a default notification subscription (Fig. 4, 404-3 Subscribe) matching one service for the second network node as NF service producer (Fig. 1, 102-Network Function Service Producer) from the at least one default notification subscription;
generating a default notification (0065) according to the determined default notification subscription and service specific information (Fig. 5C versions; 0014-supported API features; 0015-API version; 0037; 0059; 0065-0066) of the one service indicated in the determined default notification subscription; and
sending the default notification to a default notification endpoint (0065-notify consumer; 0084-subscription, UE device) indicated in the determined default notification subscription.
As concerns claim 16, the method according to claim 9, wherein the second network node is a network function service producer (Fig. 1, 102-Network Function Service Producer) and the at least one first network node is a network function service consumer (Fig. 1, 106-Network Function Service Consumer); and/or the second network node comprises at least one of: an Access and Mobility Management Function (AMF), or a location management function (LMF); and/or the third network node comprises at least one of: a network repository function (NRF), or a service communication proxy (SCP); and/or the at least one first network node comprises a Gateway Mobile Location Centre (GMLC).
As concerns claim 25, the method according to claim 20, wherein the second network node is a network function producer (Fig. 1, 102-Network Function Service Producer) and the at least one first network node is a network function consumer (Fig. 1, 106-Network Function Service Consumer); and/or the second network node comprises at least one of: an Access and Mobility Management Function (AMF), or a location management function (LMF); and/or the third network node comprises at least one of:a network repository function (NRF), or a service communication proxy (SCP); and/or the at least one first network node comprises a Gateway Mobile Location Centre (GMLC).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. See PTO-892. U.S. Patent Application Publication 2021/0240554 to Landais et al. disclose at least notifications and subscriptions (0074) and default notification subscriptions (0075, 0077, 0081-0082, 0084, 0101, 0107).
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOHN B WALSH whose telephone number is (571)272-7063. The examiner can normally be reached 7:30-3:30 pm.
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, Christopher L Parry can be reached at 571-272-8328. 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.
/JOHN B WALSH/Primary Examiner, Art Unit 2451
Prosecution Insights