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 .
This in response to the IDS filed 1/27/2025.
Information Disclosure Statement
The Information Disclosure Statements filed 1/7/2025 and 1/27/2025 have been considered.
Specification
The disclosure is objected to because of the following informalities:
[0002] line 1, has the phrase “is assigned is assigned” which appears to be a typo and will be read as a singular instance of is assigned.
[0008] line 1, reads “examples frameworks” and appears to be missing an of or to write examples as example.
Appropriate correction is required.
Claim Objections
Claim 8 is objected to because of the following informalities:
Claim 8, lines 3 and 5 have extra commas after first PDU session.
Appropriate correction is required.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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-20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Nayak et a., US PGPub 2023/0016724 A1 in it’s entirety.
a. Regarding claim 1, Nayak et al. shows a method comprising: receiving, by a wireless device, a configuration message comprising: a network slice identifier indicating a network slice of a plurality of network slices [0068]; an indication that the network slice is allowed for multiple 3rd Generation Partnership Project (3GPP) access [0069], wherein the multiple 3GPP access comprise at least a first 3GPP access and a second 3GPP access; sending, by the wireless device and via the first 3GPP access, a first registration request message requesting the network slice; and sending, by the wireless device, and via the second 3GPP access, a second registration request message requesting the network slice, wherein the network slice is allowed via the first 3GPP access (Figs. 3-8; [0087]-[0088], [0169]-[0170], and [0010]-[0018]).
PNG
media_image1.png
466
640
media_image1.png
Greyscale
PNG
media_image2.png
698
436
media_image2.png
Greyscale
b. Regarding claim 2, Nayak et al. shows the method of claim 1, further comprising: receiving, by the wireless device and via a plurality of 3GPP access, a plurality of registration accept messages indicating one or more of: a second network slice, of the plurality of network slices, is allowed, a third network, of the plurality of network slices, is rejected for one or more of the plurality of 3GPP access; and sending, based on one of the plurality of registration accept messages and via a third 3GPP access of the plurality of 3GPP access, a third registration request message deregistering the second network slice ([0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI).
c. Regarding claim 3, Nayak et al. shows the method of claim 1, further comprising: sending, by the wireless device, a request message for the parameter, wherein: the request message comprises an indication that the wireless device supports a feature of dualsteer; the feature of dualsteer is using a plurality of access paths for an 3GPP access type; and at least one access path of the plurality of access paths is associated with at least one of: a 3GPP cell; or a 3GPP radio access network (RAN) ([0082]-[0017]-[0018], [0083], and [0169]-[0170]).
d. Regarding claim 4, Nayak et al. shows the method of claim 1, wherein the configuration message further comprises: a second network slice identifier indicating a second network slice of the plurality of network slices; and a second indication that indicates the second network slice is not allowed for the multiple 3GPP access ([0017]-[0018] and [0169]).
e. Regarding claim 5, Nayak et al. shows the method of claim 4, wherein the sending the first registration request message further comprises: sending, based on the second parameter and via the first 3GPP access, the first registration request message requesting the network slice and the second network slice; and wherein the sending the second registration request message further comprises: sending. based on the second parameter and via the second 3GPP access, the second registration request message requesting the network slice, wherein the second slice is excluded in the second registration request message ([0017]-[0018] and [0169]).
f. Regarding claim 6, Nayak et al. shows the method of claim 1, further comprising: concurrently registering for the network slice via the multiple 3GPP access by sending the first registration request message and the second registration request message, wherein: a portion of time of the registration via the first 3GPP access overlaps a time of registration via the second 3GPP access ([0060] i.e. blocks may sometimes be performed substantially at the same time).
g. Regarding claim 7, Nayak et al. shows the method of claim 1, wherein the configuration message further comprises: a traffic descriptor; and a policy control information, wherein the policy control information indicates that a protocol data unit (PDU) session for a service data flow matching the traffic descriptor is preferred to use more than one 3GPP access paths ([0163] and [0169]-[0170]).
h. Regarding claim 8, Nayak et al. shows the method of claim 1, further comprising: sending, via the first 3GPP access, a first protocol data unit (PDU) session request message for a first PDU session; and sending, via the second 3GPP access, a second PDU session request message for the first PDU session ([0163] and [0169]-[0170]).
i. Regarding claim 9, Nayak et al. shows the method of claim 1, further comprising: receiving, based on the first registration request message and via the first 3GPP access, a first registration accept message indicating the network slice is allowed; and receiving, based on the second registration request message and via the second 3GPP access, a second registration accept message indicating the network slice is allowed ([0163] and [0169]-[0170]).
j. Regarding claim 10, Nayak et al. shows the method of claim 1, wherein the configuration message further comprises an indicator indicating whether the network slice is allowed for use over a non-3GPP (N3GPP) access path of a N3GPP access type [0083].
k. Regarding claim 11, Nayak et al. shows a method comprising: receiving, by a wireless device and via a first 3rd Generation Partnership Project (3GPP) access, a first registration accept message indicating a network slice of a plurality of network slices is allowed; receiving, by the wireless device and via a second 3GPP access, a second registration accept message, wherein: the second registration accept message indicates the network slice is rejected for multiple 3GPP access; and the multiple 3GPP access comprise at least the first 3GPP access and the second 3GPP access; and sending, based on the second registration accept message and via the first 3GPP access, a first registration request message deregistering the network slice (Figs. 3-8; [0087]-[0088], [0169]-[0170], and [0010]-[0018]).
l. Regarding claim 12, Nayak et al. shows the method of claim 11, further comprising: sending, based on the second registration accept message and via the second 3GPP access, a second registration request message registering the network slice; and receiving, based on the second registration request message, a third registration accept message indicating the network slice being allowed ([0017]-[0018], [0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI; Fig. 4).
m. Regarding claim 13, Nayak et al. shows the method of claim 11, wherein the first registration request message further comprises: an indication requesting a second network slice of the plurality of network slices; and wherein the method further comprising: sending, based on the second registration accept message and via the second 3GPP access, a second registration request message registering the second network slice ([0017]-[0018], [0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI; Fig. 4).
n. Regarding claim 14, Nayak et al. shows the method of claim 11, further comprising: sending, based on the second registration accept message and via the second 3GPP access, a second registration request message registering: the network slice; and a second network slice of the plurality of network slices; and receiving, based on the second registration request message, a third registration accept message indicating both the network slice and the second network slice are allowed ([0017]-[0018], [0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI; Fig. 4).
o. Regarding claim 15, Nayak et al. shows the method of claim 11, further comprising: determining, based on the second registration accept message and quality of service associated with the second 3GPP access, to register the network slice via the second 3GPP access; and sending, based on the determination and via the second 3GPP access, a second registration request message registering the network slice ([0017]-[0018], [0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI; Fig. 4).
p. Regarding claim 16, Nayak et al. shows the method of claim 11, further comprising: sending, via the first 3GPP access, a third registration request message registering the network slice; and wherein receiving the first registration accept message further comprises: receiving, based on the third registration request message and via the first 3GPP access, the first registration accept message ([0017]-[0018], [0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI; Fig. 4).
q. Regarding claim 17, Nayak et al. shows a method comprising: receiving, by a access and mobility management function (AMF) and via a second multiple 3rd Generation Partnership Project (3GPP) access, a first registration request message registering a network slice of a plurality of network slices, wherein the network slice is allowed via a first 3GPP access; sending, by the AMF and via a second 3GPP access, a first registration accept message, wherein: the first registration accept message indicates the network slice is rejected for multiple 3GPP access; and the multiple 3GPP access comprise at least the first 3GPP access and the second 3GPP access; and receiving, based on the first registration accept message and via the second 3GPP access, a second registration request message registering the network slice, wherein the network slice is deregistered via the first 3GPP access (Figs. 3-8; [0087]-[0088], [0169]-[0170], and [0010]-[0018]).
r. Regarding claim 18, Nayak et al. shows the method of claim 17, further comprising: sending, based on the second registration request message and via the second 3GPP access, a second registration accept message indicating the network slice is allowed ([0017]-[0018], [0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI, [0163] and [0169]-[0170] ; Fig. 4)).
s. Regarding claim 19, Nayak et al. shows the method of claim 17, wherein: a second network slice of the plurality of network slices is allowed via the first 3GPP access; and the receiving the second registration request message further comprising: receiving the second registration request message registering: the network slice; and the second network slice ([0017]-[0018], [0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI, [0163] and [0169]-[0170] ; Fig. 4)).
t. Regarding claim 20, Nayak et al. shows the method of claim 17, wherein the receiving the second registration request message further comprises: receiving the second registration request message registering: the network slice; and a second network slice of the plurality of network slices; and sending, based on the second registration request message, a second registration accept message indicating both the network slice and the second network slice are allowed ([0017]-[0018], [0087]-[0088] i.e. each of the allowed slices may include the same or different S-NSSAI, [0163] and [0169]-[0170] ; Fig. 4)).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Basu Mallick et al., US PGPub 2020/0113015 A1. Shows a similar multiple network slice wireless communication system to the claims of the instant application. See for example Fig. 1 below. This reference further highlights what was well known in the art.
PNG
media_image3.png
684
544
media_image3.png
Greyscale
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SEAHVOSH J NIKMANESH whose telephone number is (571)270-5549. The examiner can normally be reached M-F 9-5.
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, Yuwen Pan can be reached at (571)272-7855. 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.
/Seahvosh Nikmanesh/Examiner, Art Unit 2649 /YUWEN PAN/Supervisory Patent Examiner, Art Unit 2649
Prosecution Insights