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 Amendment/Remarks
This communication is considered fully responsive to the amendment filed on 04/14/2026.
Claims 1-20 are pending and are examined in this office action.
Claims 5, 6, 12, 13, 19-20 have been amended.
No new claim has been added and no claim has been canceled.
In view of the applicant’s argument, objection to the priority date has been withdrawn.
In view of the amendment, the objection to the claims has been withdrawn.
Response to Arguments
Applicant's arguments filed 04/14/2026 have been fully considered but they are not persuasive.
Applicant’s Argument:
Applicant argues that LOU does not claim limitation “transmit, to a base station, a radio resource control (RRC) request message comprising an indication of priority access of the wireless device to a network slice” (Emphasized added) .
Applicant argues in substance that “In brief, Lou's paragraphs [0017], [0056], and [0083] state that a terminal device selects "a network slice identifier of a network slice with a highest priority as the information about the first network slice." Lou's paragraph [0223] states that "[a] terminal device generates first information, where the first information includes any one or any combination of the following: information about a first network slice, first service information, and access information of the terminal device." Lou's paragraph [0224] states that the information about the first network slice "is used to indicate a network slice" and provides examples of service type of eMBB network slice and URLLC network slice. Lou's paragraph [0225] further states that the information about the first network slice can include "a user identifier, a network functional entity identifier, a public land mobile network (PLMN) identifier." Lou's paragraph [0233] states that "[t]he service type is an identifier used to uniquely determine a service type, for example, used to indicate a service type such as an eMBB service, a URLLC service, and an mMTC service." Lou's paragraph [0247] states that "[t]he first message ... may be a radio resource control connection request ... message" and Lou's paragraph [0248] states that "the terminal device sends the generated information about the first network slice to the network device in 5302."
However, while Lou discusses a terminal device selecting "a network slice identifier of a
network slice with a highest priority[,]" it is the network slice identifier itself that is selected as the information about the first network slice and it is this information that is included in 5302. Consequently, Lou is not concerned with priority access to a network slice, as recited in claim 1, but is instead concerned with picking a high priority network slice. Lou is silent regarding the terminal device having priority access to the network slice, in general.
This conclusion is further reinforced by Lou's use of the same information in 5302 regardless of whether the terminal device selects a high priority network slice or is preconfigured with a unique network slice identifier. This is at least because none of the contents of Lou's 5302 are an indication of priority access of the wireless device to a network slice and instead are, at most, merely an indication of the network slice itself.
Lastly, page 5 of Office Action states "eMBB service (==priority access)" when discussing Lou's paragraphs [0223]-[0228].
First, as discussed above, an indication of a service type is not an indication of priority access of the wireless device to a network slice. Second, enhanced mobile broadband (eMBB) does not have an inherently higher priority than URLLC or mMTC. Therefore, Lou does not disclose "transmit, to a base station, a radio resource control (RRC) request message comprising an indication of priority access of the wireless device to a network slice[,]" as recited in claim 1.
For at least the above reasons, independent claim 1 is patentable over Lou..”
(See REMAKRs).
Examiner’s Response:
The examiner respectfully disagrees. The claims merely recites, A wireless device, “transmit, to a base station, a radio resource control (RRC) request message comprising an indication of priority access of the wireless device to a network slice” without explaining what “priority access” any more detail.
As per Fig. 1, Fig. 3, and paragraphs 0223-0228, 0247, 0248, 0016-0017, 0055-0056, 0082-0082, 0151 of LOU (which are cited by the examiner along with other supporting paragraphs as shown here), Terminal Device (==wireless device in claim ) sends “FIRST MESSAGE” or “RRC Request” to Network Device ([0302], [0223], [0247]. Aforesaid RRC request or “FIRST MESSAGE” indicates service type supports needed by the aforesaid terminal device from the network slice, i.e eMBB, mMTC, URLLC : [0224]). ). It is well known in the art that 3GPP classifies 5G network slices into three main type of service, “In enhanced mobile broadband (enhanced mobile broadband, eMBB) network slice, a massive machine type communication (massive machine type communication, mMTC) network slice, and an ultra-reliable and low latency communications (ultra-reliable and low latency communications, URLLC) network slice”. Aforesaid URLLC service has highest priority and requires “a relatively high requirement for a latency and reliability” than aforesaid eMBB, mMTC. Aforesaid terminal devices requires highest priority access for URLLC service and sends that information to network slice : [0216]).
The Applicant is encouraged to amend the claims to clarify the definition of “priority access” to make clear “indication of priority access (e.g., because the wireless device has priority over other wireless devices), the RRC response message may indicate acceptance associated with the RRC request message.” per Par. 0196 of Applicant’s specification. Further, the Applicant should additionally amend the claims per paragraphs 0199-0202, 0207., 0216-0218. (Applicant’s specification, Qiao et al. US 20230422293 A1 ).
Thus claim limitation as written, clearly is taught by cited prior art LOU.
Regarding other independent claims 7, 15: the applicant alleges that these independent claims are allowable since they are similar to aforesaid independent claim above. The examiner respectfully disagrees in view of the above explanation of above independent claim. Thus the rejection is deemed proper.
Regarding all dependent claims: the applicant alleges that all dependent claims are allowable since they depend from all the independent claims above. The examiner respectfully disagrees in view of the above explanation of independent claims. Thus the rejection is deemed proper.
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 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.
(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.
Claims 1-20 are rejected under 35 U.S.C. 102 (a)(1) ) as being anticipated by LOU et al. (US 20190230584 A1; hereinafter as “LOU”; provided in IDS).
Examiner’s note: in what follows, references are drawn to LOU unless otherwise mentioned.
With respect to independence claim:
Regarding claim 1, LOU teaches, A wireless device (see fig. 1: terminal Device with high requirement for rate and mobility : [0216], see fig. 3: terminal device, Fig. 8-9: terminal Device) comprising:
PNG
media_image1.png
467
643
media_image1.png
Greyscale
PNG
media_image2.png
406
441
media_image2.png
Greyscale
one or more processors (fig. 8 processing unit 801, Fig. 9 Processor ); and
memory storing instructions that, when executed by the one or more processors (see fig.8 processor with memory: : [0340], , Fig. 9 processor and memory : [0340]-[0342), cause the wireless device (see fig. 1: terminal Device with high requirement for rate and mobility : [0216], see fig. 3: terminal device, Fig. 8-9: terminal Device) to:
transmit, to a base station (==Network Device in Fig. 3), a radio resource control (RRC) request message comprising an indication of priority access of the wireless device to a network slice (see fig. 3 element 301, element 302: UE sends First Message which is a RRC message including first information ; “ S301. A terminal device generates first information, where the first information includes any one or any combination of the following: information about a first network slice (==network slice in claim ), first service information, and access information of the terminal device.”: [0223]-[0228]; “ The service type is an identifier used to uniquely determine a service type, for example, used to indicate a service type such as an eMBB service (==priority access), a URLLC service, and an mMTC service. One network slice may be corresponding to one service type. Therefore, there is a mapping relationship between a service type and a network slice. The first service information may include a service type.”: [0233]; “ the first message is an air interface message, for example, may be a radio resource control connection request (Radio Resource Control Connection Request, RRC Connection Request) message, ”: [0247]; “ terminal device generates the information about the first network slice in S301, and the terminal device sends the generated information (==access of the wireless device to a network slice ) about the first network slice to the network device in S302,”: [0248]; highest priority access information of network slice: [0016]-[0017]; [0055]-[0056]; [0082]-[0084], “sending, by a terminal device, a first message to a network device, where the first message is used to request to select a network slice for the terminal device; the first message includes first information, and the first information includes any one or any combination of the following: information about a first network slice, first service information, and access information of the terminal device; and the first network slice is a network slice corresponding to a service initiated by the terminal device; or the first network slice is a network slice with a highest priority; or when the terminal device has preconfigured an identifier of a unique network slice, the first network slice is the unique network slice: [0151] ); and
receive, from the base station (==Network Device in Fig. 3), an RRC response message indicating an acceptance associated with the RRC request message (==fig. 3 RRC Response message from Network Device to Terminal Device : [0250]-[0256]; “ S304. The network device sends a second message to the terminal device, where the second message is used to indicate the network slice selected by the network device for the terminal device.
The second message may include information such as a network slice identifier, a globally unique temporary identity (Globally Unique Temporary Identity, GUTI), a network functional entity identifier, and network slice feature information, for example, a tenant (Tenant) identifier corresponding to a network slice, a network slice that supports a service type, or some or all service information supported by a network slice. The network slice that supports a service type may be an eMBB network slice, a URLLC network slice, or the like. The some or all service information supported by a network slice may be an application identifier, a flow identifier, a data packet identifier, a tunnel identifier, a radio bearer identifier, a service type, a UE usage type, an APN address, an APN identifier, or the like.
The second message may carry a network slice identifier, network slice feature information, and the like, to indicate the network slice selected by the network device for the terminal device. For example, the second message may carry an identifier, a frequency, bandwidth, air interface resource configuration, an access control configuration, and the like of a cell in which the network slice is located. .”: [0258]-[0262]; “ The second message is an air interface message, for example, may be an RRC connection setup (RRC Connection Setup) message, an RRC connection reestablishment (RRC Connection Reestablishment) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message,”: [0263]; “and receiving, by the terminal device, a second message sent by the network device, where the second message is used to indicate a network slice selected by the network device for the terminal device.”:[0151]).
Regarding claim 7, LOU teaches, A base station (==Network Device in Fig. 3), comprising :one or more processors (fig. 8 processing unit 801, Fig. 9 Processor ); and
memory storing instructions that, when executed by the one or more processors (see fig.8 processor with memory: : [0340], , Fig. 9 processor and memory : [0340]-[0342) ,
cause the base station (==Network Device in Fig. 3), to:
receive, from a wireless device (see fig. 1: terminal Device with high requirement for rate and mobility : [0216], see fig. 3: terminal device, Fig. 8-9: terminal Device), a radio resource control (RRC) request message comprising an indication of priority access of the wireless device to a network slice (see fig. 3 element 301, element 302: UE sends First Message which is a RRC message including first information ; “ S301. A terminal device generates first information, where the first information includes any one or any combination of the following: information about a first network slice (==network slice in claim ), first service information, and access information of the terminal device.”: [0223]-[0228]; “ The service type is an identifier used to uniquely determine a service type, for example, used to indicate a service type such as an eMBB service (==priority access), a URLLC service, and an mMTC service. One network slice may be corresponding to one service type. Therefore, there is a mapping relationship between a service type and a network slice. The first service information may include a service type.”: [0233]; “ the first message is an air interface message, for example, may be a radio resource control connection request (Radio Resource Control Connection Request, RRC Connection Request) message, ”: [0247]; “ terminal device generates the information about the first network slice in S301, and the terminal device sends the generated information (==access of the wireless device to a network slice ) about the first network slice to the network device in S302,”: [0248]; highest priority access information of network slice: [0016]-[0017]; [0055]-[0056]; [0082]-[0084], “sending, by a terminal device, a first message to a network device, where the first message is used to request to select a network slice for the terminal device; the first message includes first information, and the first information includes any one or any combination of the following: information about a first network slice, first service information, and access information of the terminal device; and the first network slice is a network slice corresponding to a service initiated by the terminal device; or the first network slice is a network slice with a highest priority; or when the terminal device has preconfigured an identifier of a unique network slice, the first network slice is the unique network slice: [0151]); and
transmit, to the wireless device (see fig. 1: terminal Device with high requirement for rate and mobility : [0216], see fig. 3: terminal device, Fig. 8-9: terminal Device), based on the indication of priority access, an RRC response message indicating an acceptance associated with the RRC request message (==fig. 3 RRC Response message from Network Device to Terminal Device : [0250]-[0256]; “ S304. The network device sends a second message to the terminal device, where the second message is used to indicate the network slice selected by the network device for the terminal device.
The second message may include information such as a network slice identifier, a globally unique temporary identity (Globally Unique Temporary Identity, GUTI), a network functional entity identifier, and network slice feature information, for example, a tenant (Tenant) identifier corresponding to a network slice, a network slice that supports a service type, or some or all service information supported by a network slice. The network slice that supports a service type may be an eMBB network slice, a URLLC network slice, or the like. The some or all service information supported by a network slice may be an application identifier, a flow identifier, a data packet identifier, a tunnel identifier, a radio bearer identifier, a service type, a UE usage type, an APN address, an APN identifier, or the like.
The second message may carry a network slice identifier, network slice feature information, and the like, to indicate the network slice selected by the network device for the terminal device. For example, the second message may carry an identifier, a frequency, bandwidth, air interface resource configuration, an access control configuration, and the like of a cell in which the network slice is located. .”: [0258]-[0262]; “ The second message is an air interface message, for example, may be an RRC connection setup (RRC Connection Setup) message, an RRC connection reestablishment (RRC Connection Reestablishment) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message,”: [0263]; “and receiving, by the terminal device, a second message sent by the network device, where the second message is used to indicate a network slice selected by the network device for the terminal device.”:[0151]).
Regarding claim 15, LOU teaches, A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device (see fig. 1: terminal Device with high requirement for rate and mobility : [0216], see fig. 3: terminal device, Fig. 8-9: terminal Device),
cause the wireless device (see fig. 1: terminal Device with high requirement for rate and mobility : [0216], see fig. 3: terminal device, Fig. 8-9: terminal Device) to:
transmit, to a base station (==Network Device in Fig. 3),, a radio resource control (RRC) request message comprising an indication of priority access of the wireless device to a network slice (see fig. 3 element 301, element 302: UE sends First Message which is a RRC message including first information ; “ S301. A terminal device generates first information, where the first information includes any one or any combination of the following: information about a first network slice (==network slice in claim ), first service information, and access information of the terminal device.”: [0223]-[0228]; “ The service type is an identifier used to uniquely determine a service type, for example, used to indicate a service type such as an eMBB service (==priority access), a URLLC service, and an mMTC service. One network slice may be corresponding to one service type. Therefore, there is a mapping relationship between a service type and a network slice. The first service information may include a service type.”: [0233]; “ the first message is an air interface message, for example, may be a radio resource control connection request (Radio Resource Control Connection Request, RRC Connection Request) message, ”: [0247]; “ terminal device generates the information about the first network slice in S301, and the terminal device sends the generated information (==access of the wireless device to a network slice ) about the first network slice to the network device in S302,”: [0248]; highest priority access information of network slice: [0016]-[0017]; [0055]-[0056]; [0082]-[0084], “sending, by a terminal device, a first message to a network device, where the first message is used to request to select a network slice for the terminal device; the first message includes first information, and the first information includes any one or any combination of the following: information about a first network slice, first service information, and access information of the terminal device; and the first network slice is a network slice corresponding to a service initiated by the terminal device; or the first network slice is a network slice with a highest priority; or when the terminal device has preconfigured an identifier of a unique network slice, the first network slice is the unique network slice: [0151] ); and
receive, from the base station (==Network Device in Fig. 3),, an RRC response message indicating an acceptance associated with the RRC request message (==fig. 3 RRC Response message from Network Device to Terminal Device : [0250]-[0256]; “ S304. The network device sends a second message to the terminal device, where the second message is used to indicate the network slice selected by the network device for the terminal device.
The second message may include information such as a network slice identifier, a globally unique temporary identity (Globally Unique Temporary Identity, GUTI), a network functional entity identifier, and network slice feature information, for example, a tenant (Tenant) identifier corresponding to a network slice, a network slice that supports a service type, or some or all service information supported by a network slice. The network slice that supports a service type may be an eMBB network slice, a URLLC network slice, or the like. The some or all service information supported by a network slice may be an application identifier, a flow identifier, a data packet identifier, a tunnel identifier, a radio bearer identifier, a service type, a UE usage type, an APN address, an APN identifier, or the like.
The second message may carry a network slice identifier, network slice feature information, and the like, to indicate the network slice selected by the network device for the terminal device. For example, the second message may carry an identifier, a frequency, bandwidth, air interface resource configuration, an access control configuration, and the like of a cell in which the network slice is located. .”: [0258]-[0262]; “ The second message is an air interface message, for example, may be an RRC connection setup (RRC Connection Setup) message, an RRC connection reestablishment (RRC Connection Reestablishment) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message,”: [0263]; “and receiving, by the terminal device, a second message sent by the network device, where the second message is used to indicate a network slice selected by the network device for the terminal device.”:[0151]).
With respect to dependence claim:
Regarding claim 2, LOU teaches, The wireless device of claim 1, wherein the instructions further cause the wireless device (see fig. 1: terminal Device with high requirement for rate and mobility : [0216], see fig. 3: terminal device, Fig. 8-9: terminal Device) to receive, from the base station (==Network Device in Fig. 3),, a parameter indicating the priority access of the wireless device to the network slice (“second message is used to indicate a network slice selected by the network device for the terminal device.”: [0010]; highest priority access for wireless device : [0055]-[0056]; “the first network slice is a network slice corresponding to a service initiated by the terminal device; or the first network slice is a network slice with a highest priority; or when the terminal device has preconfigured an identifier of a unique network slice, the first network slice is the unique network slice; selecting, by the network device, a network slice for the terminal device based on the first information; and sending, by the network device, a second message to the terminal device, where the second message is used to indicate the network slice selected by the network device for the terminal device.”:{0166]).
Regarding claim 3, LOU teaches, The wireless device of claim 1, wherein the priority access is indicated by one or more bits of a temporary mobile subscriber identity (TMSI) of the wireless device (“the first network slice is a network slice corresponding to a service initiated by the terminal device; or the first network slice is a network slice with a highest priority; or when the terminal device has preconfigured an identifier of a unique network slice, the first network slice is the unique network slice; selecting, by the network device, a network slice for the terminal device based on the first information; and sending, by the network device, a second message to the terminal device, where the second message is used to indicate the network slice selected by the network device for the terminal device”:[0166]; “ Optionally, the information about the first network slice may further include a user identifier, a network functional entity identifier, a public land mobile network (Public Land Mobile Network, PLMN) identifier selected by the terminal device, and the like. For example, the user identifier may be an international mobile subscriber identity (International Mobile Subscriber Identification Number, IMSI), a globally unique temporary user equipment identity (Globally Unique Temporary UE Identity, GUTI), or the like.”: 0225]).
Regarding claim 4, LOU teaches, The wireless device of claim 1, wherein the RRC request message indicates a slice/service type (SST) of the network slice ( “ The first information may be used by a network device to select a network slice for the terminal device. The information about the first network slice is used to indicate a network slice, and the information about the first network slice may be a network slice identifier, network slice feature information, or the like. For example, the information about the first network slice may include a tenant (Tenant) identifier corresponding to a network slice and a network slice that supports a service type. The network slice that supports a service type may be an eMBB network slice, a URLLC network slice, or the like.
[0225] Optionally, the information about the first network slice may further include a user identifier, a network functional entity identifier, a public land mobile network (Public Land Mobile Network, PLMN) identifier selected by the terminal device, and the like. For example, the user identifier may be an international mobile subscriber identity (International Mobile Subscriber Identification Number, IMSI), a globally unique temporary user equipment identity (Globally Unique Temporary UE Identity, GUTI), or the like.
[0226] Optionally, the first service information is used to indicate a service initiated by the terminal device. For example, the first service information may be a service application identifier, a flow identifier, a data packet identifier, a tunnel identifier, a radio bearer identifier, a service type (Service Type), a user usage type (UE Usage Type), an access point name (Access Point Name, APN) address, an APN identifier, or the like.
[0227] The first service information is defined in a standard, and is briefly described below.
[0228] Service application identifier: The service application identifier is an application layer identifier used to uniquely determine a specific service, for example, used to indicate a WeChat service, a virtual reality service, an in-vehicle service, or the like. One network slice may carry one or one type of service. Therefore, there is a mapping relationship between a service app ”: [0224]-[0228] ).
Regarding claim 5, LOU teaches, The wireless device of claim 1, wherein the indication of priority access is an ns-PriorityAccess information element in the RRC message (RRC message : [0247]; “ select a network slice identifier of a network slice with a highest priority as the information about the first network slice; or”: [0347]).
Regarding claim 6, LOU teaches, The wireless device of claim 1, wherein the indication of priority access is an establishment cause information element in the RRC message (“ The terminal device selects a network slice identifier of a network slice with a highest priority as the information about the first network slice. Priorities of different network slices may be delivered by the network device to the terminal device. For example, when the terminal device has preconfigured at least two network slice identifiers, the terminal device selects a network slice identifier of a network slice with a highest priority from the preconfigured at least two network slice identifiers as the information about the first network slice based on a network slice priority.”: [0242]).
Regarding claim 8, LOU teaches, The base station of claim 7, wherein the instructions further cause the base station to transmit, to the wireless device, a parameter indicating the priority access of the wireless device to the network slice (Regarding claim 8, the claim is interpreted and rejected for the same reason as set forth in claim 2).
Regarding claim 9, LOU teaches, The base station of claim 8, wherein the parameter indicating the priority access is included in a message comprising a random access preamble assignment (“ For example, when the access information of the terminal device is a level of the terminal device, the network device may select, as the network slice selected for the terminal device, a network slice suitable for the level of the terminal device based on the level of the terminal device and a preconfigured mapping relationship between a level of the terminal device and a network slice. When the access information of the terminal device is a RACH channel type, the network device may select, as the network slice selected for the terminal device, a network slice suitable for the RACH channel type based on the RACH channel type and a preconfigured mapping relationship between a RACH channel type and a network slice. When the access information of the terminal device is a random access preamble sequence, because different network slices are corresponding to different random access preamble sequences, the network device may identify a network slice corresponding to the random access preamble sequence, and use the network slice as the network slice selected for the terminal device.”: [0256]).
Regarding claim 10, LOU teaches, The base station of claim 7, wherein the priority access is indicated by one or more bits of a temporary mobile subscriber identity (TMSI) of the wireless device (Regarding claim 10, the claim is interpreted and rejected for the same reason as set forth in claim 3).
Regarding claim 11, LOU teaches, The base station of claim 7, wherein the RRC request message indicates a slice/service type (SST) of the network slice (Regarding claim 11, the claim is interpreted and rejected for the same reason as set forth in claim 4)..
Regarding claim 12, LOU teaches, The base station of claim 7, wherein the indication of priority access is an ns-PriorityAccess information element in the RRC message (Regarding claim 12, the claim is interpreted and rejected for the same reason as set forth in claim 5).
Regarding claim 13, LOU teaches, The base station of claim 7, wherein the indication of priority access is an establishment cause information element in the RRC message (Regarding claim 13, the claim is interpreted and rejected for the same reason as set forth in claim 6).
Regarding claim 14, LOU teaches, The base station of claim 7, wherein the RRC request message indicates a network slice type of the network slice (“ It should be noted that the access barring information corresponding to each of the at least one network slice that is included in the fourth message may be in a plurality of representation forms. For example, network slices may be classified into different types based on attributes of the network slices. Each network slice type may include one or more network slices, and each network slice type is corresponding to one piece of access barring information. For another example, network slices are randomly grouped. Each group of network slices may include one or more network slices, and each group of network slices is corresponding to one piece of access barring information.”: [0288]) .
Regarding claim 16, LOU teaches, The non-transitory computer-readable medium of claim 15, wherein the instructions further cause the wireless device to receive, from the base station, a parameter indicating the priority access of the wireless device to the network slice (Regarding claim 16, the claim is interpreted and rejected for the same reason as set forth in claim 2).
Regarding claim 17, LOU teaches, The non-transitory computer-readable medium of claim 15, wherein the priority access is indicated by one or more bits of a temporary mobile subscriber identity (TMSI) of the wireless device (Regarding claim 17, the claim is interpreted and rejected for the same reason as set forth in claim 3).
Regarding claim 18, LOU teaches, The non-transitory computer-readable medium of claim 15, wherein the RRC request message indicates a slice/service type (SST) of the network slice (Regarding claim 18, the claim is interpreted and rejected for the same reason as set forth in claim 4).
Regarding claim 19, LOU teaches, The non-transitory computer-readable medium of claim 15, wherein the indication of priority access is an ns-PriorityAccess information element in the RRC message (Regarding claim 19, the claim is interpreted and rejected for the same reason as set forth in claim 5).
Regarding claim 20, LOU teaches, The non-transitory computer-readable medium of claim 15, wherein the indication of priority access is an establishment cause information element in the RRC message (Regarding claim 20, the claim is interpreted and rejected for the same reason as set forth in claim 6).
Conclusion
THIS ACTION IS MADE FINAL. 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 M MOSTAZIR RAHMAN whose telephone number is (571)272-4785. The examiner can normally be reached 8:30am-5:00pm PST.
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, Derrick Ferris can be reached at 571-272-3123. 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.
/M Mostazir Rahman/Examiner, Art Unit 2411
/DERRICK W FERRIS/Supervisory Patent Examiner, Art Unit 2411
Prosecution Insights