Datasets:

lcolonn

/

patfig

like 0

[ "FIG7" ]

[ "FIG7 is a first schematic structural diagram of a communications device according to an embodiment of this application" ]

[ "FIG7 is a first schematic structural diagram of a communications device according to an embodiment of this application. Referring to FIG7, the communications device 70 includes a first determining unit 701 and a second determining unit 702." ]

[ { "element_identifier": "8", "terms": [ "symbol index values are" ] }, { "element_identifier": "7", "terms": [ "symbol index values are" ] }, { "element_identifier": "701", "terms": [ "first determining unit" ] }, { "element_identifier": "702", "terms": [ "second determining unit" ] }, { "element_identifier": "703", "terms": [ "sending unit" ] }, { "element_identifier": "70", "terms": [ "communications device" ] } ]

[ "701", "702", "70", "7", "702", "70", "8", "703", "27" ]

[ "FIG10" ]

[ "FIG10 is a schematic hardware structural diagram of a communications device 40 according to an embodiment of this application " ]

[ "FIG10 is a schematic hardware structural diagram of a communications device 40 according to an embodiment of this application. The communications device 40 includes at least one processor 401, a communications bus 402, a memory 403, and at least one communications interface 404." ]

[ { "element_identifier": "704", "terms": [ "receiving unit" ] }, { "element_identifier": "9", "terms": [ "symbol index value is" ] }, { "element_identifier": "401", "terms": [ "processor" ] }, { "element_identifier": "403", "terms": [ "memory" ] }, { "element_identifier": "701", "terms": [ "first determining unit" ] }, { "element_identifier": "40", "terms": [ "communications device" ] }, { "element_identifier": "702", "terms": [ "second determining unit" ] }, { "element_identifier": "402", "terms": [ "communications bus" ] }, { "element_identifier": "10", "terms": [ "andFIG.", "downlink control channel is", "As shown in Table" ] }, { "element_identifier": "404", "terms": [ "communications interface" ] }, { "element_identifier": "70", "terms": [ "communications device" ] } ]

[ "701", "702", "70", "9", "401", "704", "40", "402", "403", "404", "10", "28" ]

[ "FIG1" ]

[ "FIG1 is a schematic diagram of an application architecture for a frequency hopping processing method according to an embodiment of this application" ]

[ "A frequency hopping processing method and a device provided in embodiments of this application may be applied to frequency hopping processing of a shared channel in an NR network. As shown in FIG1, FIG1 shows a communications system provided in an embodiment of this application. The communications system includes an access device and one or more communications apparatuses connected to the access device. Both the access device and the communications apparatus may support frequency hopping processing of a shared channel." ]

[ { "element_identifier": "201711148953", "terms": [ "Chinese Patent Application No." ] }, { "element_identifier": "17", "terms": [ "November" ] }, { "element_identifier": "1", "terms": [ "Manner" ] }, { "element_identifier": "0", "terms": [ "is", "are" ] }, { "element_identifier": "10", "terms": [ "andFIG.", "downlink control channel is", "As shown in Table" ] }, { "element_identifier": "40", "terms": [ "communications device" ] }, { "element_identifier": "15", "terms": [ "RBs may be" ] }, { "element_identifier": "2", "terms": [ "Manner" ] }, { "element_identifier": "14", "terms": [ "3A." ] }, { "element_identifier": "9", "terms": [ "symbol index value is" ] }, { "element_identifier": "11", "terms": [ "symbol index value is" ] }, { "element_identifier": "6", "terms": [ "symbol index value is" ] }, { "element_identifier": "5", "terms": [ "symbol index values are" ] }, { "element_identifier": "7", "terms": [ "symbol index values are" ] }, { "element_identifier": "8", "terms": [ "symbol index values are" ] }, { "element_identifier": "13", "terms": [ "symbol index value is" ] }, { "element_identifier": "3", "terms": [ "Manner" ] }, { "element_identifier": "4", "terms": [ "following Table" ] }, { "element_identifier": "70", "terms": [ "communications device" ] }, { "element_identifier": "701", "terms": [ "first determining unit" ] }, { "element_identifier": "702", "terms": [ "second determining unit" ] }, { "element_identifier": "703", "terms": [ "sending unit" ] }, { "element_identifier": "704", "terms": [ "receiving unit" ] }, { "element_identifier": "401", "terms": [ "processor" ] }, { "element_identifier": "402", "terms": [ "communications bus" ] }, { "element_identifier": "403", "terms": [ "memory" ] }, { "element_identifier": "404", "terms": [ "communications interface" ] }, { "element_identifier": "80", "terms": [ "communications device" ] } ]

[ "1", "101", "102", "2", "23" ]

[ "FIG11", " FIG12", " FIG9" ]

[ "FIG9 is a schematic structural diagram of Embodiment 1 of a WLAN system resource indication apparatus provided in the present invention ", "FIG11 is a schematic structural diagram of Embodiment 3 of a WLAN system resource indication apparatus provided in the present invention ", "FIG12 is a schematic structural diagram of Embodiment 4 of a WLAN system resource indication apparatus provided in the present invention" ]

[ "FIG9 is a schematic structural diagram of Embodiment 1 of a WLAN system resource indication apparatus provided in the present invention. The apparatus may be integrated in the access point in the foregoing embodiment. As shown in FIG9, the apparatus includes a generation module 901 and a sending module 902. ", "FIG11 is a schematic structural diagram of Embodiment 3 of a WLAN system resource indication apparatus provided in the present invention. The apparatus may be integrated in the station in the foregoing embodiment. As shown in FIG11, the appratus includes a receiving module 111 and a reading module 112.", "Based on FIG11, the apparatus may further include a first searching module 113. ", "FIG12 is a schematic structural diagram of Embodiment 4 of a WLAN system resource indication apparatus provided in the present invention. The frequency domain resource allocation information includes an index in a frequency domain resource allocation table. Correspondingly," ]

[ { "element_identifier": "12", "terms": [ "eighth. Indices", "example" ] }, { "element_identifier": "11", "terms": [ "occupy", "example" ] }, { "element_identifier": "901", "terms": [ "generation module" ] }, { "element_identifier": "9", "terms": [ "Table" ] }, { "element_identifier": "113", "terms": [ "first searching module" ] }, { "element_identifier": "902", "terms": [ "sending module" ] }, { "element_identifier": "112", "terms": [ "reading module" ] }, { "element_identifier": "111", "terms": [ "receiving module" ] }, { "element_identifier": "10", "terms": [ "fifth station in" ] }, { "element_identifier": "903", "terms": [ "coding module" ] } ]

[ "901", "902", "9", "901", "10", "111", "903", "902", "112", "11", "112", "12", "111", "113", "47" ]

[ "FIG15", " FIG16" ]

[ "FIG15 is a schematic structural diagram of Embodiment 7 of a WLAN system resource indication apparatus provided in the present invention ", "FIG16 is a schematic structural diagram of Embodiment 8 of a WLAN system resource indication apparatus provided in the present invention " ]

[ "FIG15 is a schematic structural diagram of Embodiment 7 of a WLAN system resource indication apparatus provided in the present invention. The apparatus may be integrated in an access point. As shown in FIG15, the apparatus may include a processor 150 and a transmitter 151. The apparatus is configured to perform the method embodiment on an access point side. Their implementation principles and technical effects are similar. The transmitter 151 sends data to a station side, and other operation is all performed by the processor 150. ", "FIG16 is a schematic structural diagram of Embodiment 8 of a WLAN system resource indication apparatus provided in the present invention. The apparatus may be integrated on a station side. As shown in FIG16, the apparatus may include a receiver 160 and a processor 161. The apparatus is configured to perform the foregoing method on a station side. Their implementation principles and technical effects are similar. The receiver 160 receives data sent by an AP side, and other operation is all performed by the processor 161." ]

[ { "element_identifier": "14", "terms": [ "sixth. Indices" ] }, { "element_identifier": "160", "terms": [ "receiver" ] }, { "element_identifier": "151", "terms": [ "transmitter" ] }, { "element_identifier": "16", "terms": [ "index" ] }, { "element_identifier": "111", "terms": [ "receiving module" ] }, { "element_identifier": "112", "terms": [ "reading module" ] }, { "element_identifier": "161", "terms": [ "processor" ] }, { "element_identifier": "115", "terms": [ "determining module" ] }, { "element_identifier": "15", "terms": [ "sixth. Indices" ] }, { "element_identifier": "150", "terms": [ "processor" ] }, { "element_identifier": "13", "terms": [ "eighth. Indices" ] } ]

[ "111", "112", "13", "112", "14", "150", "114", "111", "115", "151", "15", "160", "161", "16", "48" ]

[ "FIG3" ]

[ "FIG3 is a conceptual diagram illustrating a communication node constituting a cellular communication system according to an exemplary embodiment of the present disclosure" ]

[ "FIG3 is a conceptual diagram illustrating embodiments of a communication node constituting a cellular communication system. As shown in FIG3, a communication node 300 may include at least one processor 310, a memory 320, and a transceiver 330 connected to a network for performing communications. Additionally, the communication node 300 may further include an input interface device 340, an output interface device 350, a storage device 360, and the like. Each component included in the communication node 300 may be configured to communicate with each other as connected via a bus 370." ]

[ { "element_identifier": "236", "terms": [ "UEs" ] }, { "element_identifier": "310", "terms": [ "processor" ] }, { "element_identifier": "350", "terms": [ "output interface device" ] }, { "element_identifier": "3", "terms": [ "pattern described in Table" ] }, { "element_identifier": "4", "terms": [ "pattern described in Table" ] }, { "element_identifier": "360", "terms": [ "storage device" ] }, { "element_identifier": "300", "terms": [ "communication node" ] }, { "element_identifier": "370", "terms": [ "bus" ] }, { "element_identifier": "320", "terms": [ "memory" ] }, { "element_identifier": "340", "terms": [ "input interface device" ] }, { "element_identifier": "235", "terms": [ "UEs" ] }, { "element_identifier": "330", "terms": [ "transceiver" ] } ]

[ "3", "300", "320", "310", "370", "360", "340", "350", "330", "4", "235", "236", "21" ]

[ "FIG7" ]

[ "FIG7 is a conceptual diagram illustrating a DL-UL transmission period including DL resources, UL resources, and SL resources in a communication system according to an exemplary embodiment of the present disclosure" ]

[ "FIG7 is a conceptual diagram illustrating a first exemplary embodiment of a DL-UL transmission period including DL resources, UL resources, and SL resources in a communication system. As shown in FIG7, a DL-UL transmission period may be configured, and DL resources and UL resources may be configured within the DL-UL transmission period. Additionally, SL resources may be additionally configured within the DL-UL transmission period. In particular, the DL-UL transmission period may be referred to as a DL-SL-UL transmission period. A resource that is not configured as a DL resource, a UL resource, or an SL resource within the DL-UL transmission period may be configured as a flexible (FL) resource, and the FL resource may be overridden to a DL resource, a UL resource, or an SL resource.", "A method of signaling information indicating the DL resources, the UL resources, and the SL resources shown in FIG7 may be configured follows." ]

[ { "element_identifier": "6", "terms": [ "in Table" ] }, { "element_identifier": "22", "terms": [ "July" ] }, { "element_identifier": "13", "terms": [ "andFIG." ] }, { "element_identifier": "2", "terms": [ "example within", "shown below in Table" ] }, { "element_identifier": "140", "terms": [ "cellular communication system" ] }, { "element_identifier": "100", "terms": [ "vehicle", "vehicles" ] }, { "element_identifier": "110", "terms": [ "vehicles", "vehicle" ] }, { "element_identifier": "120", "terms": [ "infrastructure" ] }, { "element_identifier": "130", "terms": [ "person" ] }, { "element_identifier": "802", "terms": [ "technology defined in IEEE" ] }, { "element_identifier": "210", "terms": [ "base station" ] }, { "element_identifier": "220", "terms": [ "relay", "relays" ] }, { "element_identifier": "236", "terms": [ "UEs" ] }, { "element_identifier": "231", "terms": [ "UEs" ] }, { "element_identifier": "250", "terms": [ "S-GW", "UPF" ] }, { "element_identifier": "260", "terms": [ "P-GW", "SMF" ] }, { "element_identifier": "270", "terms": [ "MME", "AMF" ] }, { "element_identifier": "300", "terms": [ "communication node" ] }, { "element_identifier": "310", "terms": [ "processor" ] }, { "element_identifier": "320", "terms": [ "memory" ] }, { "element_identifier": "330", "terms": [ "transceiver" ] }, { "element_identifier": "340", "terms": [ "input interface device" ] }, { "element_identifier": "350", "terms": [ "output interface device" ] }, { "element_identifier": "360", "terms": [ "storage device" ] }, { "element_identifier": "370", "terms": [ "bus" ] }, { "element_identifier": "233", "terms": [ "UEs" ] }, { "element_identifier": "234", "terms": [ "UEs" ] }, { "element_identifier": "235", "terms": [ "UEs" ] }, { "element_identifier": "1", "terms": [ "Table" ] }, { "element_identifier": "3", "terms": [ "pattern described in Table" ] }, { "element_identifier": "4", "terms": [ "pattern described in Table" ] }, { "element_identifier": "0", "terms": [ "about" ] }, { "element_identifier": "5", "terms": [ "pattern described in Table" ] }, { "element_identifier": "20", "terms": [ "less than about" ] }, { "element_identifier": "7", "terms": [ "in Table" ] }, { "element_identifier": "8", "terms": [ "described in Table" ] }, { "element_identifier": "9", "terms": [ "parameters listed in Table" ] } ]

[ "7", "23" ]

[ "FIG10", " FIG9" ]

[ "FIG9 is a conceptual diagram illustrating a slot configured by TDD-UL-DL-configuration dedicated information in a communication system according to an exemplary embodiment of the present disclosure ", "FIG10 is a conceptual diagram illustrating a slot configured by TDD-UL-DL-configuration dedicated information in a communication system according to another exemplary embodiment of the present disclosure" ]

[ "FIG9 is a conceptual diagram illustrating a first exemplary embodiment of a slot configured by TDD-UL-DL-configuration dedicated information in a communication system. As shown in FIG9, symbols included in one slot may be configured as DL symbols, UL symbols, or SL symbols according to the TDD-UL-DL-configuration dedicated information. In particular, one slot may not include an FL symbol. ", "FIG10 is a conceptual diagram illustrating a second exemplary embodiment of a slot configured by TDD-UL-DL-configuration dedicated information in a communication system. As shown in FIG10, symbols included in one slot may be configured as DL symbols, UL symbols, or SL symbols according to the TDD-UL-DL-configuration dedicated information. Among the symbols included in one slot, a symbol that is not configured as a DL symbol, a UL symbol, or an SL symbol may be an FL symbol." ]

[ { "element_identifier": "6", "terms": [ "in Table" ] }, { "element_identifier": "22", "terms": [ "July" ] }, { "element_identifier": "13", "terms": [ "andFIG." ] }, { "element_identifier": "2", "terms": [ "example within", "shown below in Table" ] }, { "element_identifier": "140", "terms": [ "cellular communication system" ] }, { "element_identifier": "100", "terms": [ "vehicle", "vehicles" ] }, { "element_identifier": "110", "terms": [ "vehicles", "vehicle" ] }, { "element_identifier": "120", "terms": [ "infrastructure" ] }, { "element_identifier": "130", "terms": [ "person" ] }, { "element_identifier": "802", "terms": [ "technology defined in IEEE" ] }, { "element_identifier": "210", "terms": [ "base station" ] }, { "element_identifier": "220", "terms": [ "relay", "relays" ] }, { "element_identifier": "236", "terms": [ "UEs" ] }, { "element_identifier": "231", "terms": [ "UEs" ] }, { "element_identifier": "250", "terms": [ "S-GW", "UPF" ] }, { "element_identifier": "260", "terms": [ "P-GW", "SMF" ] }, { "element_identifier": "270", "terms": [ "MME", "AMF" ] }, { "element_identifier": "300", "terms": [ "communication node" ] }, { "element_identifier": "310", "terms": [ "processor" ] }, { "element_identifier": "320", "terms": [ "memory" ] }, { "element_identifier": "330", "terms": [ "transceiver" ] }, { "element_identifier": "340", "terms": [ "input interface device" ] }, { "element_identifier": "350", "terms": [ "output interface device" ] }, { "element_identifier": "360", "terms": [ "storage device" ] }, { "element_identifier": "370", "terms": [ "bus" ] }, { "element_identifier": "233", "terms": [ "UEs" ] }, { "element_identifier": "234", "terms": [ "UEs" ] }, { "element_identifier": "235", "terms": [ "UEs" ] }, { "element_identifier": "1", "terms": [ "Table" ] }, { "element_identifier": "3", "terms": [ "pattern described in Table" ] }, { "element_identifier": "4", "terms": [ "pattern described in Table" ] }, { "element_identifier": "0", "terms": [ "about" ] }, { "element_identifier": "5", "terms": [ "pattern described in Table" ] }, { "element_identifier": "20", "terms": [ "less than about" ] }, { "element_identifier": "7", "terms": [ "in Table" ] }, { "element_identifier": "8", "terms": [ "described in Table" ] }, { "element_identifier": "9", "terms": [ "parameters listed in Table" ] } ]

[ "9", "10", "25" ]

[ "FIG11" ]

[ "FIG11 is a conceptual diagram illustrating a DL-UL transmission period including DL resources, UL resources, and SL resources in a communication system according to another exemplary embodiment of the present disclosure" ]

[ "FIG11 is a conceptual diagram illustrating a second exemplary embodiment of a DL-UL transmission period including DL resources, UL resources, and SL resources in a communication system. As shown in FIG11, a DL-UL transmission period may be configured, and a DL period and a UL period may be configured within the DL-UL transmission period. The DL period may be configured by a DL pattern included in the TDD-UL-DL-configuration common information, and the UL period may be configured by a UL pattern included in the TDD-UL-DL-configuration common information." ]

[ { "element_identifier": "6", "terms": [ "in Table" ] }, { "element_identifier": "22", "terms": [ "July" ] }, { "element_identifier": "13", "terms": [ "andFIG." ] }, { "element_identifier": "2", "terms": [ "example within", "shown below in Table" ] }, { "element_identifier": "140", "terms": [ "cellular communication system" ] }, { "element_identifier": "100", "terms": [ "vehicle", "vehicles" ] }, { "element_identifier": "110", "terms": [ "vehicles", "vehicle" ] }, { "element_identifier": "120", "terms": [ "infrastructure" ] }, { "element_identifier": "130", "terms": [ "person" ] }, { "element_identifier": "802", "terms": [ "technology defined in IEEE" ] }, { "element_identifier": "210", "terms": [ "base station" ] }, { "element_identifier": "220", "terms": [ "relay", "relays" ] }, { "element_identifier": "236", "terms": [ "UEs" ] }, { "element_identifier": "231", "terms": [ "UEs" ] }, { "element_identifier": "250", "terms": [ "S-GW", "UPF" ] }, { "element_identifier": "260", "terms": [ "P-GW", "SMF" ] }, { "element_identifier": "270", "terms": [ "MME", "AMF" ] }, { "element_identifier": "300", "terms": [ "communication node" ] }, { "element_identifier": "310", "terms": [ "processor" ] }, { "element_identifier": "320", "terms": [ "memory" ] }, { "element_identifier": "330", "terms": [ "transceiver" ] }, { "element_identifier": "340", "terms": [ "input interface device" ] }, { "element_identifier": "350", "terms": [ "output interface device" ] }, { "element_identifier": "360", "terms": [ "storage device" ] }, { "element_identifier": "370", "terms": [ "bus" ] }, { "element_identifier": "233", "terms": [ "UEs" ] }, { "element_identifier": "234", "terms": [ "UEs" ] }, { "element_identifier": "235", "terms": [ "UEs" ] }, { "element_identifier": "1", "terms": [ "Table" ] }, { "element_identifier": "3", "terms": [ "pattern described in Table" ] }, { "element_identifier": "4", "terms": [ "pattern described in Table" ] }, { "element_identifier": "0", "terms": [ "about" ] }, { "element_identifier": "5", "terms": [ "pattern described in Table" ] }, { "element_identifier": "20", "terms": [ "less than about" ] }, { "element_identifier": "7", "terms": [ "in Table" ] }, { "element_identifier": "8", "terms": [ "described in Table" ] }, { "element_identifier": "9", "terms": [ "parameters listed in Table" ] } ]

[ "11" ]

[ "FIG2" ]

[ "FIG2 is a block diagram of a transmitter system (also known as access network) and a receiver system (also known as user equipment or UE) according to one exemplary embodiment" ]

[ "FIG2 is a simplified block diagram of an embodiment of a transmitter system 210 (also known as the access network) and a receiver system 250 (also known as access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214." ]

[ { "element_identifier": "236", "terms": [ "data source" ] }, { "element_identifier": "210", "terms": [ "transmitter system" ] }, { "element_identifier": "214", "terms": [ "data processor" ] }, { "element_identifier": "230", "terms": [ "processor" ] }, { "element_identifier": "280", "terms": [ "modulator" ] }, { "element_identifier": "242", "terms": [ "RX data processor" ] }, { "element_identifier": "220", "terms": [ "TX MIMO processor" ] }, { "element_identifier": "2", "terms": [ "Layer" ] }, { "element_identifier": "250", "terms": [ "receiver system" ] }, { "element_identifier": "270", "terms": [ "processor" ] }, { "element_identifier": "240", "terms": [ "demodulator" ] }, { "element_identifier": "260", "terms": [ "RX data processor" ] }, { "element_identifier": "200", "terms": [ "MIMO system" ] } ]

[ "200", "00", "210", "214", "230", "242", "000", "250", "260", "272", "280", "220", "232", "240", "270", "236", "32", "2" ]

[ "FIG1" ]

[ "FIG1 shows a diagram of a wireless communication system according to one exemplary embodiment" ]

[ "FIG1 shows a multiple access wireless communication system according to one embodiment of the invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional including 112 and 114. In FIG1, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from access terminal 116 over reverse link 118. Access terminal (AT) 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal (AT) 122 over forward link 126 and receive information from access terminal (AT) 122 over reverse link 124. In a FDD system, communication links 118, 120, 124 and 126 may use different frequency for communication. For example, forward link 120 may use a different frequency then that used by reverse link 118." ]

[ { "element_identifier": "124", "terms": [ "over reverse link" ] }, { "element_identifier": "116", "terms": [ "access terminal", "access terminals" ] }, { "element_identifier": "1", "terms": [ "Layer", "method" ] }, { "element_identifier": "100", "terms": [ "access network" ] }, { "element_identifier": "104", "terms": [ "one including" ] }, { "element_identifier": "112", "terms": [ "antennas" ] }, { "element_identifier": "118", "terms": [ "reverse link" ] }, { "element_identifier": "108", "terms": [ "antennas" ] }, { "element_identifier": "106", "terms": [ "antennas" ] }, { "element_identifier": "110", "terms": [ "another including" ] }, { "element_identifier": "114", "terms": [ "antennas" ] }, { "element_identifier": "120", "terms": [ "forward link", "forward links" ] } ]

[ "110", "112", "118", "116", "120", "108", "104", "106", "100", "124", "114", "1", "31" ]

[ "FIG5", " FIG6", " FIG7" ]

[ "FIG5 is a schematic block diagram of a network device according to an embodiment of the present disclosure ", "FIG6 is a schematic block diagram of a terminal device according to another embodiment of the present disclosure ", "FIG7 is a schematic block diagram of a network device according to another embodiment of the present disclosure " ]

[ "As shown in FIG5, a network device 400 according to an embodiment of the present disclosure includes a receiving unit 410 and a determination unit 420. According to an exemplary embodiment, the network device may further include a sending unit 430. ", "FIG6 shows a terminal device according to another embodiment of the present disclosure. As shown in FIG6, the terminal device 100 comprises a processor 110 and a transceiver 120, wherein the processor 110 is connected to the transceiver 120. According to exemplary embodiments, the network device 100 further comprises a memory 130, wherein the memory 130 is connected to the processor 110. The processor 110, the memory 130, and the transceiver 120 can communicate with each other through an internal connection path. The processor 110 is configured to determine a Buffer Status Report BSR, wherein the BSR indicates that data to be transmitted of the terminal device comprise target-type data, wherein the target-type data are data need to be transmitted preferentially; the transceiver 120 is configured to transmit the BSR to a network device, wherein the network device configures a transmitting resource preferentially for the terminal device based on the BSR. ", "FIG7 shows a schematic block diagram of a network device according to another embodiment of the present disclosure. As shown in FIG7, the network device 200 comprises a processor 210 and a transceiver 220, wherein the processor 210 is connected to the transceiver 220. According to exemplary embodiments, the terminal device 200 further comprises a memory 230, wherein the memory 230 is connected to the processor 210. The processor 210, the memory 230, and the transceiver 220 can communicate with each other through an internal connection path. The transceiver 220 is configured to receive a buffer status report BSR sent by a terminal device, wherein the BSR indicates that data to be transmitted of the terminal device comprise target-type data; the processor 210 is configured to configure a transmitting resource preferentially for the terminal device based on the BSR." ]

[ { "element_identifier": "210", "terms": [ "processor" ] }, { "element_identifier": "230", "terms": [ "memory" ] }, { "element_identifier": "22", "terms": [ "processing module" ] }, { "element_identifier": "130", "terms": [ "memory" ] }, { "element_identifier": "100", "terms": [ "method" ] }, { "element_identifier": "220", "terms": [ "transceiver" ] }, { "element_identifier": "20", "terms": [ "network device" ] }, { "element_identifier": "21", "terms": [ "transceiver module" ] }, { "element_identifier": "110", "terms": [ "processor" ] }, { "element_identifier": "200", "terms": [ "method" ] }, { "element_identifier": "120", "terms": [ "transceiver" ] } ]

[ "20", "21", "22", "100", "110", "120", "130", "200", "210", "220", "230", "7", "14" ]

[ "FIG2" ]

[ "FIG2 is a schematic diagram of a buffer status report according to an embodiment of the present disclosure" ]

[ "According to exemplary embodiments, if the network device carries a Critical BSR in a Medium Access Control Protocol Data Unit MAC PDU transmitted to the terminal device, the MAC Service Data Unit (SDU) in the MAC PDU carries related information of target-type data. FIG2 is a schematic diagram of a BSR according to the embodiments of the present disclosure. As shown in FIG2, the BSR of the embodiments of the present disclosure comprises a Logical Channel Group (LCG) Identify (ID) domain and a Buffer Size domain, wherein the LCG ID domain indicates a LCG corresponding to a BSR, wherein the Buffer Size domain comprises related information of target-type data." ]

[ { "element_identifier": "12", "terms": [ "transceiver module" ] }, { "element_identifier": "11", "terms": [ "module" ] }, { "element_identifier": "100", "terms": [ "method" ] }, { "element_identifier": "10", "terms": [ "terminal device" ] }, { "element_identifier": "200", "terms": [ "method" ] } ]

[ "100", "2", "200", "10", "11", "12", "4", "13" ]

[ "FIG5" ]

[ "FIG5 is a schematic flowchart of an information monitoring method according to another embodiment of this application" ]

[ "Specifically, as shown in FIG5, that a slot corresponding to the first bandwidth part includes seven OFDM symbols and a slot corresponding to the second bandwidth part includes 14 OFDM symbols is used as an example for description. In this way, an absolute time length of the slot corresponding to the first bandwidth part is 7.5⁢KSCS1, an absolute time length of each corresponding symbol is 7.5⁢K7⋅SCS1=15⁢K14⋅SCS1, and an absolute time length of the slot corresponding to the second bandwidth part is 15⁢K⋅M214⋅SCS2. The terminal starts to perform switching from the m1th symbol within a current slot of the first bandwidth part. In this case, within the radio frequency switching duration of the terminal, an absolute time length of other slots than the current slot of the first bandwidth part is Tre−M1−m1⋅15⁢K14⋅SCS1+.Afunctionx+=max0x is used. In this way, a quantity of slots that are within the second bandwidth part and that correspond to the absolute time length of the other slots is ⌈Tre−M1−m1⋅15⁢K14⋅SCS1+⋅14⋅SCS215⁢K⋅M2⌉. Therefore, the terminal needs to monitor information corresponding to the second bandwidth part starting from the ⌈Tre−M1−m1⋅15⁢K14⋅SCS1+⋅14⋅SCS215⁢K⋅M2⌉+1th slot after the current slot." ]

[ { "element_identifier": "201710314141", "terms": [ "Chinese Patent Application No." ] }, { "element_identifier": "5", "terms": [ "May" ] }, { "element_identifier": "10", "terms": [ "terminal" ] }, { "element_identifier": "1", "terms": [ "foregoing formula" ] }, { "element_identifier": "2", "terms": [ "like.", "formula" ] }, { "element_identifier": "3", "terms": [ "centralized manner." ] }, { "element_identifier": "20", "terms": [ "network device" ] }, { "element_identifier": "15", "terms": [ "subcarrier spacing" ] }, { "element_identifier": "60", "terms": [ "subcarrier spacing" ] }, { "element_identifier": "14", "terms": [ "second bandwidth part includes" ] }, { "element_identifier": "7", "terms": [ "is" ] }, { "element_identifier": "600", "terms": [ "network device" ] }, { "element_identifier": "610", "terms": [ "processing module" ] }, { "element_identifier": "620", "terms": [ "sending module" ] }, { "element_identifier": "700", "terms": [ "network device" ] }, { "element_identifier": "710", "terms": [ "transceiver" ] }, { "element_identifier": "720", "terms": [ "processor" ] }, { "element_identifier": "730", "terms": [ "memory" ] }, { "element_identifier": "800", "terms": [ "terminal" ] }, { "element_identifier": "810", "terms": [ "sending module" ] }, { "element_identifier": "820", "terms": [ "receiving module" ] }, { "element_identifier": "830", "terms": [ "processing module" ] }, { "element_identifier": "900", "terms": [ "terminal" ] }, { "element_identifier": "910", "terms": [ "transceiver" ] }, { "element_identifier": "920", "terms": [ "processor" ] }, { "element_identifier": "930", "terms": [ "memory" ] }, { "element_identifier": "1000", "terms": [ "system" ] } ]

[ "4", "5", "24" ]

[ "FIG7" ]

[ "FIG7 is a schematic structural diagram of a network device according to an embodiment of this application" ]

[ "The sending module 620 in this embodiment of this application may be implemented by a transceiver, and the processing module 610 may be implemented by a processor. As shown in FIG7, a network device 700 may include a transceiver 710, a processor 720, and a memory 730. The memory 730 may be configured to store indication information, and may further be configured to store code, instructions, and the like to be executed by the processor 720." ]

[ { "element_identifier": "620", "terms": [ "sending module" ] }, { "element_identifier": "7", "terms": [ "is" ] }, { "element_identifier": "710", "terms": [ "transceiver" ] }, { "element_identifier": "600", "terms": [ "network device" ] }, { "element_identifier": "720", "terms": [ "processor" ] }, { "element_identifier": "610", "terms": [ "processing module" ] }, { "element_identifier": "730", "terms": [ "memory" ] }, { "element_identifier": "700", "terms": [ "network device" ] } ]

[ "600", "610", "620", "6", "700", "720", "710", "730", "7", "25" ]

[ "FIG9" ]

[ "FIG9 is a schematic structural diagram of a terminal according to an embodiment of this application" ]

[ "The sending module 810 and the receiving module 820 in this embodiment of this application may be implemented by a transceiver, and the processing module 830 may be implemented by a processor. As shown in FIG9, a terminal 900 may include a transceiver 910, a processor 920, and a memory 930. The memory 930 may be configured to store indication information, and may further be configured to store code, instructions, and the like to be executed by the processor 920." ]

[ { "element_identifier": "900", "terms": [ "terminal" ] }, { "element_identifier": "810", "terms": [ "sending module" ] }, { "element_identifier": "920", "terms": [ "processor" ] }, { "element_identifier": "820", "terms": [ "receiving module" ] }, { "element_identifier": "830", "terms": [ "processing module" ] }, { "element_identifier": "800", "terms": [ "terminal" ] }, { "element_identifier": "930", "terms": [ "memory" ] }, { "element_identifier": "910", "terms": [ "transceiver" ] } ]

[ "800", "810", "820", "830", "900", "920", "910", "930", "9", "26" ]

[ "FIG10" ]

[ "FIG10 is a schematic block diagram of a system according to an embodiment of this application " ]

[ "An embodiment of this application further provides a system 1000. As shown in FIG10, the system 1000 includes:the network device 700 according to the foregoing embodiment of this application and the terminal 900 according to the foregoing embodiment of this application." ]

[ { "element_identifier": "800", "terms": [ "terminal" ] }, { "element_identifier": "600", "terms": [ "network device" ] }, { "element_identifier": "10", "terms": [ "terminal" ] }, { "element_identifier": "1000", "terms": [ "system" ] } ]

[ "1000", "600", "800", "10", "27" ]

[ "FIG9" ]

[ "FIG9 is a schematic structural diagram of an embodiment of a MAC PDU" ]

[ "In this embodiment, downlink data is sent by using a MAC PDU. The following briefly describes a structure of the MAC PDU. Referring to FIG9, FIG9 is a schematic structural diagram of an embodiment of a MAC PDU.", "As shown in FIG9, the MAC PDU includes one MAC header (MAC header), a MAC payload (not shown in the figure), zero or at least one MAC data element (MAC data element), and zero or at least one MAC control element (MAC control element)." ]

[ { "element_identifier": "5", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "9", "terms": [ "time information.Embodiment" ] }, { "element_identifier": "4", "terms": [ "transmission start time", "MCS", "user equipment set.Embodiment" ] }, { "element_identifier": "20", "terms": [ "as", "user equipment.Embodiment" ] }, { "element_identifier": "0", "terms": [ "DLPN", "greater than" ] }, { "element_identifier": "61", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "10", "terms": [ "base station" ] }, { "element_identifier": "3", "terms": [ "OVSF code", "Msg" ] } ]

[ "20", "4", "3", "4", "10", "20", "4", "4", "4", "4", "5", "0", "0", "9", "61" ]

[ "FIG7" ]

[ "FIG7 is another scheduling process that is possibly used in a communications system" ]

[ "For the foregoing problem, another scheduling process that is possibly used in the communications system is shown in FIG7. Referring to FIG7, the scheduling process includes:", "In this way, in the scheduling process shown in FIG7, each time the UE is scheduled, the base station 10 needs to deliver DCI only once, and the UE needs to receive the DCI only once. However, actually, when sending the uplink information, the UE 11 needs to send only one bit of NEPN (Next PUD number, next PDU number). To schedule the one bit of NEPN, the base station 10 needs to send, for each UE, a total of 21 bits of downlink scheduling information including a channel frequency (6 bits), a transmission start time (4 bits), duration (6 bits), an MCS (4 bits), and an ULPN (1 bit), and signaling overheads are still relatively large." ]

[ { "element_identifier": "14", "terms": [ "April", "user equipment.Embodiment" ] }, { "element_identifier": "201610084148", "terms": [ "Chinese Patent Application No." ] }, { "element_identifier": "06", "terms": [ "February" ] }, { "element_identifier": "20", "terms": [ "as", "user equipment.Embodiment" ] }, { "element_identifier": "2", "terms": [ "modulo" ] }, { "element_identifier": "1", "terms": [ "Embodiment" ] }, { "element_identifier": "34", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "10", "terms": [ "base station" ] }, { "element_identifier": "11", "terms": [ "UE" ] }, { "element_identifier": "12", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "13", "terms": [ "embodiment" ] }, { "element_identifier": "0", "terms": [ "DLPN", "greater than" ] }, { "element_identifier": "6", "terms": [ "channel frequency", "uplink information is sent.Embodiment" ] }, { "element_identifier": "4", "terms": [ "transmission start time", "MCS", "user equipment set.Embodiment" ] }, { "element_identifier": "8", "terms": [ "is" ] }, { "element_identifier": "32", "terms": [ "may reach" ] }, { "element_identifier": "21", "terms": [ "uplink information sending apparatus" ] }, { "element_identifier": "210", "terms": [ "obtaining module" ] }, { "element_identifier": "211", "terms": [ "sending module" ] }, { "element_identifier": "22", "terms": [ "system scheduling apparatus" ] }, { "element_identifier": "220", "terms": [ "determining module" ] }, { "element_identifier": "221", "terms": [ "first sending module" ] }, { "element_identifier": "222", "terms": [ "second sending module" ] }, { "element_identifier": "23", "terms": [ "downlink information receiving apparatus" ] }, { "element_identifier": "230", "terms": [ "obtaining module" ] }, { "element_identifier": "231", "terms": [ "sending module" ] }, { "element_identifier": "232", "terms": [ "receiving module" ] }, { "element_identifier": "24", "terms": [ "downlink information sending apparatus" ] }, { "element_identifier": "240", "terms": [ "module" ] }, { "element_identifier": "241", "terms": [ "first sending module" ] }, { "element_identifier": "242", "terms": [ "second sending module" ] }, { "element_identifier": "251", "terms": [ "processor" ] }, { "element_identifier": "252", "terms": [ "memory" ] }, { "element_identifier": "253", "terms": [ "system bus" ] }, { "element_identifier": "3", "terms": [ "OVSF code", "Msg" ] }, { "element_identifier": "15", "terms": [ "single subcarrier is", "user equipment set.Embodiment" ] }, { "element_identifier": "010", "terms": [ "indication information is" ] }, { "element_identifier": "111", "terms": [ "indication information is" ] }, { "element_identifier": "3100", "terms": [ "uplink information sending apparatus" ] }, { "element_identifier": "3101", "terms": [ "obtaining module" ] }, { "element_identifier": "3102", "terms": [ "sending module" ] }, { "element_identifier": "3201", "terms": [ "determining module" ] }, { "element_identifier": "3202", "terms": [ "sending module" ] }, { "element_identifier": "3400", "terms": [ "uplink information sending apparatus" ] }, { "element_identifier": "3401", "terms": [ "receiving module" ] }, { "element_identifier": "3402", "terms": [ "obtaining module" ] }, { "element_identifier": "3403", "terms": [ "sending module" ] }, { "element_identifier": "5", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "7", "terms": [ "MAC payload.Embodiment" ] }, { "element_identifier": "9", "terms": [ "time information.Embodiment" ] }, { "element_identifier": "16", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "17", "terms": [ "uplink information is sent.Embodiment" ] }, { "element_identifier": "18", "terms": [ "MAC payload.Embodiment" ] }, { "element_identifier": "19", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "25", "terms": [ "uplink information sending apparatus.Embodiment" ] }, { "element_identifier": "26", "terms": [ "information sending apparatus set.Embodiment" ] }, { "element_identifier": "27", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "28", "terms": [ "uplink information is sent.Embodiment" ] }, { "element_identifier": "29", "terms": [ "MAC payload.Embodiment" ] }, { "element_identifier": "30", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "31", "terms": [ "time information.Embodiment" ] }, { "element_identifier": "33", "terms": [ "time information.Embodiment" ] }, { "element_identifier": "35", "terms": [ "embodiment" ] }, { "element_identifier": "36", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "37", "terms": [ "user equipment set.Embodiment" ] }, { "element_identifier": "38", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "39", "terms": [ "uplink information is sent.Embodiment" ] }, { "element_identifier": "40", "terms": [ "MAC payload.Embodiment" ] }, { "element_identifier": "41", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "42", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "43", "terms": [ "user equipment set.Embodiment" ] }, { "element_identifier": "44", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "45", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "46", "terms": [ "indication information.Embodiment" ] }, { "element_identifier": "47", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "48", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "49", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "50", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "51", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "52", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "53", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "54", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "55", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "56", "terms": [ "indication information.Embodiment" ] }, { "element_identifier": "57", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "58", "terms": [ "uplink information sending apparatus.Embodiment" ] }, { "element_identifier": "59", "terms": [ "uplink information sending apparatus.Embodiment" ] }, { "element_identifier": "60", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "61", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "62", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "63", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "64", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "65", "terms": [ "system information.Embodiment" ] }, { "element_identifier": "66", "terms": [ "random access channel PRACH.Embodiment" ] }, { "element_identifier": "67", "terms": [ "random access.Embodiment" ] }, { "element_identifier": "68", "terms": [ "random access channel PRACH.Embodiment" ] }, { "element_identifier": "69", "terms": [ "random access.Embodiment" ] }, { "element_identifier": "70", "terms": [ "coding scheme MCS.Embodiment" ] }, { "element_identifier": "71", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "72", "terms": [ "coding scheme MCS.Embodiment" ] }, { "element_identifier": "73", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "74", "terms": [ "coding scheme MCS.Embodiment" ] }, { "element_identifier": "75", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "76", "terms": [ "coding scheme MCS.Embodiment" ] } ]

[ "7", "62" ]

[ "FIG25" ]

[ "FIG25 is a schematic structural diagram of a device according to an embodiment of the present invention" ]

[ "Specifically, reference may be made to a schematic diagram of a device provided in FIG25 according to an embodiment of the present invention. The device includes a processor 251 and a memory 252. The processor 251 and the memory 252 are connected by using a system bus 253. The memory 252 stores driver software, which may specifically be wireless communications protocol software, such as global system for mobile communications (Global System for Mobile, GSM), Universal Mobile Telecommunications System (Universal Mobile Telecommunications System, UMTS), Worldwide Interoperability for Microwave Access (Worldwide Interoperability for Microwave Access, WiMAX), or Long Term Evolution (Long Term Evolution, LTE) protocol software. Driven by the memory 252, the processor 251 may implement a function of a wireless communications protocol to schedule, send, or receive wireless communication data, so as to execute an operation process in any one or multiple method embodiments, thereby reducing instruction overheads and deceasing power consumption during device execution." ]

[ { "element_identifier": "253", "terms": [ "system bus" ] }, { "element_identifier": "252", "terms": [ "memory" ] }, { "element_identifier": "25", "terms": [ "uplink information sending apparatus.Embodiment" ] }, { "element_identifier": "26", "terms": [ "information sending apparatus set.Embodiment" ] }, { "element_identifier": "251", "terms": [ "processor" ] }, { "element_identifier": "70", "terms": [ "coding scheme MCS.Embodiment" ] } ]

[ "252", "253", "251", "25", "26", "70" ]

[ "FIG9" ]

[ "FIG9 is a schematic structural diagram of an embodiment of a MAC PDU" ]

[ "In this embodiment, downlink data is sent by using a MAC PDU. The following briefly describes a structure of the MAC PDU. Referring to FIG9, FIG9 is a schematic structural diagram of an embodiment of a MAC PDU.", "As shown in FIG9, the MAC PDU includes one MAC header (MAC header), a MAC payload (not shown in the figure), zero or at least one MAC data element (MAC data element), and zero or at least one MAC control element (MAC control element)." ]

[ { "element_identifier": "5", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "9", "terms": [ "time information.Embodiment" ] }, { "element_identifier": "62", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "4", "terms": [ "transmission start time", "MCS", "user equipment set.Embodiment" ] }, { "element_identifier": "20", "terms": [ "as", "user equipment.Embodiment" ] }, { "element_identifier": "0", "terms": [ "DLPN", "greater than" ] }, { "element_identifier": "10", "terms": [ "base station" ] }, { "element_identifier": "3", "terms": [ "OVSF code", "Msg" ] } ]

[ "20", "4", "3", "4", "10", "20", "4", "4", "4", "4", "5", "0", "0", "9", "62" ]

[ "FIG7" ]

[ "FIG7 is another scheduling process that is possibly used in a communications system" ]

[ "For the foregoing problem, another scheduling process that is possibly used in the communications system is shown in FIG7. Referring to FIG7, the scheduling process includes:", "In this way, in the scheduling process shown in FIG7, each time the UE is scheduled, the base station 10 needs to deliver DCI only once, and the UE needs to receive the DCI only once. However, actually, when sending the uplink information, the UE 11 needs to send only one bit of NEPN (Next PUD number, next PDU number). To schedule the one bit of NEPN, the base station 10 needs to send, for each UE, a total of 21 bits of downlink scheduling information including a channel frequency (6 bits), a transmission start time (4 bits), duration (6 bits), an MCS (4 bits), and an ULPN (1 bit), and signaling overheads are still relatively large." ]

[ { "element_identifier": "14", "terms": [ "April", "user equipment.Embodiment" ] }, { "element_identifier": "201610084148", "terms": [ "Chinese Patent Application No." ] }, { "element_identifier": "06", "terms": [ "February" ] }, { "element_identifier": "20", "terms": [ "as", "user equipment.Embodiment" ] }, { "element_identifier": "2", "terms": [ "modulo" ] }, { "element_identifier": "1", "terms": [ "Embodiment" ] }, { "element_identifier": "34", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "10", "terms": [ "base station" ] }, { "element_identifier": "11", "terms": [ "UE" ] }, { "element_identifier": "12", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "13", "terms": [ "embodiment" ] }, { "element_identifier": "0", "terms": [ "DLPN", "greater than" ] }, { "element_identifier": "6", "terms": [ "channel frequency", "uplink information is sent.Embodiment" ] }, { "element_identifier": "4", "terms": [ "transmission start time", "MCS", "user equipment set.Embodiment" ] }, { "element_identifier": "8", "terms": [ "is" ] }, { "element_identifier": "32", "terms": [ "may reach" ] }, { "element_identifier": "21", "terms": [ "uplink information sending apparatus" ] }, { "element_identifier": "210", "terms": [ "obtaining module" ] }, { "element_identifier": "211", "terms": [ "sending module" ] }, { "element_identifier": "22", "terms": [ "system scheduling apparatus" ] }, { "element_identifier": "220", "terms": [ "determining module" ] }, { "element_identifier": "221", "terms": [ "first sending module" ] }, { "element_identifier": "222", "terms": [ "second sending module" ] }, { "element_identifier": "23", "terms": [ "downlink information receiving apparatus" ] }, { "element_identifier": "230", "terms": [ "obtaining module" ] }, { "element_identifier": "231", "terms": [ "sending module" ] }, { "element_identifier": "232", "terms": [ "receiving module" ] }, { "element_identifier": "24", "terms": [ "downlink information sending apparatus" ] }, { "element_identifier": "240", "terms": [ "module" ] }, { "element_identifier": "241", "terms": [ "first sending module" ] }, { "element_identifier": "242", "terms": [ "second sending module" ] }, { "element_identifier": "251", "terms": [ "processor" ] }, { "element_identifier": "252", "terms": [ "memory" ] }, { "element_identifier": "253", "terms": [ "system bus" ] }, { "element_identifier": "3", "terms": [ "OVSF code", "Msg" ] }, { "element_identifier": "15", "terms": [ "single subcarrier is", "user equipment set.Embodiment" ] }, { "element_identifier": "010", "terms": [ "indication information is" ] }, { "element_identifier": "111", "terms": [ "indication information is" ] }, { "element_identifier": "3100", "terms": [ "uplink information sending apparatus" ] }, { "element_identifier": "3101", "terms": [ "obtaining module" ] }, { "element_identifier": "3102", "terms": [ "sending module" ] }, { "element_identifier": "3201", "terms": [ "determining module" ] }, { "element_identifier": "3202", "terms": [ "sending module" ] }, { "element_identifier": "3400", "terms": [ "uplink information sending apparatus" ] }, { "element_identifier": "3401", "terms": [ "receiving module" ] }, { "element_identifier": "3402", "terms": [ "obtaining module" ] }, { "element_identifier": "3403", "terms": [ "sending module" ] }, { "element_identifier": "5", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "7", "terms": [ "MAC payload.Embodiment" ] }, { "element_identifier": "9", "terms": [ "time information.Embodiment" ] }, { "element_identifier": "16", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "17", "terms": [ "uplink information is sent.Embodiment" ] }, { "element_identifier": "18", "terms": [ "MAC payload.Embodiment" ] }, { "element_identifier": "19", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "25", "terms": [ "uplink information sending apparatus.Embodiment" ] }, { "element_identifier": "26", "terms": [ "information sending apparatus set.Embodiment" ] }, { "element_identifier": "27", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "28", "terms": [ "uplink information is sent.Embodiment" ] }, { "element_identifier": "29", "terms": [ "MAC payload.Embodiment" ] }, { "element_identifier": "30", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "31", "terms": [ "time information.Embodiment" ] }, { "element_identifier": "33", "terms": [ "time information.Embodiment" ] }, { "element_identifier": "35", "terms": [ "embodiment" ] }, { "element_identifier": "36", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "37", "terms": [ "user equipment set.Embodiment" ] }, { "element_identifier": "38", "terms": [ "DCI.Embodiment" ] }, { "element_identifier": "39", "terms": [ "uplink information is sent.Embodiment" ] }, { "element_identifier": "40", "terms": [ "MAC payload.Embodiment" ] }, { "element_identifier": "41", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "42", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "43", "terms": [ "user equipment set.Embodiment" ] }, { "element_identifier": "44", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "45", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "46", "terms": [ "indication information.Embodiment" ] }, { "element_identifier": "47", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "48", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "49", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "50", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "51", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "52", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "53", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "54", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "55", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "56", "terms": [ "indication information.Embodiment" ] }, { "element_identifier": "57", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "58", "terms": [ "uplink information sending apparatus.Embodiment" ] }, { "element_identifier": "59", "terms": [ "uplink information sending apparatus.Embodiment" ] }, { "element_identifier": "60", "terms": [ "embodiment", "embodiments" ] }, { "element_identifier": "61", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "62", "terms": [ "first uplink information.Embodiment" ] }, { "element_identifier": "63", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "64", "terms": [ "user equipment.Embodiment" ] }, { "element_identifier": "65", "terms": [ "system information.Embodiment" ] }, { "element_identifier": "66", "terms": [ "random access channel PRACH.Embodiment" ] }, { "element_identifier": "67", "terms": [ "random access.Embodiment" ] }, { "element_identifier": "68", "terms": [ "random access channel PRACH.Embodiment" ] }, { "element_identifier": "69", "terms": [ "random access.Embodiment" ] }, { "element_identifier": "70", "terms": [ "coding scheme MCS.Embodiment" ] }, { "element_identifier": "71", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "72", "terms": [ "coding scheme MCS.Embodiment" ] }, { "element_identifier": "73", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "74", "terms": [ "coding scheme MCS.Embodiment" ] }, { "element_identifier": "75", "terms": [ "uplink information.Embodiment" ] }, { "element_identifier": "76", "terms": [ "coding scheme MCS.Embodiment" ] } ]

[ "7", "63" ]

[ "FIG25" ]

[ "FIG25 is a schematic structural diagram of a device according to an embodiment of the present invention" ]

[ "Specifically, reference may be made to a schematic diagram of a device provided in FIG25 according to an embodiment of the present invention. The device includes a processor 251 and a memory 252. The processor 251 and the memory 252 are connected by using a system bus 253. The memory 252 stores driver software, which may specifically be wireless communications protocol software, such as global system for mobile communications (Global System for Mobile, GSM), Universal Mobile Telecommunications System (Universal Mobile Telecommunications System, UMTS), Worldwide Interoperability for Microwave Access (Worldwide Interoperability for Microwave Access, WiMAX), or Long Term Evolution (Long Term Evolution, LTE) protocol software. Driven by the memory 252, the processor 251 may implement a function of a wireless communications protocol to schedule, send, or receive wireless communication data, so as to execute an operation process in any one or multiple method embodiments, thereby reducing instruction overheads and deceasing power consumption during device execution." ]

[ { "element_identifier": "253", "terms": [ "system bus" ] }, { "element_identifier": "252", "terms": [ "memory" ] }, { "element_identifier": "25", "terms": [ "uplink information sending apparatus.Embodiment" ] }, { "element_identifier": "26", "terms": [ "information sending apparatus set.Embodiment" ] }, { "element_identifier": "251", "terms": [ "processor" ] }, { "element_identifier": "71", "terms": [ "uplink information.Embodiment" ] } ]

[ "252", "253", "251", "25", "26", "71" ]

[ "FIG3A", " FIG3B" ]

[ "FIG3A is a logic flow diagram of a method performed by a base station for transmitting a downlink transmission with transmission gaps according to one or more embodiments ", "FIG3B is a logic flow diagram of a method performed by a user equipment for receiving a downlink transmission with transmission gaps according to one or more embodiments" ]

[ "Also in view of the above variations and modifications, FIG3A generally illustrates a method according to some embodiments where the transmission 6 is a scheduled (downlink) transmission transmitted from a base station to a user equipment. This scheduled transmission may be for instance a narrowband physical downlink shared channel transmission, e.g., in a narrowband internet of things (NB-IoT) system. Regardless, the method in FIG3A is implemented by the base station configured for use in a wireless communication system. As shown, the method comprises transmitting to a user equipment one or more configuration messages that indicate a pattern of transmission gaps in time (Block 202). The one or more configuration messages (e.g., RRC messages) may for instance indicate a duration of each transmission gap and/or a periodicity if the transmission gaps. In any event, the method also comprises transmitting to the user equipment a scheduled transmission 6 that comprises a data block and one or more repetitions of the data block (Block 204). The scheduled transmission 6 is notably transmitted with transmission gaps therein according to the indicated pattern. ", "FIG3B illustrates a corresponding method implemented by the user equipment. As shown, the method comprises receiving from a base station one or more configuration messages that indicate a pattern of transmission gaps in time (Block 306). The one or more configuration messages (e.g., RRC messages) may for instance indicate a duration of each transmission gap and/or a periodicity if the transmission gaps. In any event, the method also comprises receiving from the base station a scheduled transmission 6 that comprises a data block and one or more repetitions of the data block (Block 204). The scheduled transmission 6 is notably received with transmission gaps therein according to the indicated pattern." ]

[ { "element_identifier": "11", "terms": [ "filed" ] }, { "element_identifier": "2016", "terms": [ "January" ] }, { "element_identifier": "180", "terms": [ "wireless communication system is" ] }, { "element_identifier": "2", "terms": [ "node", "nodes" ] }, { "element_identifier": "4", "terms": [ "receiving radio node", "user equipment" ] }, { "element_identifier": "6", "terms": [ "transmission" ] }, { "element_identifier": "8", "terms": [ "pattern" ] }, { "element_identifier": "10", "terms": [ "network node" ] }, { "element_identifier": "12", "terms": [ "devices", "device" ] }, { "element_identifier": "14", "terms": [ "uplink transmission" ] }, { "element_identifier": "22", "terms": [ "time blocks", "time block" ] }, { "element_identifier": "16", "terms": [ "repetitions" ] }, { "element_identifier": "18", "terms": [ "transmission gaps" ] }, { "element_identifier": "24", "terms": [ "bandwidth" ] }, { "element_identifier": "26", "terms": [ "stop transmission signal" ] }, { "element_identifier": "28", "terms": [ "communication" ] }, { "element_identifier": "400", "terms": [ "method" ] }, { "element_identifier": "402", "terms": [ "at block" ] }, { "element_identifier": "404", "terms": [ "at block" ] }, { "element_identifier": "500", "terms": [ "method" ] }, { "element_identifier": "502", "terms": [ "at block" ] }, { "element_identifier": "504", "terms": [ "at block" ] }, { "element_identifier": "600", "terms": [ "bits" ] }, { "element_identifier": "700", "terms": [ "divided into two groups" ] }, { "element_identifier": "1", "terms": [ "numbers", "embodiment" ] }, { "element_identifier": "702", "terms": [ "transmission gap subcarriers", "divided into two groups" ] }, { "element_identifier": "820", "terms": [ "processing circuits" ] }, { "element_identifier": "810", "terms": [ "radio circuits" ] }, { "element_identifier": "840", "terms": [ "antennas" ] }, { "element_identifier": "830", "terms": [ "instructions stored in memory" ] }, { "element_identifier": "850", "terms": [ "module" ] }, { "element_identifier": "860", "terms": [ "unit" ] }, { "element_identifier": "870", "terms": [ "unit" ] }, { "element_identifier": "920", "terms": [ "processing circuits" ] }, { "element_identifier": "910", "terms": [ "radio circuits" ] }, { "element_identifier": "940", "terms": [ "antennas" ] }, { "element_identifier": "930", "terms": [ "instructions stored in memory" ] }, { "element_identifier": "950", "terms": [ "receiving module/unit" ] }, { "element_identifier": "960", "terms": [ "unit" ] }, { "element_identifier": "970", "terms": [ "module" ] }, { "element_identifier": "1000", "terms": [ "UE" ] }, { "element_identifier": "1020", "terms": [ "processing circuits" ] }, { "element_identifier": "1010", "terms": [ "radio circuits" ] }, { "element_identifier": "1040", "terms": [ "antennas" ] }, { "element_identifier": "1030", "terms": [ "instructions stored in memory" ] }, { "element_identifier": "1120", "terms": [ "processing circuits" ] }, { "element_identifier": "1110", "terms": [ "radio circuits" ] }, { "element_identifier": "1140", "terms": [ "antennas" ] }, { "element_identifier": "1100", "terms": [ "base station" ] }, { "element_identifier": "1130", "terms": [ "instructions stored in memory" ] }, { "element_identifier": "15", "terms": [ "embodiment" ] }, { "element_identifier": "29", "terms": [ "embodiment" ] }, { "element_identifier": "31", "terms": [ "embodiment" ] }, { "element_identifier": "33", "terms": [ "embodiment" ] }, { "element_identifier": "208", "terms": [ "andreceiving" ] }, { "element_identifier": "35", "terms": [ "embodiment" ] }, { "element_identifier": "45", "terms": [ "embodiment" ] }, { "element_identifier": "204", "terms": [ "andtransmitting" ] }, { "element_identifier": "49", "terms": [ "embodiment" ] }, { "element_identifier": "59", "terms": [ "embodiment" ] }, { "element_identifier": "63", "terms": [ "embodiment" ] }, { "element_identifier": "65", "terms": [ "embodiment" ] }, { "element_identifier": "67", "terms": [ "embodiment" ] } ]

[ "202", "206", "22", "204", "208" ]

[ "FIG7" ]

[ "FIG7 is a logic flow diagram of a method implemented by a transmitting radio node according to one or more embodiments" ]

[ "FIG7 presents a diagram containing aspect of an example method 400 for transmitting a data block to a receiving radio node in a wireless communication system, which may be implemented by a transmitting radio node in example embodiments of the present disclosure. As introduced above, depending on the uplink or downlink nature of a transmitted data block repetition, this transmitting radio node may correspond to a wireless communication device (e.g., a UE) or a radio network node 10 (e.g., an eNB). As shown in FIG7, method 400 may include, at block 402, determining a transmission gap pattern that specifies a pattern of transmission gaps in time. In an additional aspect, method 400 may include, at block 404, transmitting, to a receiving radio node, repetitions of a data block over an entire system bandwidth and/or in a half-duplex manner, by transmitting the repetitions with transmission gaps therebetween according to the determined transmission gap pattern. Furthermore, although not shown in FIG7, method 400 may include further aspects, including but not limited to those disclosed in one or more of the enumerated embodiments below." ]

[ { "element_identifier": "402", "terms": [ "at block" ] }, { "element_identifier": "404", "terms": [ "at block" ] }, { "element_identifier": "400", "terms": [ "method" ] }, { "element_identifier": "26", "terms": [ "stop transmission signal" ] } ]

[ "400", "402", "404", "7", "26" ]

[ "FIG8" ]

[ "FIG8 is a logic flow diagram of a method implemented by a receiving radio node according to one or more embodiments" ]

[ "FIG8 presents a diagram containing aspect of an example method 500 for receiving a data block transmitted by a transmitting radio node in a wireless communication system, which may be implemented by a receiving radio node in example embodiments of the present disclosure. As introduced above, depending on the uplink or downlink nature of a transmitted data block repetition, this receiving radio node may correspond to a wireless communication device (e.g., a UE) or a radio network node 10 (e.g., an eNB). As shown in FIG8, method 500 may include, at block 502, determining a transmission gap pattern that specifies a pattern of transmission gaps in time. In an additional aspect, method 500 may include, at block 504, receiving, at the receiving radio node, repetitions of a data block transmitted by the transmitting radio node over an entire system bandwidth and/or in a half-duplex manner, by receiving the repetitions with transmission gaps therebetween according to the determined transmission gap pattern. Furthermore, although not shown in FIG8, method 500 may include further aspects, including but not limited to those disclosed in one or more of the enumerated embodiments below." ]

[ { "element_identifier": "8", "terms": [ "pattern" ] }, { "element_identifier": "500", "terms": [ "method" ] }, { "element_identifier": "502", "terms": [ "at block" ] }, { "element_identifier": "504", "terms": [ "at block" ] } ]

[ "500", "502", "504", "8", "27" ]

[ "FIG9" ]

[ "FIG9 is a diagram illustrating a set of bits defining a transmission gap pattern according to one or more embodiments" ]

[ "FIG9 is a diagram illustrating a set of bits defining a transmission gap pattern according to one or more embodiments of the present disclosure. In some embodiments, radio network node 10 may be configured to generate scheduling information including time and resource/frequency/subcarrier allocations for UL and DL signal transmissions to be performed by devices. Generating this scheduling information includes generating a transmission gap pattern to be utilized by these system devices. Once the scheduling information is generated (including the transmission gap pattern), the radio network node 10 may transmit the scheduling information, including the transmission gap pattern, to the wireless communication device. In some examples, this transmission may be a DCI or a dedicated RRC signal.", "In an example embodiment shown in FIG9, the scheduling information defining the transmission gap pattern may take the form of a set of bits 600, where each bit of the set of bits 600 corresponds to a set of time blocks 22. As shown in FIG9, each bit of the set of bits 600 has a value (zero or one) indicating whether a transmission gap is scheduled for the corresponding set of time blocks 22. In an aspect, a number of bits n in the set of bits 600 may be equal to the number of time blocks m in a particular transmission period, such that a ratio r of m to n equals one. This is the case in the embodiment illustrated in FIG9, where the set of bits contains 10 bits (n = m = 10 and m:n = 1) that correspond one-to-one to the ten time blocks 22 (namely, time blocks 22A-22J). As shown in FIG9, the radio network node 10 may set the value of a bit to zero to indicate that a repetition transmission of a data block is to be transmitted during the time block 22 corresponding to the bit and may set the value of the bit to one to indicate that that a transmission gap is scheduled for the corresponding time block 22." ]

[ { "element_identifier": "18", "terms": [ "transmission gaps" ] }, { "element_identifier": "16", "terms": [ "repetitions" ] }, { "element_identifier": "600", "terms": [ "bits" ] } ]

[ "600", "010100011", "0", "220", "16", "18", "9" ]

[ "FIG2" ]

[ "FIG2 is a drawing illustrating an example (1) of TDD configurations" ]

[ "FIG2 is a drawing illustrating an example (1) of TDD configurations. In LTE, TDD configurations illustrated in FIG2 are used. As illustrated in FIG2, seven (7) TDD configurations are defined. In cases where \"Downlink-to-Uplink Switch-point periodicity\" is \"5 ms\", special subframes, indicated by \"S\", that can be used for DL and UL, are present in both of two (2) 5 ms half frames included in a 10 ms radio frame. In cases where \"Downlink-to-Uplink Switch-point periodicity\" is \"10 ms\", the special subframe, indicated by \"S\", that can be used for DL and UL, is present only in the first half frame among the two (2) 5 ms half frames included in a 10 ms radio frame. \"D\" indicates a subframe used for DL, and \"U\" indicates a subframe used for UL." ]

[ { "element_identifier": "1", "terms": [ "Methods", "Method" ] }, { "element_identifier": "10", "terms": [ "greater than" ] }, { "element_identifier": "2", "terms": [ "example" ] }, { "element_identifier": "100", "terms": [ "base station apparatus", "base station apparatuses" ] }, { "element_identifier": "200", "terms": [ "user apparatus", "user apparatuses" ] }, { "element_identifier": "7", "terms": [ "seven" ] }, { "element_identifier": "0", "terms": [ "selecting from" ] }, { "element_identifier": "23", "terms": [ "using transmission power exceeding", "default value" ] }, { "element_identifier": "3", "terms": [ "method" ] }, { "element_identifier": "6", "terms": [ "frequency band less than", "period such as last", "RACH resource.Method" ] }, { "element_identifier": "26", "terms": [ "maximum", "HPUE is" ] }, { "element_identifier": "28", "terms": [ "HPUE is" ] }, { "element_identifier": "4", "terms": [ "method" ] }, { "element_identifier": "5", "terms": [ "RACH resource.Method", "April" ] }, { "element_identifier": "110", "terms": [ "transmission unit" ] }, { "element_identifier": "120", "terms": [ "reception unit" ] }, { "element_identifier": "130", "terms": [ "setting information management unit" ] }, { "element_identifier": "140", "terms": [ "resource setting unit" ] }, { "element_identifier": "210", "terms": [ "transmission unit" ] }, { "element_identifier": "220", "terms": [ "reception unit" ] }, { "element_identifier": "230", "terms": [ "setting information management unit" ] }, { "element_identifier": "240", "terms": [ "resource control unit" ] }, { "element_identifier": "1001", "terms": [ "processor", "processors" ] }, { "element_identifier": "1002", "terms": [ "storage apparatus" ] }, { "element_identifier": "1003", "terms": [ "auxiliary storage apparatus" ] }, { "element_identifier": "1004", "terms": [ "communication apparatus" ] }, { "element_identifier": "1005", "terms": [ "input apparatus" ] }, { "element_identifier": "1006", "terms": [ "output apparatus" ] }, { "element_identifier": "1007", "terms": [ "bus" ] }, { "element_identifier": "802", "terms": [ "IEEE" ] } ]

[ "5", "5", "5", "10", "10", "10", "5", "2", "3", "4", "5", "6", "7", "8", "9", "0", "2", "3", "4", "5", "6", "14" ]

[ "FIG3" ]

[ "FIG3 is a drawing illustrating an example (2) of TDD configurations" ]

[ "FIG3 is a drawing illustrating an example (2) of TDD configurations. In NR, more flexible DL and UL patterns can be configured compared to LTE. FIG3 illustrates an example of a case in which a TDD configuration is semi-statically configured.", "As illustrated in FIG3, periodicity of the TDD configurations can be configured by selecting from 0.5 ms, 0.625 ms, 1 ms, 1.25 ms, 2 ms, 2.5 ms, 5 ms, and 10 ms. Further, as illustrated in FIG3, it is possible to configure (set) a number of consecutive (continuous) DL slots (using slot as a unit) from the start of the TDD configuration period. It is possible to configure (set) a number of consecutive (continuous) DL symbols (using symbol as a unit) that are continuously provided after the consecutive DL slots. Further, as illustrated in FIG3, it is possible to configure (set) a number of consecutive (continuous) UL slots (using slot as a unit) from the end of the TDD configuration period. It is possible to configure (set) a number of consecutive (continuous) UL symbols (using symbol as a unit) that are continuously provided before the consecutive UL slots. There are flexible resources between the DL and the UL illustrated in FIG3. The flexible resources are resources dynamically used for DL or UL, which can be configured (set) by using symbol as a unit." ]

[ { "element_identifier": "1", "terms": [ "Methods", "Method" ] }, { "element_identifier": "10", "terms": [ "greater than" ] }, { "element_identifier": "2", "terms": [ "example" ] }, { "element_identifier": "100", "terms": [ "base station apparatus", "base station apparatuses" ] }, { "element_identifier": "200", "terms": [ "user apparatus", "user apparatuses" ] }, { "element_identifier": "7", "terms": [ "seven" ] }, { "element_identifier": "0", "terms": [ "selecting from" ] }, { "element_identifier": "23", "terms": [ "using transmission power exceeding", "default value" ] }, { "element_identifier": "3", "terms": [ "method" ] }, { "element_identifier": "6", "terms": [ "frequency band less than", "period such as last", "RACH resource.Method" ] }, { "element_identifier": "26", "terms": [ "maximum", "HPUE is" ] }, { "element_identifier": "28", "terms": [ "HPUE is" ] }, { "element_identifier": "4", "terms": [ "method" ] }, { "element_identifier": "5", "terms": [ "RACH resource.Method", "April" ] }, { "element_identifier": "110", "terms": [ "transmission unit" ] }, { "element_identifier": "120", "terms": [ "reception unit" ] }, { "element_identifier": "130", "terms": [ "setting information management unit" ] }, { "element_identifier": "140", "terms": [ "resource setting unit" ] }, { "element_identifier": "210", "terms": [ "transmission unit" ] }, { "element_identifier": "220", "terms": [ "reception unit" ] }, { "element_identifier": "230", "terms": [ "setting information management unit" ] }, { "element_identifier": "240", "terms": [ "resource control unit" ] }, { "element_identifier": "1001", "terms": [ "processor", "processors" ] }, { "element_identifier": "1002", "terms": [ "storage apparatus" ] }, { "element_identifier": "1003", "terms": [ "auxiliary storage apparatus" ] }, { "element_identifier": "1004", "terms": [ "communication apparatus" ] }, { "element_identifier": "1005", "terms": [ "input apparatus" ] }, { "element_identifier": "1006", "terms": [ "output apparatus" ] }, { "element_identifier": "1007", "terms": [ "bus" ] }, { "element_identifier": "802", "terms": [ "IEEE" ] } ]

[ "10", "15" ]

[ "FIG6" ]

[ "FIG6 is an example (1) of UL resource allocations in an embodiment of the present invention" ]

[ "FIG6 is an example (1) of UL resource allocations in an embodiment of the present invention. In the case where the user apparatus 200 is semi-statically configured with UL-DL config common as (including) a TDD configuration, the base station apparatus 100 may perform one of resource allocation methods 1-1, 1-2, 1-3, and 1-4 as shown below by using the UL-DL config common.", "Method (1-1): as illustrated in FIG6, allocation of UL resources may be equal to or less than 50% or X%.Method (1-2): as illustrated in FIG6, allocation of UL resources and flexible resources may be equal to or less than X%.Method (1-3): as illustrated in FIG6, allocation may be equal to or less than X% with respect to Y% of UL resources and flexible resources. A value of Y may be the same throughout the UE power classes, or may be different for each of the UE power classes.Method (1-4): the above-described method (1-1), method (1-2), and method (1-3) may be applied to each of the up to two configurable semi-static UL-DL periods, or may be applied to a period equal to a sum of the two UL-DL periods." ]

[ { "element_identifier": "1", "terms": [ "Methods", "Method" ] }, { "element_identifier": "10", "terms": [ "greater than" ] }, { "element_identifier": "2", "terms": [ "example" ] }, { "element_identifier": "100", "terms": [ "base station apparatus", "base station apparatuses" ] }, { "element_identifier": "200", "terms": [ "user apparatus", "user apparatuses" ] }, { "element_identifier": "7", "terms": [ "seven" ] }, { "element_identifier": "0", "terms": [ "selecting from" ] }, { "element_identifier": "23", "terms": [ "using transmission power exceeding", "default value" ] }, { "element_identifier": "3", "terms": [ "method" ] }, { "element_identifier": "6", "terms": [ "frequency band less than", "period such as last", "RACH resource.Method" ] }, { "element_identifier": "26", "terms": [ "maximum", "HPUE is" ] }, { "element_identifier": "28", "terms": [ "HPUE is" ] }, { "element_identifier": "4", "terms": [ "method" ] }, { "element_identifier": "5", "terms": [ "RACH resource.Method", "April" ] }, { "element_identifier": "110", "terms": [ "transmission unit" ] }, { "element_identifier": "120", "terms": [ "reception unit" ] }, { "element_identifier": "130", "terms": [ "setting information management unit" ] }, { "element_identifier": "140", "terms": [ "resource setting unit" ] }, { "element_identifier": "210", "terms": [ "transmission unit" ] }, { "element_identifier": "220", "terms": [ "reception unit" ] }, { "element_identifier": "230", "terms": [ "setting information management unit" ] }, { "element_identifier": "240", "terms": [ "resource control unit" ] }, { "element_identifier": "1001", "terms": [ "processor", "processors" ] }, { "element_identifier": "1002", "terms": [ "storage apparatus" ] }, { "element_identifier": "1003", "terms": [ "auxiliary storage apparatus" ] }, { "element_identifier": "1004", "terms": [ "communication apparatus" ] }, { "element_identifier": "1005", "terms": [ "input apparatus" ] }, { "element_identifier": "1006", "terms": [ "output apparatus" ] }, { "element_identifier": "1007", "terms": [ "bus" ] }, { "element_identifier": "802", "terms": [ "IEEE" ] } ]

[ "10", "18" ]

[ "FIG7" ]

[ "FIG7 is an example (2) of UL resource allocations in an embodiment of the present invention" ]

[ "FIG7 is an example (2) of UL resource allocations in an embodiment of the present invention. In the case where the user apparatus 200 is semi-statically configured with UL-DL config common as (including) a TDD configuration and where UL-DL configuration dedicated as (including) a TDD configuration for flexible resources is configured, the base station apparatus 100 may perform the following resource allocation methods 2-1, 2-2, 2-3, or 2-4, using the UL-DL config common and the UL-DL configuration dedicated.", "Method (2-1): as illustrated in FIG7, allocation of UL resources including UL resources configured in flexible resources may be equal to or less than 50% or X%.Method (2-2): allocation of UL resources and flexible resources illustrated in FIG7 may be equal to or less than 50% or X%.Method (2-3): allocation of UL resources including UL resources that are configured in Y% of flexible resources may be equal to or less than 50% or X%. A value of Y may be the same throughout the UE power classes, or may be different for each of the UE power classes.Method (2-4): the above-described method (2-1), method (2-2), and method (2-3) may be applied to each of the up to two configurable semi-static UL-DL periods, or may be applied to a period equal to a sum of the two UL-DL periods." ]

[ { "element_identifier": "1", "terms": [ "Methods", "Method" ] }, { "element_identifier": "10", "terms": [ "greater than" ] }, { "element_identifier": "2", "terms": [ "example" ] }, { "element_identifier": "100", "terms": [ "base station apparatus", "base station apparatuses" ] }, { "element_identifier": "200", "terms": [ "user apparatus", "user apparatuses" ] }, { "element_identifier": "7", "terms": [ "seven" ] }, { "element_identifier": "0", "terms": [ "selecting from" ] }, { "element_identifier": "23", "terms": [ "using transmission power exceeding", "default value" ] }, { "element_identifier": "3", "terms": [ "method" ] }, { "element_identifier": "6", "terms": [ "frequency band less than", "period such as last", "RACH resource.Method" ] }, { "element_identifier": "26", "terms": [ "maximum", "HPUE is" ] }, { "element_identifier": "28", "terms": [ "HPUE is" ] }, { "element_identifier": "4", "terms": [ "method" ] }, { "element_identifier": "5", "terms": [ "RACH resource.Method", "April" ] }, { "element_identifier": "110", "terms": [ "transmission unit" ] }, { "element_identifier": "120", "terms": [ "reception unit" ] }, { "element_identifier": "130", "terms": [ "setting information management unit" ] }, { "element_identifier": "140", "terms": [ "resource setting unit" ] }, { "element_identifier": "210", "terms": [ "transmission unit" ] }, { "element_identifier": "220", "terms": [ "reception unit" ] }, { "element_identifier": "230", "terms": [ "setting information management unit" ] }, { "element_identifier": "240", "terms": [ "resource control unit" ] }, { "element_identifier": "1001", "terms": [ "processor", "processors" ] }, { "element_identifier": "1002", "terms": [ "storage apparatus" ] }, { "element_identifier": "1003", "terms": [ "auxiliary storage apparatus" ] }, { "element_identifier": "1004", "terms": [ "communication apparatus" ] }, { "element_identifier": "1005", "terms": [ "input apparatus" ] }, { "element_identifier": "1006", "terms": [ "output apparatus" ] }, { "element_identifier": "1007", "terms": [ "bus" ] }, { "element_identifier": "802", "terms": [ "IEEE" ] } ]

[ "10" ]

[ "FIG9" ]

[ "FIG9 is a drawing illustrating an example of a functional structure of a user apparatus 200 according to an embodiment of the present invention" ]

[ "FIG9 is a drawing illustrating an example of a functional structure of a user apparatus 200. As illustrated in FIG9, the user apparatus 200 includes a transmission unit 210, a reception unit 220, a setting information management unit 230, and a resource control unit 240. The functional structure illustrated in FIG9 is merely an example. Functional divisions and names of functional units may be anything as long as operations can be performed according to an embodiment of the present invention." ]

[ { "element_identifier": "210", "terms": [ "transmission unit" ] }, { "element_identifier": "230", "terms": [ "setting information management unit" ] }, { "element_identifier": "130", "terms": [ "setting information management unit" ] }, { "element_identifier": "100", "terms": [ "base station apparatus", "base station apparatuses" ] }, { "element_identifier": "220", "terms": [ "reception unit" ] }, { "element_identifier": "240", "terms": [ "resource control unit" ] }, { "element_identifier": "140", "terms": [ "resource setting unit" ] }, { "element_identifier": "110", "terms": [ "transmission unit" ] }, { "element_identifier": "200", "terms": [ "user apparatus", "user apparatuses" ] }, { "element_identifier": "120", "terms": [ "reception unit" ] } ]

[ "100", "110", "130", "140", "120", "200", "210", "230", "240", "220", "20" ]

[ "FIG1" ]

[ "FIG1 is a drawing illustrating a configuration example of a wireless communication system according to an embodiment of the present invention" ]

[ "FIG1 is a drawing illustrating a configuration example of a wireless communication system according to an embodiment of the present invention. As illustrated in FIG1, the wireless communication system includes a base station apparatus 100 and a user apparatus 200. In FIG1, a single base station apparatus 100 and a single user apparatus 200 are illustrated as examples. There may be a plurality of the base station apparatuses 100 and a plurality of the user apparatuses 200.", "The base station apparatus 100 is a communication apparatus that provides one or more cells and performs wireless communications with the user apparatus 200. As illustrated in FIG1, the base station apparatus 100 transmits information related to TDD configurations to the user apparatus 200. The information related to TDD configurations is, for example, information indicating which subframes, which slots, or which symbols are used for DL, UL, or \"flexible\" in a radio frame. Further, the base station apparatus 100 transmits to the user apparatus 200 UL scheduling based on the configured TDD configurations.", "As illustrated in FIG1, the user apparatus 200 receives from the base station apparatus 100 the information related to TDD configurations and the UL scheduling, and performs UL transmission to the base station apparatus 100 by using UL resources. The user apparatus 200 transmits to the base station apparatus 100 information related to UL resources based on the used UL resources. The information related to UL resources includes, for example, information indicating that the UL resource usage rate exceeds a predetermined rate." ]

[ { "element_identifier": "100", "terms": [ "base station apparatus", "base station apparatuses" ] }, { "element_identifier": "200", "terms": [ "user apparatus", "user apparatuses" ] } ]

[ "100", "13", "200" ]

[ "FIG3" ]

[ "FIG3 shows an example wireless device and two base stations" ]

[ "FIG3 shows an example of base stations (base station 1, 120A, and base station 2, 120B) and a wireless device 110. The wireless device 110 may comprise a UE or any other wireless device. The base station (e.g., 120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other base station. A wireless device and/or a base station may perform one or more functions of a relay node. The base station 1, 120A, may comprise at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, and/or the like), at least one processor 321A, and at least one set of program code instructions 323A that may be stored in non-transitory memory 322A and executable by the at least one processor 321A. The base station 2, 120B, may comprise at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B that may be stored in non-transitory memory 322B and executable by the at least one processor 321B." ]

[ { "element_identifier": "310", "terms": [ "communication interface" ] }, { "element_identifier": "313", "terms": [ "touchpad" ] }, { "element_identifier": "1", "terms": [ "Msg" ] }, { "element_identifier": "2", "terms": [ "Type" ] }, { "element_identifier": "319", "terms": [ "peripherals" ] }, { "element_identifier": "314", "terms": [ "processor" ] }, { "element_identifier": "56", "terms": [ "subframe may have" ] }, { "element_identifier": "311", "terms": [ "microphone" ] }, { "element_identifier": "315", "terms": [ "stored in non-transitory memory" ] }, { "element_identifier": "318", "terms": [ "chipset" ] }, { "element_identifier": "316", "terms": [ "program code instructions" ] }, { "element_identifier": "110", "terms": [ "wireless device", "wireless devices" ] }, { "element_identifier": "317", "terms": [ "power source" ] }, { "element_identifier": "312", "terms": [ "keypad" ] } ]

[ "1", "2", "110", "310", "311", "317", "312", "314", "318", "56", "313", "319", "315", "316" ]

[ "FIG1" ]

[ "FIG1 shows an example radio access network (RAN) architecture" ]

[ "FIG1 shows an example Radio Access Network (RAN) architecture. A RAN node may comprise a next generation Node B (gNB) (e.g., 120A, 120B) providing New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g., 110A). A RAN node may comprise a base station such as a next generation evolved Node B (ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device (e.g., 110B). A first wireless device 110A may communicate with a base station, such as a gNB 120A, over a Uu interface. A second wireless device 110B may communicate with a base station, such as an ng-eNB 120D, over a Uu interface. The wireless devices 110A and/or 110B may be structurally similar to wireless devices shown in and/or described in connection with other drawing figures. The Node B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120D may be structurally similar to Nodes B and/or base stations shown in and/or described in connection with other drawing figures." ]

[ { "element_identifier": "9", "terms": [ "August", "licensed frequency band.Clause" ] }, { "element_identifier": "1", "terms": [ "Msg" ] }, { "element_identifier": "2", "terms": [ "Type" ] }, { "element_identifier": "110", "terms": [ "wireless device", "wireless devices" ] }, { "element_identifier": "310", "terms": [ "communication interface" ] }, { "element_identifier": "314", "terms": [ "processor" ] }, { "element_identifier": "316", "terms": [ "program code instructions" ] }, { "element_identifier": "315", "terms": [ "stored in non-transitory memory" ] }, { "element_identifier": "311", "terms": [ "microphone" ] }, { "element_identifier": "312", "terms": [ "keypad" ] }, { "element_identifier": "313", "terms": [ "touchpad" ] }, { "element_identifier": "317", "terms": [ "power source" ] }, { "element_identifier": "318", "terms": [ "chipset" ] }, { "element_identifier": "319", "terms": [ "peripherals" ] }, { "element_identifier": "506", "terms": [ "uplink DM-RS" ] }, { "element_identifier": "503", "terms": [ "PUSCH" ] }, { "element_identifier": "504", "terms": [ "PUCCH" ] }, { "element_identifier": "507", "terms": [ "uplink PT-RS" ] }, { "element_identifier": "508", "terms": [ "SRS" ] }, { "element_identifier": "0", "terms": [ "type", "received HARQ information is" ] }, { "element_identifier": "501", "terms": [ "UL-SCH" ] }, { "element_identifier": "502", "terms": [ "RACH" ] }, { "element_identifier": "505", "terms": [ "PRACH" ] }, { "element_identifier": "511", "terms": [ "DL-SCH" ] }, { "element_identifier": "512", "terms": [ "PCH" ] }, { "element_identifier": "513", "terms": [ "BCH" ] }, { "element_identifier": "509", "terms": [ "UCI" ] }, { "element_identifier": "517", "terms": [ "DCI" ] }, { "element_identifier": "515", "terms": [ "PDCCH" ] }, { "element_identifier": "522", "terms": [ "CSI-RS" ] }, { "element_identifier": "523", "terms": [ "downlink DM-RSs" ] }, { "element_identifier": "524", "terms": [ "PT-RS" ] }, { "element_identifier": "521", "terms": [ "PSS/SSS" ] }, { "element_identifier": "516", "terms": [ "PBCH" ] }, { "element_identifier": "32", "terms": [ "wireless device with", "supplementary uplink carrier.Clause" ] }, { "element_identifier": "514", "terms": [ "PDSCH" ] }, { "element_identifier": "12", "terms": [ "ADM-RS configuration may support", "slot may be", "may comprise", "unlicensed frequency band.Clause" ] }, { "element_identifier": "601", "terms": [ "organized into radio frames" ] }, { "element_identifier": "10", "terms": [ "frame duration may be", "second value.Clause" ] }, { "element_identifier": "602", "terms": [ "ten equally sized subframes" ] }, { "element_identifier": "603", "terms": [ "slots" ] }, { "element_identifier": "15", "terms": [ "subframe with", "carrier is", "second value.Clause" ] }, { "element_identifier": "604", "terms": [ "OFDM symbols" ] }, { "element_identifier": "14", "terms": [ "slot may be", "subframe may have", "supplementary uplink carrier.Clause" ] }, { "element_identifier": "700", "terms": [ "channel bandwidth" ] }, { "element_identifier": "701", "terms": [ "arrow" ] }, { "element_identifier": "702", "terms": [ "subcarrier spacing" ] }, { "element_identifier": "703", "terms": [ "subcarriers" ] }, { "element_identifier": "704", "terms": [ "guard bands" ] }, { "element_identifier": "705", "terms": [ "guard bands" ] }, { "element_identifier": "706", "terms": [ "subcarriers" ] }, { "element_identifier": "709", "terms": [ "first subcarrier spacing" ] }, { "element_identifier": "707", "terms": [ "subcarriers" ] }, { "element_identifier": "710", "terms": [ "second subcarrier spacing" ] }, { "element_identifier": "708", "terms": [ "subcarriers" ] }, { "element_identifier": "711", "terms": [ "third subcarrier spacing" ] }, { "element_identifier": "801", "terms": [ "transmission bandwidth" ] }, { "element_identifier": "802", "terms": [ "frequency domain" ] }, { "element_identifier": "803", "terms": [ "time domain" ] }, { "element_identifier": "805", "terms": [ "resource element" ] }, { "element_identifier": "807", "terms": [ "OFDM symbols" ] }, { "element_identifier": "28", "terms": [ "subframe may have", "reference signal.Clause" ] }, { "element_identifier": "30", "terms": [ "numerology is", "supplementary uplink carrier.Clause" ] }, { "element_identifier": "56", "terms": [ "subframe may have" ] }, { "element_identifier": "60", "terms": [ "numerology is" ] }, { "element_identifier": "806", "terms": [ "resource block" ] }, { "element_identifier": "940", "terms": [ "SS burst", "SS bursts" ] }, { "element_identifier": "950", "terms": [ "SS burst set" ] }, { "element_identifier": "120", "terms": [ "base station", "base stations" ] }, { "element_identifier": "910", "terms": [ "P1 procedure" ] }, { "element_identifier": "920", "terms": [ "P2 procedure" ] }, { "element_identifier": "930", "terms": [ "P3 procedure" ] }, { "element_identifier": "1010", "terms": [ "BWP1" ] }, { "element_identifier": "1050", "terms": [ "BWP1" ] }, { "element_identifier": "1020", "terms": [ "BWP2" ] }, { "element_identifier": "1040", "terms": [ "BWP2" ] }, { "element_identifier": "1030", "terms": [ "BWP3" ] }, { "element_identifier": "1130", "terms": [ "MN" ] }, { "element_identifier": "1150", "terms": [ "SN" ] }, { "element_identifier": "1110", "terms": [ "SDAP" ] }, { "element_identifier": "1111", "terms": [ "NR PDCP" ] }, { "element_identifier": "1114", "terms": [ "MN RLC" ] }, { "element_identifier": "1118", "terms": [ "MN MAC" ] }, { "element_identifier": "1112", "terms": [ "NR PDCP" ] }, { "element_identifier": "1115", "terms": [ "MN RLC" ] }, { "element_identifier": "1116", "terms": [ "SN RLC" ] }, { "element_identifier": "1119", "terms": [ "MAC" ] }, { "element_identifier": "1113", "terms": [ "NR PDCP" ] }, { "element_identifier": "1117", "terms": [ "SN RLC" ] }, { "element_identifier": "1120", "terms": [ "SDAP" ] }, { "element_identifier": "1140", "terms": [ "SDAP" ] }, { "element_identifier": "1121", "terms": [ "NR PDCP" ] }, { "element_identifier": "1142", "terms": [ "NR PDCP" ] }, { "element_identifier": "1124", "terms": [ "MN RLC" ] }, { "element_identifier": "1125", "terms": [ "MN RLC" ] }, { "element_identifier": "1128", "terms": [ "MN MAC" ] }, { "element_identifier": "1122", "terms": [ "NR PDCP" ] }, { "element_identifier": "1143", "terms": [ "NR PDCP" ] }, { "element_identifier": "1146", "terms": [ "SN RLC" ] }, { "element_identifier": "1147", "terms": [ "SN RLC" ] }, { "element_identifier": "1148", "terms": [ "SN MAC" ] }, { "element_identifier": "1123", "terms": [ "NR PDCP" ] }, { "element_identifier": "1141", "terms": [ "NR PDCP" ] }, { "element_identifier": "1126", "terms": [ "MN RLC" ] }, { "element_identifier": "1144", "terms": [ "SN RLC" ] }, { "element_identifier": "1145", "terms": [ "SN RLC" ] }, { "element_identifier": "1127", "terms": [ "MN RLC" ] }, { "element_identifier": "1230", "terms": [ "Msg2" ] }, { "element_identifier": "1240", "terms": [ "Msg3" ] }, { "element_identifier": "1250", "terms": [ "contention resolution" ] }, { "element_identifier": "3", "terms": [ "Msg" ] }, { "element_identifier": "1220", "terms": [ "Msg1" ] }, { "element_identifier": "1210", "terms": [ "RACH configuration" ] }, { "element_identifier": "1355", "terms": [ "Control" ] }, { "element_identifier": "1365", "terms": [ "Control" ] }, { "element_identifier": "1352", "terms": [ "Multiplexing" ] }, { "element_identifier": "1362", "terms": [ "Multiplexing" ] }, { "element_identifier": "1351", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1361", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1354", "terms": [ "Random Access Control" ] }, { "element_identifier": "1364", "terms": [ "Random Access Control" ] }, { "element_identifier": "1530", "terms": [ "RRC Connected" ] }, { "element_identifier": "1510", "terms": [ "RRC Idle" ] }, { "element_identifier": "1520", "terms": [ "RRC Inactive" ] }, { "element_identifier": "1540", "terms": [ "connection release" ] }, { "element_identifier": "1570", "terms": [ "connection inactivation" ] }, { "element_identifier": "1580", "terms": [ "connection resume" ] }, { "element_identifier": "1560", "terms": [ "connection release" ] }, { "element_identifier": "4", "terms": [ "Category", "NW configures" ] }, { "element_identifier": "25", "terms": [ "UL transmission exceeding" ] }, { "element_identifier": "16", "terms": [ "less than", "between", "second value.Clause" ] }, { "element_identifier": "31", "terms": [ "comprise four octets containing", "normal uplink carrier.Clause" ] }, { "element_identifier": "7", "terms": [ "particular value such as" ] }, { "element_identifier": "6", "terms": [ "carriers greater than", "supplementary uplink carrier.Clause" ] }, { "element_identifier": "2410", "terms": [ "NUL coverage" ] }, { "element_identifier": "2420", "terms": [ "SUL coverage" ] }, { "element_identifier": "2530", "terms": [ "distance" ] }, { "element_identifier": "2540", "terms": [ "measured RSRP" ] }, { "element_identifier": "2550", "terms": [ "first RSRP region" ] }, { "element_identifier": "2510", "terms": [ "NUL coverage" ] }, { "element_identifier": "2560", "terms": [ "second RSRP region" ] }, { "element_identifier": "2750", "terms": [ "contention resolution" ] }, { "element_identifier": "2650", "terms": [ "contention resolution" ] }, { "element_identifier": "2810", "terms": [ "NUL coverage" ] }, { "element_identifier": "2820", "terms": [ "SUL coverage" ] }, { "element_identifier": "2850", "terms": [ "other devices" ] }, { "element_identifier": "2860", "terms": [ "RSRP region" ] }, { "element_identifier": "2902", "terms": [ "At step" ] }, { "element_identifier": "2904", "terms": [ "carrier. At step" ] }, { "element_identifier": "2906", "terms": [ "cell. At step" ] }, { "element_identifier": "2908", "terms": [ "NUL carrier. At step" ] }, { "element_identifier": "2910", "terms": [ "at step" ] }, { "element_identifier": "2912", "terms": [ "step" ] }, { "element_identifier": "2914", "terms": [ "step" ] }, { "element_identifier": "3002", "terms": [ "At step" ] }, { "element_identifier": "3004", "terms": [ "step" ] }, { "element_identifier": "3006", "terms": [ "SUL. At step" ] }, { "element_identifier": "3008", "terms": [ "reference signals. At step" ] }, { "element_identifier": "3010", "terms": [ "at step" ] }, { "element_identifier": "3012", "terms": [ "at step" ] }, { "element_identifier": "5", "terms": [ "normal uplink carrier.Clause" ] }, { "element_identifier": "8", "terms": [ "unlicensed frequency band.Clause" ] }, { "element_identifier": "11", "terms": [ "normal uplink carrier.Clause" ] }, { "element_identifier": "13", "terms": [ "supplementary uplink carrier.Clause" ] }, { "element_identifier": "17", "terms": [ "cells.Clause" ] }, { "element_identifier": "18", "terms": [ "supplementary uplink carrier.Clause" ] }, { "element_identifier": "19", "terms": [ "random access procedure.Clause" ] }, { "element_identifier": "20", "terms": [ "second preamble.Clause" ] }, { "element_identifier": "21", "terms": [ "cell.Clause" ] }, { "element_identifier": "22", "terms": [ "resolution being unsuccessfully completed.Clause" ] }, { "element_identifier": "23", "terms": [ "supplementary carrier.Clause" ] }, { "element_identifier": "24", "terms": [ "normal uplink carrier.Clause" ] }, { "element_identifier": "26", "terms": [ "second value.Clause" ] }, { "element_identifier": "29", "terms": [ "clauses", "clause" ] }, { "element_identifier": "33", "terms": [ "licensed frequency band.Clause" ] }, { "element_identifier": "34", "terms": [ "first unlicensed frequency band.Clause" ] }, { "element_identifier": "35", "terms": [ "supplementary uplink carrier.Clause" ] }, { "element_identifier": "37", "terms": [ "received reference signal.Clause" ] }, { "element_identifier": "38", "terms": [ "signal strength threshold.Clause" ] }, { "element_identifier": "40", "terms": [ "cells.Clause" ] }, { "element_identifier": "42", "terms": [ "first computing device.Clause" ] }, { "element_identifier": "44", "terms": [ "supplementary uplink carrier.Clause" ] }, { "element_identifier": "43", "terms": [ "clauses", "clause" ] }, { "element_identifier": "46", "terms": [ "received reference signal.Clause" ] }, { "element_identifier": "47", "terms": [ "normal uplink carrier.Clause" ] }, { "element_identifier": "48", "terms": [ "unlicensed frequency band.Clause" ] }, { "element_identifier": "49", "terms": [ "random access procedure.Clause" ] }, { "element_identifier": "50", "terms": [ "unlicensed frequency band.Clause" ] }, { "element_identifier": "51", "terms": [ "signal strength threshold.Clause" ] }, { "element_identifier": "53", "terms": [ "supplementary uplink carrier.Clause" ] }, { "element_identifier": "54", "terms": [ "supplementary uplink carrier.Clause" ] }, { "element_identifier": "55", "terms": [ "normal uplink carrier.Clause" ] }, { "element_identifier": "57", "terms": [ "reference signal.Clause" ] }, { "element_identifier": "3400", "terms": [ "computing device" ] }, { "element_identifier": "3401", "terms": [ "processor", "processors" ] }, { "element_identifier": "3404", "terms": [ "removable media" ] }, { "element_identifier": "3405", "terms": [ "hard drive" ] }, { "element_identifier": "3402", "terms": [ "ROM storage" ] }, { "element_identifier": "3403", "terms": [ "RAM" ] }, { "element_identifier": "3407", "terms": [ "output device controllers" ] }, { "element_identifier": "3409", "terms": [ "network interface" ] }, { "element_identifier": "3411", "terms": [ "GPS", "microprocessor" ] }, { "element_identifier": "3412", "terms": [ "Bluetooth interface" ] }, { "element_identifier": "3413", "terms": [ "Wi-Fi interface" ] }, { "element_identifier": "3406", "terms": [ "display" ] }, { "element_identifier": "3408", "terms": [ "user input devices" ] }, { "element_identifier": "3410", "terms": [ "network" ] } ]

[ "54", "1" ]

[ "FIG11" ]

[ "FIG11 illustrates an example of a resource zone and a contention zone according to an embodiment of the present specification" ]

[ "FIG11 illustrates an example of a resource zone and a contention zone according to an embodiment of the present specification.", "C_SF denotes the number of contention zones existing in the time domain within one resource zone. In FIG11, C_SF=8.", "C_RB denotes the number of contention zones existing in the time domain within one resource zone. In FIG11, C_RB=4." ]

[ { "element_identifier": "32", "terms": [ "there may be" ] }, { "element_identifier": "802", "terms": [ "IEEE" ] }, { "element_identifier": "10", "terms": [ "UE" ] }, { "element_identifier": "20", "terms": [ "BSs" ] }, { "element_identifier": "30", "terms": [ "EPC" ] }, { "element_identifier": "1", "terms": [ "PRB" ] }, { "element_identifier": "2", "terms": [ "contention zone", "section" ] }, { "element_identifier": "3", "terms": [ "in section" ] }, { "element_identifier": "4", "terms": [ "Equation", "Contention zone" ] }, { "element_identifier": "36", "terms": [ "3GPP TS" ] }, { "element_identifier": "5", "terms": [ "Equation" ] }, { "element_identifier": "6", "terms": [ "Equation" ] }, { "element_identifier": "7", "terms": [ "Equation" ] }, { "element_identifier": "8", "terms": [ "following Equation" ] }, { "element_identifier": "9", "terms": [ "Equation" ] }, { "element_identifier": "0", "terms": [ "configuration field includes", "four MCS levels from" ] }, { "element_identifier": "1910", "terms": [ "processor" ] }, { "element_identifier": "1920", "terms": [ "memory" ] }, { "element_identifier": "1930", "terms": [ "transceiver" ] }, { "element_identifier": "2010", "terms": [ "data processing unit" ] }, { "element_identifier": "2020", "terms": [ "encoder", "encoders" ] }, { "element_identifier": "2030", "terms": [ "interleaver", "interleavers" ] }, { "element_identifier": "2040", "terms": [ "constellation mapper" ] }, { "element_identifier": "2050", "terms": [ "spatial stream encoder" ] }, { "element_identifier": "2060", "terms": [ "IDFT" ] }, { "element_identifier": "2070", "terms": [ "inserter" ] } ]

[ "11", "31" ]

[ "FIG12" ]

[ "FIG12 illustrates an example in which a contention zone is indicated by a configuration field according to an embodiment of the present specification" ]

[ "FIG12 illustrates an example in which a contention zone is indicated by a configuration field according to an embodiment of the present specification.", "Referring to FIG12, the configuration field=[0, 1, 1, 0]. That is, a density level of 0 indicates that one contention zone exists in one resource zone, a time offset of 1 indicates that the contention zone is located in a subframe 1∗N/C_SF+1, and a frequency offset of 1 indicates that the contention zone is located in PRB 1∗M/C_RB+1." ]

[ { "element_identifier": "32", "terms": [ "there may be" ] }, { "element_identifier": "802", "terms": [ "IEEE" ] }, { "element_identifier": "10", "terms": [ "UE" ] }, { "element_identifier": "20", "terms": [ "BSs" ] }, { "element_identifier": "30", "terms": [ "EPC" ] }, { "element_identifier": "1", "terms": [ "PRB" ] }, { "element_identifier": "2", "terms": [ "contention zone", "section" ] }, { "element_identifier": "3", "terms": [ "in section" ] }, { "element_identifier": "4", "terms": [ "Equation", "Contention zone" ] }, { "element_identifier": "36", "terms": [ "3GPP TS" ] }, { "element_identifier": "5", "terms": [ "Equation" ] }, { "element_identifier": "6", "terms": [ "Equation" ] }, { "element_identifier": "7", "terms": [ "Equation" ] }, { "element_identifier": "8", "terms": [ "following Equation" ] }, { "element_identifier": "9", "terms": [ "Equation" ] }, { "element_identifier": "0", "terms": [ "configuration field includes", "four MCS levels from" ] }, { "element_identifier": "1910", "terms": [ "processor" ] }, { "element_identifier": "1920", "terms": [ "memory" ] }, { "element_identifier": "1930", "terms": [ "transceiver" ] }, { "element_identifier": "2010", "terms": [ "data processing unit" ] }, { "element_identifier": "2020", "terms": [ "encoder", "encoders" ] }, { "element_identifier": "2030", "terms": [ "interleaver", "interleavers" ] }, { "element_identifier": "2040", "terms": [ "constellation mapper" ] }, { "element_identifier": "2050", "terms": [ "spatial stream encoder" ] }, { "element_identifier": "2060", "terms": [ "IDFT" ] }, { "element_identifier": "2070", "terms": [ "inserter" ] } ]

[ "12", "32" ]

[ "FIG13" ]

[ "FIG13 illustrates an example in which a contention zone is indicated by a configuration field according to another embodiment of the present specification" ]

[ "FIG13 illustrates an example in which a contention zone is indicated by a configuration field according to another embodiment of the present specification.", "Referring to FIG13, the configuration field=[1, 0, 0, 2]. That is, a density level of 1 indicates that two contention zones exist in one resource zone, where the period thereof is T/2. Contention zone 1 of the two contention zones has a time offset of 0, thus being located in subframe 1, and has a frequency offset of 0, thus being located in PRB 1. Contention zone 2 of the two contention zones has a time offset of 0, thus being located in subframe 1+T/2. Since contention zone 2 has a frequency offset of 0 and frequency hopping is 2 with respect to PRB 1, frequency hopping of 2∗M/C_RB is performed on contention zone 2. That is, it is analyzed that a PRB index of 2∗M/C_RB+1 is allocated through hopping a PRB having an index of 1 by 2∗M/C_RB." ]

[ { "element_identifier": "32", "terms": [ "there may be" ] }, { "element_identifier": "802", "terms": [ "IEEE" ] }, { "element_identifier": "10", "terms": [ "UE" ] }, { "element_identifier": "20", "terms": [ "BSs" ] }, { "element_identifier": "30", "terms": [ "EPC" ] }, { "element_identifier": "1", "terms": [ "PRB" ] }, { "element_identifier": "2", "terms": [ "contention zone", "section" ] }, { "element_identifier": "3", "terms": [ "in section" ] }, { "element_identifier": "4", "terms": [ "Equation", "Contention zone" ] }, { "element_identifier": "36", "terms": [ "3GPP TS" ] }, { "element_identifier": "5", "terms": [ "Equation" ] }, { "element_identifier": "6", "terms": [ "Equation" ] }, { "element_identifier": "7", "terms": [ "Equation" ] }, { "element_identifier": "8", "terms": [ "following Equation" ] }, { "element_identifier": "9", "terms": [ "Equation" ] }, { "element_identifier": "0", "terms": [ "configuration field includes", "four MCS levels from" ] }, { "element_identifier": "1910", "terms": [ "processor" ] }, { "element_identifier": "1920", "terms": [ "memory" ] }, { "element_identifier": "1930", "terms": [ "transceiver" ] }, { "element_identifier": "2010", "terms": [ "data processing unit" ] }, { "element_identifier": "2020", "terms": [ "encoder", "encoders" ] }, { "element_identifier": "2030", "terms": [ "interleaver", "interleavers" ] }, { "element_identifier": "2040", "terms": [ "constellation mapper" ] }, { "element_identifier": "2050", "terms": [ "spatial stream encoder" ] }, { "element_identifier": "2060", "terms": [ "IDFT" ] }, { "element_identifier": "2070", "terms": [ "inserter" ] } ]

[ "13", "33" ]

[ "FIG2" ]

[ "FIG2 is a schematic structural diagramschematic structural diagram of a gNB according to an embodiment of this application" ]

[ "The following describes a random access method provided in the embodiments of this application, only by using an example in which a terminal is UE and an access network device is a gNB. Specifically, FIG2 is a schematic structural diagram of a gNB according to an embodiment of this application. As shown in FIG2, the gNB may include at least one processor 21, a memory 22, a communications interface 23, and a communications bus 24. The following describes each component of the gNB in detail with reference to FIG2.", "In specific implementation, in an embodiment, the processor 21 may include one or more CPUs, for example, a CPU 0 and a CPU 1 in FIG2. In specific implementation, in an embodiment, the gNB may include a plurality of processors, for example, a processor 21 and a processor 25 shown in FIG2. Each of these processors may be a single-core processor (single-CPU), or may be a multi-core processor (multi-CPU). The processor herein may be one or more devices, circuits, and/or processing cores used to process data (such as a computer program instruction).", "The communications bus 24 may be an industry standard architecture (industry standard architecture, ISA) bus, a peripheral component interconnect (peripheral component, PCI) bus, an extended industry standard architecture (extended industry standard architecture, EISA) bus, or the like. The bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of denotation, the bus is denoted by using only one bold line in FIG2. However, this does not indicate that there is only one bus or only one type of bus.", "The gNB shown in FIG2 may perform an operation performed by the gNB in the random access method provided in the embodiments of this application. For example, the processor 21 in the gNB may configure, for the terminal, random access configurations corresponding to at least two uplink frequency bands.", "When the processing module 130 is a processor, the communications module 131 is a communications interface. When the storage module 132 is a memory, the server in this embodiment of the present invention may be the gNB shown in FIG2." ]

[ { "element_identifier": "24", "terms": [ "communications bus" ] }, { "element_identifier": "22", "terms": [ "memory" ] }, { "element_identifier": "2", "terms": [ "uplink frequency band" ] }, { "element_identifier": "25", "terms": [ "time may be" ] }, { "element_identifier": "0", "terms": [ "∗", "CPU" ] }, { "element_identifier": "21", "terms": [ "processor" ] }, { "element_identifier": "23", "terms": [ "communications interface" ] } ]

[ "21", "0", "25", "0", "22", "24", "23", "2", "26" ]

[ "FIG3" ]

[ "FIG3 is a schematic structural diagram of UE according to an embodiment of this application" ]

[ "FIG3 is a schematic structural diagram of UE according to an embodiment of this application. As shown in FIG3, the UE may include a processor 31, a memory 32, and a transceiver 33. The following describes each component of the UE in detail with reference to FIG3.", "In specific implementation, in an embodiment, the processor 31 may include one or more CPUs, for example, a CPU 0 and a CPU 1 in FIG3. In specific implementation, in an embodiment, the UE may include a plurality of processors, for example, a processor 31 and a processor 34 shown in FIG3. Each of these processors may be a single-CPU processor, or may be a multi-CPU processor. The processor herein may be one or more devices, circuits, and/or processing cores used to process data (such as a computer program instruction).", "A device structure shown in FIG3 does not constitute a limitation on the UE. A quantity of included components may be greater or less than that shown in the figure, or some components may be combined, or components may be disposed differently. Although not shown, the UE may further include a battery, a camera, a Bluetooth module, a global positioning system (Global Positioning System, GPS) module, and the like. Details are not described herein.", "The UE shown in FIG3 may perform an operation performed by the UE in the random access method provided in the embodiments of this application. For example, the transceiver 33 in the UE may obtain, from a gNB, random access configurations corresponding to at least two uplink frequency bands, and the processor 31 in the UE may initiate random access based on the random access configurations, corresponding to the at least two uplink frequency bands, obtained by the transceiver 33.", "When the processing module 101 is a processor, the communications module 102 is a communications interface. When the storage module 103 is a memory, the server in this embodiment of the present invention may be the UE shown in FIG3." ]

[ { "element_identifier": "201710459722", "terms": [ "Chinese Patent Application No." ] }, { "element_identifier": "16", "terms": [ "June" ] }, { "element_identifier": "1", "terms": [ "uplink frequency band" ] }, { "element_identifier": "2", "terms": [ "uplink frequency band" ] }, { "element_identifier": "3", "terms": [ "uplink frequency band" ] }, { "element_identifier": "25", "terms": [ "time may be" ] }, { "element_identifier": "0", "terms": [ "∗", "CPU" ] }, { "element_identifier": "14", "terms": [ "andFIG." ] }, { "element_identifier": "6", "terms": [ "frequency is less than" ] }, { "element_identifier": "21", "terms": [ "processor" ] }, { "element_identifier": "22", "terms": [ "memory" ] }, { "element_identifier": "23", "terms": [ "communications interface" ] }, { "element_identifier": "24", "terms": [ "communications bus" ] }, { "element_identifier": "31", "terms": [ "processor" ] }, { "element_identifier": "32", "terms": [ "memory" ] }, { "element_identifier": "33", "terms": [ "transceiver" ] }, { "element_identifier": "34", "terms": [ "processor", "communications bus" ] }, { "element_identifier": "403", "terms": [ "step" ] }, { "element_identifier": "1022", "terms": [ "message obtained in step" ] }, { "element_identifier": "48", "terms": [ "first" ] }, { "element_identifier": "401", "terms": [ "step" ] }, { "element_identifier": "402", "terms": [ "step" ] }, { "element_identifier": "503", "terms": [ "step" ] }, { "element_identifier": "604", "terms": [ "step" ] }, { "element_identifier": "703", "terms": [ "step" ] }, { "element_identifier": "805", "terms": [ "step" ] }, { "element_identifier": "804", "terms": [ "step" ] }, { "element_identifier": "810", "terms": [ "step" ] }, { "element_identifier": "811", "terms": [ "step" ] }, { "element_identifier": "91", "terms": [ "receiving unit" ] }, { "element_identifier": "92", "terms": [ "random access unit" ] }, { "element_identifier": "93", "terms": [ "recording unit" ] }, { "element_identifier": "94", "terms": [ "sending unit" ] }, { "element_identifier": "95", "terms": [ "determining unit" ] }, { "element_identifier": "96", "terms": [ "transmission unit" ] }, { "element_identifier": "97", "terms": [ "elimination unit" ] }, { "element_identifier": "4032", "terms": [ "step" ] }, { "element_identifier": "4033", "terms": [ "step" ] }, { "element_identifier": "4035", "terms": [ "step" ] }, { "element_identifier": "502", "terms": [ "step" ] }, { "element_identifier": "602", "terms": [ "step" ] }, { "element_identifier": "702", "terms": [ "step" ] }, { "element_identifier": "806", "terms": [ "step" ] }, { "element_identifier": "808", "terms": [ "step" ] }, { "element_identifier": "812", "terms": [ "step" ] }, { "element_identifier": "813", "terms": [ "step" ] }, { "element_identifier": "4031", "terms": [ "UE in performing step" ] }, { "element_identifier": "4034", "terms": [ "step" ] }, { "element_identifier": "4036", "terms": [ "UE in performing step" ] }, { "element_identifier": "801", "terms": [ "step" ] }, { "element_identifier": "803", "terms": [ "UE in performing step" ] }, { "element_identifier": "807", "terms": [ "step" ] }, { "element_identifier": "809", "terms": [ "step" ] }, { "element_identifier": "802", "terms": [ "UE in performing step" ] }, { "element_identifier": "101", "terms": [ "processing module" ] }, { "element_identifier": "102", "terms": [ "communications module" ] }, { "element_identifier": "103", "terms": [ "storage module" ] }, { "element_identifier": "110", "terms": [ "processor" ] }, { "element_identifier": "111", "terms": [ "memory" ] }, { "element_identifier": "120", "terms": [ "configuration unit" ] }, { "element_identifier": "121", "terms": [ "unit" ] }, { "element_identifier": "501", "terms": [ "step" ] }, { "element_identifier": "601", "terms": [ "step" ] }, { "element_identifier": "701", "terms": [ "step" ] }, { "element_identifier": "130", "terms": [ "processing module" ] }, { "element_identifier": "131", "terms": [ "communications module" ] }, { "element_identifier": "132", "terms": [ "storage module" ] }, { "element_identifier": "140", "terms": [ "processor" ] }, { "element_identifier": "141", "terms": [ "memory" ] } ]

[ "31", "34", "32", "33", "4", "27" ]

[ "FIG9" ]

[ "FIG9 is a schematic structural diagram of UE according to an embodiment of this application" ]

[ "When each function module is obtained through division based on each corresponding function, FIG9 is a possible schematic structural diagram of the UE in the foregoing embodiments. As shown in FIG9, the UE may include a receiving unit 91, a random access unit 92, a recording unit 93, a sending unit 94, a determining unit 95, a transmission unit 96, an elimination unit 97, and a time management unit 98." ]

[ { "element_identifier": "2", "terms": [ "uplink frequency band" ] } ]

[ "12", "12", "2", "9", "30" ]

[ "FIG3D" ]

[ "FIG3D is a flowchart of a contention-based random access method according to another embodiment of the present invention" ]

[ "In addition, after multiplying or convolving the modulated symbol and the PRACH sequence together correspondingly to obtain a multiplexing result, the UE may perform orthogonal code spreading for the multiplexing result, that is, multiply each multiplexing result by the orthogonal code directly. As shown in FIG3D, the procedure of this implementation manner includes steps 301b to 307b. Steps 301b to 307b are similar to steps 301 to 306, and are not detailed here any further." ]

[ { "element_identifier": "201210034106", "terms": [ "Patent Application No. CN" ] }, { "element_identifier": "15", "terms": [ "February" ] }, { "element_identifier": "200", "terms": [ "is generally less than" ] }, { "element_identifier": "11", "terms": [ "embodiment" ] }, { "element_identifier": "201", "terms": [ "step" ] }, { "element_identifier": "204", "terms": [ "step" ] }, { "element_identifier": "203", "terms": [ "step" ] }, { "element_identifier": "202", "terms": [ "descriptions about step" ] }, { "element_identifier": "102", "terms": [ "step" ] }, { "element_identifier": "303", "terms": [ "step" ] }, { "element_identifier": "2", "terms": [ "embodiment" ] }, { "element_identifier": "305", "terms": [ "step" ] }, { "element_identifier": "304", "terms": [ "orthogonal code spreading. Step" ] }, { "element_identifier": "306", "terms": [ "step" ] }, { "element_identifier": "301a", "terms": [ "steps" ] }, { "element_identifier": "301", "terms": [ "steps" ] }, { "element_identifier": "301b", "terms": [ "steps" ] }, { "element_identifier": "404", "terms": [ "step" ] }, { "element_identifier": "405", "terms": [ "step" ] }, { "element_identifier": "406", "terms": [ "step" ] }, { "element_identifier": "402", "terms": [ "steps" ] }, { "element_identifier": "839", "terms": [ "is" ] }, { "element_identifier": "139", "terms": [ "is" ] }, { "element_identifier": "603", "terms": [ "system bandwidth. In step" ] }, { "element_identifier": "602", "terms": [ "steps" ] }, { "element_identifier": "6", "terms": [ "then", "base station.Embodiment" ] }, { "element_identifier": "0", "terms": [ "PRACH sequence", "first information" ] }, { "element_identifier": "1", "terms": [ "embodiments", "embodiment" ] }, { "element_identifier": "63", "terms": [ "PRACH" ] }, { "element_identifier": "702", "terms": [ "steps" ] }, { "element_identifier": "91", "terms": [ "obtaining module" ] }, { "element_identifier": "92", "terms": [ "sending module" ] }, { "element_identifier": "98", "terms": [ "module" ] }, { "element_identifier": "93", "terms": [ "judging module" ] }, { "element_identifier": "94", "terms": [ "determining module" ] }, { "element_identifier": "95", "terms": [ "response receiving module" ] }, { "element_identifier": "96", "terms": [ "scheduling transmission module" ] }, { "element_identifier": "1101", "terms": [ "first receiving module" ] }, { "element_identifier": "1102", "terms": [ "second receiving module" ] }, { "element_identifier": "1103", "terms": [ "response sending module" ] }, { "element_identifier": "1104", "terms": [ "scheduling receiving module" ] }, { "element_identifier": "1105", "terms": [ "success message sending module" ] }, { "element_identifier": "3", "terms": [ "embodiment" ] }, { "element_identifier": "4", "terms": [ "PRACH sequence together correspondingly.Embodiment" ] }, { "element_identifier": "5", "terms": [ "embodiment" ] }, { "element_identifier": "7", "terms": [ "cell identifier.Embodiment" ] }, { "element_identifier": "8", "terms": [ "Turbo coding.Embodiment" ] }, { "element_identifier": "10", "terms": [ "second cyclic prefix.Embodiment" ] }, { "element_identifier": "12", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "13", "terms": [ "result onto discontinuous subcarriers.Embodiment" ] }, { "element_identifier": "14", "terms": [ "frequency hopping manner.Embodiment" ] }, { "element_identifier": "17", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "18", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "19", "terms": [ "frequency domain.Embodiment" ] }, { "element_identifier": "20", "terms": [ "same subframe.Embodiment" ] }, { "element_identifier": "21", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "22", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "24", "terms": [ "first information.Embodiment" ] }, { "element_identifier": "25", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "27", "terms": [ "broadcast message.Embodiment" ] }, { "element_identifier": "28", "terms": [ "control signaling.Embodiment" ] }, { "element_identifier": "29", "terms": [ "embodiment" ] }, { "element_identifier": "31", "terms": [ "UE.Embodiment" ] }, { "element_identifier": "32", "terms": [ "embodiments", "embodiment" ] }, { "element_identifier": "33", "terms": [ "embodiment" ] }, { "element_identifier": "34", "terms": [ "embodiment" ] }, { "element_identifier": "35", "terms": [ "PRACH sequence together correspondingly.Embodiment" ] }, { "element_identifier": "36", "terms": [ "embodiment" ] }, { "element_identifier": "38", "terms": [ "cell identifier.Embodiment" ] }, { "element_identifier": "39", "terms": [ "Turbo coding.Embodiment" ] }, { "element_identifier": "40", "terms": [ "IFFT transformation.Embodiment" ] }, { "element_identifier": "42", "terms": [ "second cyclic prefix.Embodiment" ] }, { "element_identifier": "43", "terms": [ "embodiment" ] }, { "element_identifier": "45", "terms": [ "result onto discontinuous subcarriers.Embodiment" ] }, { "element_identifier": "46", "terms": [ "frequency hopping manner.Embodiment" ] }, { "element_identifier": "49", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "50", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "51", "terms": [ "frequency domain.Embodiment" ] }, { "element_identifier": "52", "terms": [ "same subframe.Embodiment" ] }, { "element_identifier": "53", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "54", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "56", "terms": [ "first information.Embodiment" ] }, { "element_identifier": "57", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "58", "terms": [ "broadcast message.Embodiment" ] }, { "element_identifier": "59", "terms": [ "control signaling.Embodiment" ] }, { "element_identifier": "60", "terms": [ "embodiment" ] }, { "element_identifier": "62", "terms": [ "UE.Embodiment" ] } ]

[ "4", "4", "30" ]

[ "FIG5" ]

[ "FIG5 is a flowchart of a contention-based random access method according to another embodiment of the present invention" ]

[ "FIG5 is a flowchart of a contention-based random access method according to another embodiment of the present invention. This embodiment may be implemented based on the embodiments described above. As shown in FIG5, the method includes:" ]

[ { "element_identifier": "201210034106", "terms": [ "Patent Application No. CN" ] }, { "element_identifier": "15", "terms": [ "February" ] }, { "element_identifier": "200", "terms": [ "is generally less than" ] }, { "element_identifier": "11", "terms": [ "embodiment" ] }, { "element_identifier": "201", "terms": [ "step" ] }, { "element_identifier": "204", "terms": [ "step" ] }, { "element_identifier": "203", "terms": [ "step" ] }, { "element_identifier": "202", "terms": [ "descriptions about step" ] }, { "element_identifier": "102", "terms": [ "step" ] }, { "element_identifier": "303", "terms": [ "step" ] }, { "element_identifier": "2", "terms": [ "embodiment" ] }, { "element_identifier": "305", "terms": [ "step" ] }, { "element_identifier": "304", "terms": [ "orthogonal code spreading. Step" ] }, { "element_identifier": "306", "terms": [ "step" ] }, { "element_identifier": "301a", "terms": [ "steps" ] }, { "element_identifier": "301", "terms": [ "steps" ] }, { "element_identifier": "301b", "terms": [ "steps" ] }, { "element_identifier": "404", "terms": [ "step" ] }, { "element_identifier": "405", "terms": [ "step" ] }, { "element_identifier": "406", "terms": [ "step" ] }, { "element_identifier": "402", "terms": [ "steps" ] }, { "element_identifier": "839", "terms": [ "is" ] }, { "element_identifier": "139", "terms": [ "is" ] }, { "element_identifier": "603", "terms": [ "system bandwidth. In step" ] }, { "element_identifier": "602", "terms": [ "steps" ] }, { "element_identifier": "6", "terms": [ "then", "base station.Embodiment" ] }, { "element_identifier": "0", "terms": [ "PRACH sequence", "first information" ] }, { "element_identifier": "1", "terms": [ "embodiments", "embodiment" ] }, { "element_identifier": "63", "terms": [ "PRACH" ] }, { "element_identifier": "702", "terms": [ "steps" ] }, { "element_identifier": "91", "terms": [ "obtaining module" ] }, { "element_identifier": "92", "terms": [ "sending module" ] }, { "element_identifier": "98", "terms": [ "module" ] }, { "element_identifier": "93", "terms": [ "judging module" ] }, { "element_identifier": "94", "terms": [ "determining module" ] }, { "element_identifier": "95", "terms": [ "response receiving module" ] }, { "element_identifier": "96", "terms": [ "scheduling transmission module" ] }, { "element_identifier": "1101", "terms": [ "first receiving module" ] }, { "element_identifier": "1102", "terms": [ "second receiving module" ] }, { "element_identifier": "1103", "terms": [ "response sending module" ] }, { "element_identifier": "1104", "terms": [ "scheduling receiving module" ] }, { "element_identifier": "1105", "terms": [ "success message sending module" ] }, { "element_identifier": "3", "terms": [ "embodiment" ] }, { "element_identifier": "4", "terms": [ "PRACH sequence together correspondingly.Embodiment" ] }, { "element_identifier": "5", "terms": [ "embodiment" ] }, { "element_identifier": "7", "terms": [ "cell identifier.Embodiment" ] }, { "element_identifier": "8", "terms": [ "Turbo coding.Embodiment" ] }, { "element_identifier": "10", "terms": [ "second cyclic prefix.Embodiment" ] }, { "element_identifier": "12", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "13", "terms": [ "result onto discontinuous subcarriers.Embodiment" ] }, { "element_identifier": "14", "terms": [ "frequency hopping manner.Embodiment" ] }, { "element_identifier": "17", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "18", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "19", "terms": [ "frequency domain.Embodiment" ] }, { "element_identifier": "20", "terms": [ "same subframe.Embodiment" ] }, { "element_identifier": "21", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "22", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "24", "terms": [ "first information.Embodiment" ] }, { "element_identifier": "25", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "27", "terms": [ "broadcast message.Embodiment" ] }, { "element_identifier": "28", "terms": [ "control signaling.Embodiment" ] }, { "element_identifier": "29", "terms": [ "embodiment" ] }, { "element_identifier": "31", "terms": [ "UE.Embodiment" ] }, { "element_identifier": "32", "terms": [ "embodiments", "embodiment" ] }, { "element_identifier": "33", "terms": [ "embodiment" ] }, { "element_identifier": "34", "terms": [ "embodiment" ] }, { "element_identifier": "35", "terms": [ "PRACH sequence together correspondingly.Embodiment" ] }, { "element_identifier": "36", "terms": [ "embodiment" ] }, { "element_identifier": "38", "terms": [ "cell identifier.Embodiment" ] }, { "element_identifier": "39", "terms": [ "Turbo coding.Embodiment" ] }, { "element_identifier": "40", "terms": [ "IFFT transformation.Embodiment" ] }, { "element_identifier": "42", "terms": [ "second cyclic prefix.Embodiment" ] }, { "element_identifier": "43", "terms": [ "embodiment" ] }, { "element_identifier": "45", "terms": [ "result onto discontinuous subcarriers.Embodiment" ] }, { "element_identifier": "46", "terms": [ "frequency hopping manner.Embodiment" ] }, { "element_identifier": "49", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "50", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "51", "terms": [ "frequency domain.Embodiment" ] }, { "element_identifier": "52", "terms": [ "same subframe.Embodiment" ] }, { "element_identifier": "53", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "54", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "56", "terms": [ "first information.Embodiment" ] }, { "element_identifier": "57", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "58", "terms": [ "broadcast message.Embodiment" ] }, { "element_identifier": "59", "terms": [ "control signaling.Embodiment" ] }, { "element_identifier": "60", "terms": [ "embodiment" ] }, { "element_identifier": "62", "terms": [ "UE.Embodiment" ] } ]

[ "501", "502", "4", "503", "504", "505", "4", "506", "507", "4", "508", "4", "509", "5", "32" ]

[ "FIG6A" ]

[ "FIG6A is a flowchart of a contention-based random access method according to another embodiment of the present invention" ]

[ "FIG6A is a flowchart of a contention-based random access method according to another embodiment of the present invention. As shown in FIG6A, the method in this embodiment includes:Step 601: A UE obtains a PRACH sequence.", "Optionally, in the embodiment shown in FIG6A, before modulating the first information, the UE may perform channel coding, add a CRC check bit, perform scrambling, or the like for the first information, which improves transmission performance of the first information.", "Optionally, in the embodiment shown in FIG6A, after modulating the first information and obtaining the modulated symbol, the UE may perform orthogonal code spreading for the modulated symbol; or, after performing IFFT transformation for the resource mapping result, the UE may perform orthogonal code spreading for the IFFT transformation result to multiplex more users." ]

[ { "element_identifier": "201210034106", "terms": [ "Patent Application No. CN" ] }, { "element_identifier": "15", "terms": [ "February" ] }, { "element_identifier": "200", "terms": [ "is generally less than" ] }, { "element_identifier": "11", "terms": [ "embodiment" ] }, { "element_identifier": "201", "terms": [ "step" ] }, { "element_identifier": "204", "terms": [ "step" ] }, { "element_identifier": "203", "terms": [ "step" ] }, { "element_identifier": "202", "terms": [ "descriptions about step" ] }, { "element_identifier": "102", "terms": [ "step" ] }, { "element_identifier": "303", "terms": [ "step" ] }, { "element_identifier": "2", "terms": [ "embodiment" ] }, { "element_identifier": "305", "terms": [ "step" ] }, { "element_identifier": "304", "terms": [ "orthogonal code spreading. Step" ] }, { "element_identifier": "306", "terms": [ "step" ] }, { "element_identifier": "301a", "terms": [ "steps" ] }, { "element_identifier": "301", "terms": [ "steps" ] }, { "element_identifier": "301b", "terms": [ "steps" ] }, { "element_identifier": "404", "terms": [ "step" ] }, { "element_identifier": "405", "terms": [ "step" ] }, { "element_identifier": "406", "terms": [ "step" ] }, { "element_identifier": "402", "terms": [ "steps" ] }, { "element_identifier": "839", "terms": [ "is" ] }, { "element_identifier": "139", "terms": [ "is" ] }, { "element_identifier": "603", "terms": [ "system bandwidth. In step" ] }, { "element_identifier": "602", "terms": [ "steps" ] }, { "element_identifier": "6", "terms": [ "then", "base station.Embodiment" ] }, { "element_identifier": "0", "terms": [ "PRACH sequence", "first information" ] }, { "element_identifier": "1", "terms": [ "embodiments", "embodiment" ] }, { "element_identifier": "63", "terms": [ "PRACH" ] }, { "element_identifier": "702", "terms": [ "steps" ] }, { "element_identifier": "91", "terms": [ "obtaining module" ] }, { "element_identifier": "92", "terms": [ "sending module" ] }, { "element_identifier": "98", "terms": [ "module" ] }, { "element_identifier": "93", "terms": [ "judging module" ] }, { "element_identifier": "94", "terms": [ "determining module" ] }, { "element_identifier": "95", "terms": [ "response receiving module" ] }, { "element_identifier": "96", "terms": [ "scheduling transmission module" ] }, { "element_identifier": "1101", "terms": [ "first receiving module" ] }, { "element_identifier": "1102", "terms": [ "second receiving module" ] }, { "element_identifier": "1103", "terms": [ "response sending module" ] }, { "element_identifier": "1104", "terms": [ "scheduling receiving module" ] }, { "element_identifier": "1105", "terms": [ "success message sending module" ] }, { "element_identifier": "3", "terms": [ "embodiment" ] }, { "element_identifier": "4", "terms": [ "PRACH sequence together correspondingly.Embodiment" ] }, { "element_identifier": "5", "terms": [ "embodiment" ] }, { "element_identifier": "7", "terms": [ "cell identifier.Embodiment" ] }, { "element_identifier": "8", "terms": [ "Turbo coding.Embodiment" ] }, { "element_identifier": "10", "terms": [ "second cyclic prefix.Embodiment" ] }, { "element_identifier": "12", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "13", "terms": [ "result onto discontinuous subcarriers.Embodiment" ] }, { "element_identifier": "14", "terms": [ "frequency hopping manner.Embodiment" ] }, { "element_identifier": "17", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "18", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "19", "terms": [ "frequency domain.Embodiment" ] }, { "element_identifier": "20", "terms": [ "same subframe.Embodiment" ] }, { "element_identifier": "21", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "22", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "24", "terms": [ "first information.Embodiment" ] }, { "element_identifier": "25", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "27", "terms": [ "broadcast message.Embodiment" ] }, { "element_identifier": "28", "terms": [ "control signaling.Embodiment" ] }, { "element_identifier": "29", "terms": [ "embodiment" ] }, { "element_identifier": "31", "terms": [ "UE.Embodiment" ] }, { "element_identifier": "32", "terms": [ "embodiments", "embodiment" ] }, { "element_identifier": "33", "terms": [ "embodiment" ] }, { "element_identifier": "34", "terms": [ "embodiment" ] }, { "element_identifier": "35", "terms": [ "PRACH sequence together correspondingly.Embodiment" ] }, { "element_identifier": "36", "terms": [ "embodiment" ] }, { "element_identifier": "38", "terms": [ "cell identifier.Embodiment" ] }, { "element_identifier": "39", "terms": [ "Turbo coding.Embodiment" ] }, { "element_identifier": "40", "terms": [ "IFFT transformation.Embodiment" ] }, { "element_identifier": "42", "terms": [ "second cyclic prefix.Embodiment" ] }, { "element_identifier": "43", "terms": [ "embodiment" ] }, { "element_identifier": "45", "terms": [ "result onto discontinuous subcarriers.Embodiment" ] }, { "element_identifier": "46", "terms": [ "frequency hopping manner.Embodiment" ] }, { "element_identifier": "49", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "50", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "51", "terms": [ "frequency domain.Embodiment" ] }, { "element_identifier": "52", "terms": [ "same subframe.Embodiment" ] }, { "element_identifier": "53", "terms": [ "modulated symbol.Embodiment" ] }, { "element_identifier": "54", "terms": [ "PRACH sequence.Embodiment" ] }, { "element_identifier": "56", "terms": [ "first information.Embodiment" ] }, { "element_identifier": "57", "terms": [ "base station.Embodiment" ] }, { "element_identifier": "58", "terms": [ "broadcast message.Embodiment" ] }, { "element_identifier": "59", "terms": [ "control signaling.Embodiment" ] }, { "element_identifier": "60", "terms": [ "embodiment" ] }, { "element_identifier": "62", "terms": [ "UE.Embodiment" ] } ]

[ "602", "603", "33" ]

[ "FIG2" ]

[ "FIG2 is a block diagram of a transmitter system (also known as access network) and a receiver system (also known as user equipment or UE) according to one exemplary embodiment" ]

[ "FIG2 is a simplified block diagram of an embodiment of a transmitter system 210 (also known as the access network) and a receiver system 250 (also known as access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214." ]

[ { "element_identifier": "236", "terms": [ "data source" ] }, { "element_identifier": "210", "terms": [ "transmitter system" ] }, { "element_identifier": "214", "terms": [ "data processor" ] }, { "element_identifier": "230", "terms": [ "processor" ] }, { "element_identifier": "280", "terms": [ "modulator" ] }, { "element_identifier": "242", "terms": [ "RX data processor" ] }, { "element_identifier": "238", "terms": [ "TX data processor" ] }, { "element_identifier": "220", "terms": [ "TX MIMO processor" ] }, { "element_identifier": "2", "terms": [ "Type" ] }, { "element_identifier": "250", "terms": [ "receiver system" ] }, { "element_identifier": "270", "terms": [ "processor" ] }, { "element_identifier": "240", "terms": [ "demodulator" ] }, { "element_identifier": "260", "terms": [ "RX data processor" ] }, { "element_identifier": "200", "terms": [ "MIMO system" ] } ]

[ "200", "210", "214", "230", "242", "250", "260", "272", "280", "220", "232", "240", "270", "238", "236", "33", "2" ]

[ "FIG1" ]

[ "FIG1 shows a diagram of a wireless communication system according to one exemplary embodiment" ]

[ "FIG1 shows a multiple access wireless communication system according to one embodiment of the invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional including 112 and 114. In FIG1, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from access terminal 116 over reverse link 118. Access terminal (AT) 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal (AT) 122 over forward link 126 and receive information from access terminal (AT) 122 over reverse link 124. In a FDD system, communication links 118, 120, 124 and 126 may use different frequency for communication. For example, forward link 120 may use a different frequency then that used by reverse link 118." ]

[ { "element_identifier": "4", "terms": [ "described in sub clause" ] }, { "element_identifier": "37", "terms": [ "TS" ] }, { "element_identifier": "38", "terms": [ "TS" ] }, { "element_identifier": "11", "terms": [ "section" ] }, { "element_identifier": "2018", "terms": [ "16th - 20th April", "21st - 25th May" ] }, { "element_identifier": "100", "terms": [ "access network" ] }, { "element_identifier": "104", "terms": [ "one including" ] }, { "element_identifier": "106", "terms": [ "antennas" ] }, { "element_identifier": "108", "terms": [ "antennas" ] }, { "element_identifier": "110", "terms": [ "another including" ] }, { "element_identifier": "112", "terms": [ "antennas" ] }, { "element_identifier": "114", "terms": [ "antennas" ] }, { "element_identifier": "116", "terms": [ "access terminal", "access terminals" ] }, { "element_identifier": "120", "terms": [ "forward link", "forward links" ] }, { "element_identifier": "118", "terms": [ "reverse link" ] }, { "element_identifier": "126", "terms": [ "communication over forward links" ] }, { "element_identifier": "124", "terms": [ "over reverse link" ] }, { "element_identifier": "122", "terms": [ "different access terminals" ] }, { "element_identifier": "210", "terms": [ "transmitter system" ] }, { "element_identifier": "250", "terms": [ "receiver system" ] }, { "element_identifier": "200", "terms": [ "MIMO system" ] }, { "element_identifier": "212", "terms": [ "data source" ] }, { "element_identifier": "214", "terms": [ "data processor" ] }, { "element_identifier": "230", "terms": [ "processor" ] }, { "element_identifier": "220", "terms": [ "TX MIMO processor" ] }, { "element_identifier": "222t", "terms": [ "222a through" ] }, { "element_identifier": "222", "terms": [ "being transmitted. Each transmitter", "receivers" ] }, { "element_identifier": "222a", "terms": [ "modulated signals from transmitters" ] }, { "element_identifier": "224a", "terms": [ "transmitted from NT antennas" ] }, { "element_identifier": "224t", "terms": [ "NT antennas 224a through" ] }, { "element_identifier": "252a", "terms": [ "NR antennas" ] }, { "element_identifier": "252r", "terms": [ "NR antennas 252a through" ] }, { "element_identifier": "252", "terms": [ "signal from each antenna" ] }, { "element_identifier": "254r", "terms": [ "254a through" ] }, { "element_identifier": "254", "terms": [ "through 254r. Each receiver", "streams from NR receivers" ] }, { "element_identifier": "260", "terms": [ "RX data processor" ] }, { "element_identifier": "270", "terms": [ "processor" ] }, { "element_identifier": "238", "terms": [ "TX data processor" ] }, { "element_identifier": "236", "terms": [ "data source" ] }, { "element_identifier": "280", "terms": [ "modulator" ] }, { "element_identifier": "254a", "terms": [ "transmitters" ] }, { "element_identifier": "224", "terms": [ "antennas" ] }, { "element_identifier": "240", "terms": [ "demodulator" ] }, { "element_identifier": "242", "terms": [ "RX data processor" ] }, { "element_identifier": "300", "terms": [ "device" ] }, { "element_identifier": "302", "terms": [ "input device" ] }, { "element_identifier": "304", "terms": [ "output device" ] }, { "element_identifier": "306", "terms": [ "control circuit" ] }, { "element_identifier": "310", "terms": [ "memory" ] }, { "element_identifier": "312", "terms": [ "program code" ] }, { "element_identifier": "314", "terms": [ "transceiver" ] }, { "element_identifier": "308", "terms": [ "CPU" ] }, { "element_identifier": "400", "terms": [ "application layer" ] }, { "element_identifier": "3", "terms": [ "Layer" ] }, { "element_identifier": "402", "terms": [ "portion" ] }, { "element_identifier": "2", "terms": [ "Type" ] }, { "element_identifier": "404", "terms": [ "portion" ] }, { "element_identifier": "1", "terms": [ "Type" ] }, { "element_identifier": "406", "terms": [ "portion" ] }, { "element_identifier": "0", "terms": [ "N >", "INTEGER" ] }, { "element_identifier": "5", "terms": [ "frequencies defined in Subclause" ] }, { "element_identifier": "8", "terms": [ "CCE aggregation level" ] }, { "element_identifier": "16", "terms": [ "CCE aggregation level" ] }, { "element_identifier": "15", "terms": [ "in NR Rel.", "reference SCS is" ] }, { "element_identifier": "30", "terms": [ "SCS is" ] }, { "element_identifier": "28", "terms": [ "ms comprises" ] }, { "element_identifier": "1100", "terms": [ "flow chart" ] }, { "element_identifier": "1105", "terms": [ "In step" ] }, { "element_identifier": "1110", "terms": [ "serving cell. In step" ] }, { "element_identifier": "1115", "terms": [ "\"blank\". In step" ] }, { "element_identifier": "1200", "terms": [ "flow chart" ] }, { "element_identifier": "1205", "terms": [ "UE. In step" ] }, { "element_identifier": "1210", "terms": [ "serving cell. In step" ] }, { "element_identifier": "1215", "terms": [ "\"blank\". In step" ] }, { "element_identifier": "1300", "terms": [ "flow chart" ] }, { "element_identifier": "1305", "terms": [ "UE. In step" ] }, { "element_identifier": "1310", "terms": [ "serving cell. In step" ] }, { "element_identifier": "1315", "terms": [ "indication. In step" ] }, { "element_identifier": "1320", "terms": [ "occupancy time. In step" ] }, { "element_identifier": "1325", "terms": [ "scheduled resource. In step" ] }, { "element_identifier": "1330", "terms": [ "occupancy time. In step" ] } ]

[ "110", "112", "118", "116", "120", "108", "106", "104", "100", "122", "124", "114", "1", "32" ]

[ "FIG3" ]

[ "FIG3 shows an example wireless device and two base stations" ]

[ "FIG3 shows an example of base stations (base station 1, 120A, and base station 2, 120B) and a wireless device 110. The wireless device 110 may comprise a UE or any other wireless device. The base station (e.g., 120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other base station. A wireless device and/or a base station may perform one or more functions of a relay node. The base station 1, 120A, may comprise at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, and/or the like), at least one processor 321A, and at least one set of program code instructions 323A that may be stored in non-transitory memory 322A and executable by the at least one processor 321A. The base station 2, 120B, may comprise at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B that may be stored in non-transitory memory 322B and executable by the at least one processor 321B." ]

[ { "element_identifier": "310", "terms": [ "communication interface" ] }, { "element_identifier": "313", "terms": [ "touchpad" ] }, { "element_identifier": "1", "terms": [ "Msg" ] }, { "element_identifier": "2", "terms": [ "Msg" ] }, { "element_identifier": "319", "terms": [ "peripherals" ] }, { "element_identifier": "314", "terms": [ "processor" ] }, { "element_identifier": "311", "terms": [ "microphone" ] }, { "element_identifier": "315", "terms": [ "stored in non-transitory memory" ] }, { "element_identifier": "318", "terms": [ "chipset" ] }, { "element_identifier": "316", "terms": [ "program code instructions" ] }, { "element_identifier": "110", "terms": [ "wireless device", "wireless devices" ] }, { "element_identifier": "317", "terms": [ "power source" ] }, { "element_identifier": "312", "terms": [ "keypad" ] } ]

[ "1", "2", "110", "310", "311", "312", "313", "317", "314", "318", "09", "319", "315", "316" ]

[ "FIG20" ]

[ "FIG20 shows an example generic random access resource configuration, and field descriptions" ]

[ "A wireless device may determine a random access procedure unsuccessfully completed. The wireless device may consider the random access procedure unsuccessfully completed, for example, if a wireless device receives no RAR corresponding to one or more preambles sent by the wireless device during a random access procedure. There may be a number of preamble transmissions allowed during a random access procedure (e.g., preambleTransMax in FIG20), wherein the number of preamble transmissions may be semi-statically configured by RRC. The wireless device may consider a random access procedure unsuccessfully completed, for example, if a wireless device receives no RAR corresponding to the number of preamble transmissions. A wireless device may indicate a problem to upper layer(s), for example, after an unsuccessful completion of a random access procedure, and after the indicated problem. The upper layers(s) may trigger radio link failure that may lead to prolonged random access delay and degraded user experience." ]

[ { "element_identifier": "9", "terms": [ "August" ] }, { "element_identifier": "1", "terms": [ "Msg" ] }, { "element_identifier": "2", "terms": [ "Msg" ] }, { "element_identifier": "110", "terms": [ "wireless device", "wireless devices" ] }, { "element_identifier": "310", "terms": [ "communication interface" ] }, { "element_identifier": "314", "terms": [ "processor" ] }, { "element_identifier": "316", "terms": [ "program code instructions" ] }, { "element_identifier": "315", "terms": [ "stored in non-transitory memory" ] }, { "element_identifier": "311", "terms": [ "microphone" ] }, { "element_identifier": "312", "terms": [ "keypad" ] }, { "element_identifier": "313", "terms": [ "touchpad" ] }, { "element_identifier": "317", "terms": [ "power source" ] }, { "element_identifier": "318", "terms": [ "chipset" ] }, { "element_identifier": "319", "terms": [ "peripherals" ] }, { "element_identifier": "506", "terms": [ "uplink DM-RS" ] }, { "element_identifier": "503", "terms": [ "PUSCH" ] }, { "element_identifier": "504", "terms": [ "PUCCH" ] }, { "element_identifier": "507", "terms": [ "uplink PT-RS" ] }, { "element_identifier": "508", "terms": [ "SRS" ] }, { "element_identifier": "0", "terms": [ "each", "DCI code points", "received HARQ information is" ] }, { "element_identifier": "501", "terms": [ "UL-SCH" ] }, { "element_identifier": "502", "terms": [ "RACH" ] }, { "element_identifier": "505", "terms": [ "PRACH" ] }, { "element_identifier": "511", "terms": [ "DL-SCH" ] }, { "element_identifier": "512", "terms": [ "PCH" ] }, { "element_identifier": "513", "terms": [ "BCH" ] }, { "element_identifier": "509", "terms": [ "UCI" ] }, { "element_identifier": "517", "terms": [ "DCI" ] }, { "element_identifier": "515", "terms": [ "PDCCH" ] }, { "element_identifier": "522", "terms": [ "CSI-RS" ] }, { "element_identifier": "523", "terms": [ "downlink DM-RSs" ] }, { "element_identifier": "524", "terms": [ "PT-RS" ] }, { "element_identifier": "521", "terms": [ "PSS/SSS" ] }, { "element_identifier": "516", "terms": [ "PBCH" ] }, { "element_identifier": "32", "terms": [ "wireless device with" ] }, { "element_identifier": "514", "terms": [ "PDSCH" ] }, { "element_identifier": "12", "terms": [ "ADM-RS configuration may support", "slot may be", "may comprise" ] }, { "element_identifier": "601", "terms": [ "organized into radio frames" ] }, { "element_identifier": "10", "terms": [ "frame duration may be" ] }, { "element_identifier": "602", "terms": [ "ten equally sized subframes" ] }, { "element_identifier": "603", "terms": [ "slots" ] }, { "element_identifier": "15", "terms": [ "subframe with", "carrier is", "values" ] }, { "element_identifier": "604", "terms": [ "OFDM symbols" ] }, { "element_identifier": "14", "terms": [ "slot may be", "subframe may have", "≤ s_id <" ] }, { "element_identifier": "700", "terms": [ "channel bandwidth" ] }, { "element_identifier": "701", "terms": [ "arrow" ] }, { "element_identifier": "702", "terms": [ "subcarrier spacing" ] }, { "element_identifier": "703", "terms": [ "subcarriers" ] }, { "element_identifier": "704", "terms": [ "guard bands" ] }, { "element_identifier": "705", "terms": [ "guard bands" ] }, { "element_identifier": "706", "terms": [ "subcarriers" ] }, { "element_identifier": "709", "terms": [ "first subcarrier spacing" ] }, { "element_identifier": "707", "terms": [ "subcarriers" ] }, { "element_identifier": "710", "terms": [ "second subcarrier spacing" ] }, { "element_identifier": "708", "terms": [ "subcarriers" ] }, { "element_identifier": "711", "terms": [ "third subcarrier spacing" ] }, { "element_identifier": "801", "terms": [ "transmission bandwidth" ] }, { "element_identifier": "802", "terms": [ "frequency domain" ] }, { "element_identifier": "803", "terms": [ "time domain" ] }, { "element_identifier": "805", "terms": [ "resource element" ] }, { "element_identifier": "807", "terms": [ "OFDM symbols" ] }, { "element_identifier": "28", "terms": [ "subframe may have" ] }, { "element_identifier": "30", "terms": [ "numerology is" ] }, { "element_identifier": "56", "terms": [ "subframe may have" ] }, { "element_identifier": "60", "terms": [ "numerology is" ] }, { "element_identifier": "806", "terms": [ "resource block" ] }, { "element_identifier": "940", "terms": [ "SS burst", "SS bursts" ] }, { "element_identifier": "950", "terms": [ "SS burst set" ] }, { "element_identifier": "120", "terms": [ "base station", "base stations" ] }, { "element_identifier": "910", "terms": [ "P1 procedure" ] }, { "element_identifier": "920", "terms": [ "P2 procedure" ] }, { "element_identifier": "930", "terms": [ "P3 procedure" ] }, { "element_identifier": "1010", "terms": [ "BWP1" ] }, { "element_identifier": "1050", "terms": [ "BWP1" ] }, { "element_identifier": "1020", "terms": [ "BWP2" ] }, { "element_identifier": "1040", "terms": [ "BWP2" ] }, { "element_identifier": "1030", "terms": [ "BWP3" ] }, { "element_identifier": "1130", "terms": [ "MN" ] }, { "element_identifier": "1150", "terms": [ "SN" ] }, { "element_identifier": "1110", "terms": [ "SDAP" ] }, { "element_identifier": "1111", "terms": [ "NR PDCP" ] }, { "element_identifier": "1114", "terms": [ "MN RLC" ] }, { "element_identifier": "1118", "terms": [ "MN MAC" ] }, { "element_identifier": "1112", "terms": [ "NR PDCP" ] }, { "element_identifier": "1115", "terms": [ "MN RLC" ] }, { "element_identifier": "1116", "terms": [ "SN RLC" ] }, { "element_identifier": "1119", "terms": [ "MAC" ] }, { "element_identifier": "1113", "terms": [ "NR PDCP" ] }, { "element_identifier": "1117", "terms": [ "SN RLC" ] }, { "element_identifier": "1120", "terms": [ "SDAP" ] }, { "element_identifier": "1140", "terms": [ "SDAP" ] }, { "element_identifier": "1121", "terms": [ "NR PDCP" ] }, { "element_identifier": "1142", "terms": [ "NR PDCP" ] }, { "element_identifier": "1124", "terms": [ "MN RLC" ] }, { "element_identifier": "1125", "terms": [ "MN RLC" ] }, { "element_identifier": "1128", "terms": [ "MN MAC" ] }, { "element_identifier": "1122", "terms": [ "NR PDCP" ] }, { "element_identifier": "1143", "terms": [ "NR PDCP" ] }, { "element_identifier": "1146", "terms": [ "SN RLC" ] }, { "element_identifier": "1147", "terms": [ "SN RLC" ] }, { "element_identifier": "1148", "terms": [ "SN MAC" ] }, { "element_identifier": "1123", "terms": [ "NR PDCP" ] }, { "element_identifier": "1141", "terms": [ "NR PDCP" ] }, { "element_identifier": "1126", "terms": [ "MN RLC" ] }, { "element_identifier": "1144", "terms": [ "SN RLC" ] }, { "element_identifier": "1145", "terms": [ "SN RLC" ] }, { "element_identifier": "1127", "terms": [ "MN RLC" ] }, { "element_identifier": "1230", "terms": [ "Msg2" ] }, { "element_identifier": "1240", "terms": [ "Msg3" ] }, { "element_identifier": "1250", "terms": [ "contention resolution" ] }, { "element_identifier": "3", "terms": [ "Msg" ] }, { "element_identifier": "1220", "terms": [ "Msg1" ] }, { "element_identifier": "1210", "terms": [ "RACH configuration" ] }, { "element_identifier": "1355", "terms": [ "Control" ] }, { "element_identifier": "1365", "terms": [ "Control" ] }, { "element_identifier": "1352", "terms": [ "Multiplexing" ] }, { "element_identifier": "1362", "terms": [ "Multiplexing" ] }, { "element_identifier": "1351", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1361", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1354", "terms": [ "Random Access Control" ] }, { "element_identifier": "1364", "terms": [ "Random Access Control" ] }, { "element_identifier": "1530", "terms": [ "RRC Connected" ] }, { "element_identifier": "1510", "terms": [ "RRC Idle" ] }, { "element_identifier": "1520", "terms": [ "RRC Inactive" ] }, { "element_identifier": "1540", "terms": [ "connection release" ] }, { "element_identifier": "1570", "terms": [ "connection inactivation" ] }, { "element_identifier": "1580", "terms": [ "connection resume" ] }, { "element_identifier": "1560", "terms": [ "connection release" ] }, { "element_identifier": "4", "terms": [ "Category" ] }, { "element_identifier": "6", "terms": [ "carriers greater than" ] }, { "element_identifier": "80", "terms": [ "≤ t_id <" ] }, { "element_identifier": "8", "terms": [ "≤ f_id <" ] }, { "element_identifier": "25", "terms": [ "UL transmission exceeding" ] }, { "element_identifier": "16", "terms": [ "less than", "between" ] }, { "element_identifier": "2510", "terms": [ "coverage" ] }, { "element_identifier": "2520", "terms": [ "coverage" ] }, { "element_identifier": "2650", "terms": [ "contention resolution" ] }, { "element_identifier": "3102", "terms": [ "downlink reference signals" ] }, { "element_identifier": "3202", "terms": [ "At step" ] }, { "element_identifier": "3204", "terms": [ "step" ] }, { "element_identifier": "3206", "terms": [ "At step" ] }, { "element_identifier": "3208", "terms": [ "step" ] }, { "element_identifier": "3210", "terms": [ "DL RSs. At step" ] }, { "element_identifier": "3212", "terms": [ "at step" ] }, { "element_identifier": "3214", "terms": [ "at step" ] }, { "element_identifier": "3216", "terms": [ "at step" ] }, { "element_identifier": "3302", "terms": [ "step" ] }, { "element_identifier": "3304", "terms": [ "step" ] }, { "element_identifier": "3306", "terms": [ "LBT procedure. At step" ] }, { "element_identifier": "3308", "terms": [ "At step" ] }, { "element_identifier": "3310", "terms": [ "step" ] }, { "element_identifier": "3312", "terms": [ "step" ] }, { "element_identifier": "3314", "terms": [ "at step" ] }, { "element_identifier": "41", "terms": [ "clause" ] }, { "element_identifier": "81", "terms": [ "clauses", "clause" ] }, { "element_identifier": "3400", "terms": [ "computing device" ] }, { "element_identifier": "3401", "terms": [ "processor", "processors" ] }, { "element_identifier": "3404", "terms": [ "removable media" ] }, { "element_identifier": "3405", "terms": [ "hard drive" ] }, { "element_identifier": "3402", "terms": [ "ROM storage" ] }, { "element_identifier": "3403", "terms": [ "RAM" ] }, { "element_identifier": "3407", "terms": [ "output device controllers" ] }, { "element_identifier": "3409", "terms": [ "network interface" ] }, { "element_identifier": "3411", "terms": [ "GPS", "microprocessor" ] }, { "element_identifier": "3412", "terms": [ "Bluetooth interface" ] }, { "element_identifier": "3413", "terms": [ "WiFi interface" ] }, { "element_identifier": "3406", "terms": [ "display" ] }, { "element_identifier": "3408", "terms": [ "user input devices" ] }, { "element_identifier": "3410", "terms": [ "network" ] } ]

[ "20", "5", "10", "5" ]

[ "FIG1" ]

[ "FIG1 shows an example radio access network (RAN) architecture" ]

[ "FIG1 shows an example Radio Access Network (RAN) architecture. A RAN node may comprise a next generation Node B (gNB) (e.g., 120A, 120B) providing New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g., 110A). A RAN node may comprise a base station such as a next generation evolved Node B (ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device (e.g., 110B). A first wireless device 110A may communicate with a base station, such as a gNB 120A, over a Uu interface. A second wireless device 110B may communicate with a base station, such as an ng-eNB 120D, over a Uu interface. The wireless devices 110A and/or 110B may be structurally similar to wireless devices shown in and/or described in connection with other drawing figures. The Node B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120D may be structurally similar to Nodes B and/or base stations shown in and/or described in connection with other drawing figures." ]

[ { "element_identifier": "9", "terms": [ "August" ] }, { "element_identifier": "1", "terms": [ "Msg" ] }, { "element_identifier": "2", "terms": [ "Msg" ] }, { "element_identifier": "110", "terms": [ "wireless device", "wireless devices" ] }, { "element_identifier": "310", "terms": [ "communication interface" ] }, { "element_identifier": "314", "terms": [ "processor" ] }, { "element_identifier": "316", "terms": [ "program code instructions" ] }, { "element_identifier": "315", "terms": [ "stored in non-transitory memory" ] }, { "element_identifier": "311", "terms": [ "microphone" ] }, { "element_identifier": "312", "terms": [ "keypad" ] }, { "element_identifier": "313", "terms": [ "touchpad" ] }, { "element_identifier": "317", "terms": [ "power source" ] }, { "element_identifier": "318", "terms": [ "chipset" ] }, { "element_identifier": "319", "terms": [ "peripherals" ] }, { "element_identifier": "506", "terms": [ "uplink DM-RS" ] }, { "element_identifier": "503", "terms": [ "PUSCH" ] }, { "element_identifier": "504", "terms": [ "PUCCH" ] }, { "element_identifier": "507", "terms": [ "uplink PT-RS" ] }, { "element_identifier": "508", "terms": [ "SRS" ] }, { "element_identifier": "0", "terms": [ "each", "DCI code points", "received HARQ information is" ] }, { "element_identifier": "501", "terms": [ "UL-SCH" ] }, { "element_identifier": "502", "terms": [ "RACH" ] }, { "element_identifier": "505", "terms": [ "PRACH" ] }, { "element_identifier": "511", "terms": [ "DL-SCH" ] }, { "element_identifier": "512", "terms": [ "PCH" ] }, { "element_identifier": "513", "terms": [ "BCH" ] }, { "element_identifier": "509", "terms": [ "UCI" ] }, { "element_identifier": "517", "terms": [ "DCI" ] }, { "element_identifier": "515", "terms": [ "PDCCH" ] }, { "element_identifier": "522", "terms": [ "CSI-RS" ] }, { "element_identifier": "523", "terms": [ "downlink DM-RSs" ] }, { "element_identifier": "524", "terms": [ "PT-RS" ] }, { "element_identifier": "521", "terms": [ "PSS/SSS" ] }, { "element_identifier": "516", "terms": [ "PBCH" ] }, { "element_identifier": "32", "terms": [ "wireless device with" ] }, { "element_identifier": "514", "terms": [ "PDSCH" ] }, { "element_identifier": "12", "terms": [ "ADM-RS configuration may support", "slot may be", "may comprise" ] }, { "element_identifier": "601", "terms": [ "organized into radio frames" ] }, { "element_identifier": "10", "terms": [ "frame duration may be" ] }, { "element_identifier": "602", "terms": [ "ten equally sized subframes" ] }, { "element_identifier": "603", "terms": [ "slots" ] }, { "element_identifier": "15", "terms": [ "subframe with", "carrier is", "values" ] }, { "element_identifier": "604", "terms": [ "OFDM symbols" ] }, { "element_identifier": "14", "terms": [ "slot may be", "subframe may have", "≤ s_id <" ] }, { "element_identifier": "700", "terms": [ "channel bandwidth" ] }, { "element_identifier": "701", "terms": [ "arrow" ] }, { "element_identifier": "702", "terms": [ "subcarrier spacing" ] }, { "element_identifier": "703", "terms": [ "subcarriers" ] }, { "element_identifier": "704", "terms": [ "guard bands" ] }, { "element_identifier": "705", "terms": [ "guard bands" ] }, { "element_identifier": "706", "terms": [ "subcarriers" ] }, { "element_identifier": "709", "terms": [ "first subcarrier spacing" ] }, { "element_identifier": "707", "terms": [ "subcarriers" ] }, { "element_identifier": "710", "terms": [ "second subcarrier spacing" ] }, { "element_identifier": "708", "terms": [ "subcarriers" ] }, { "element_identifier": "711", "terms": [ "third subcarrier spacing" ] }, { "element_identifier": "801", "terms": [ "transmission bandwidth" ] }, { "element_identifier": "802", "terms": [ "frequency domain" ] }, { "element_identifier": "803", "terms": [ "time domain" ] }, { "element_identifier": "805", "terms": [ "resource element" ] }, { "element_identifier": "807", "terms": [ "OFDM symbols" ] }, { "element_identifier": "28", "terms": [ "subframe may have" ] }, { "element_identifier": "30", "terms": [ "numerology is" ] }, { "element_identifier": "56", "terms": [ "subframe may have" ] }, { "element_identifier": "60", "terms": [ "numerology is" ] }, { "element_identifier": "806", "terms": [ "resource block" ] }, { "element_identifier": "940", "terms": [ "SS burst", "SS bursts" ] }, { "element_identifier": "950", "terms": [ "SS burst set" ] }, { "element_identifier": "120", "terms": [ "base station", "base stations" ] }, { "element_identifier": "910", "terms": [ "P1 procedure" ] }, { "element_identifier": "920", "terms": [ "P2 procedure" ] }, { "element_identifier": "930", "terms": [ "P3 procedure" ] }, { "element_identifier": "1010", "terms": [ "BWP1" ] }, { "element_identifier": "1050", "terms": [ "BWP1" ] }, { "element_identifier": "1020", "terms": [ "BWP2" ] }, { "element_identifier": "1040", "terms": [ "BWP2" ] }, { "element_identifier": "1030", "terms": [ "BWP3" ] }, { "element_identifier": "1130", "terms": [ "MN" ] }, { "element_identifier": "1150", "terms": [ "SN" ] }, { "element_identifier": "1110", "terms": [ "SDAP" ] }, { "element_identifier": "1111", "terms": [ "NR PDCP" ] }, { "element_identifier": "1114", "terms": [ "MN RLC" ] }, { "element_identifier": "1118", "terms": [ "MN MAC" ] }, { "element_identifier": "1112", "terms": [ "NR PDCP" ] }, { "element_identifier": "1115", "terms": [ "MN RLC" ] }, { "element_identifier": "1116", "terms": [ "SN RLC" ] }, { "element_identifier": "1119", "terms": [ "MAC" ] }, { "element_identifier": "1113", "terms": [ "NR PDCP" ] }, { "element_identifier": "1117", "terms": [ "SN RLC" ] }, { "element_identifier": "1120", "terms": [ "SDAP" ] }, { "element_identifier": "1140", "terms": [ "SDAP" ] }, { "element_identifier": "1121", "terms": [ "NR PDCP" ] }, { "element_identifier": "1142", "terms": [ "NR PDCP" ] }, { "element_identifier": "1124", "terms": [ "MN RLC" ] }, { "element_identifier": "1125", "terms": [ "MN RLC" ] }, { "element_identifier": "1128", "terms": [ "MN MAC" ] }, { "element_identifier": "1122", "terms": [ "NR PDCP" ] }, { "element_identifier": "1143", "terms": [ "NR PDCP" ] }, { "element_identifier": "1146", "terms": [ "SN RLC" ] }, { "element_identifier": "1147", "terms": [ "SN RLC" ] }, { "element_identifier": "1148", "terms": [ "SN MAC" ] }, { "element_identifier": "1123", "terms": [ "NR PDCP" ] }, { "element_identifier": "1141", "terms": [ "NR PDCP" ] }, { "element_identifier": "1126", "terms": [ "MN RLC" ] }, { "element_identifier": "1144", "terms": [ "SN RLC" ] }, { "element_identifier": "1145", "terms": [ "SN RLC" ] }, { "element_identifier": "1127", "terms": [ "MN RLC" ] }, { "element_identifier": "1230", "terms": [ "Msg2" ] }, { "element_identifier": "1240", "terms": [ "Msg3" ] }, { "element_identifier": "1250", "terms": [ "contention resolution" ] }, { "element_identifier": "3", "terms": [ "Msg" ] }, { "element_identifier": "1220", "terms": [ "Msg1" ] }, { "element_identifier": "1210", "terms": [ "RACH configuration" ] }, { "element_identifier": "1355", "terms": [ "Control" ] }, { "element_identifier": "1365", "terms": [ "Control" ] }, { "element_identifier": "1352", "terms": [ "Multiplexing" ] }, { "element_identifier": "1362", "terms": [ "Multiplexing" ] }, { "element_identifier": "1351", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1361", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1354", "terms": [ "Random Access Control" ] }, { "element_identifier": "1364", "terms": [ "Random Access Control" ] }, { "element_identifier": "1530", "terms": [ "RRC Connected" ] }, { "element_identifier": "1510", "terms": [ "RRC Idle" ] }, { "element_identifier": "1520", "terms": [ "RRC Inactive" ] }, { "element_identifier": "1540", "terms": [ "connection release" ] }, { "element_identifier": "1570", "terms": [ "connection inactivation" ] }, { "element_identifier": "1580", "terms": [ "connection resume" ] }, { "element_identifier": "1560", "terms": [ "connection release" ] }, { "element_identifier": "4", "terms": [ "Category" ] }, { "element_identifier": "6", "terms": [ "carriers greater than" ] }, { "element_identifier": "80", "terms": [ "≤ t_id <" ] }, { "element_identifier": "8", "terms": [ "≤ f_id <" ] }, { "element_identifier": "25", "terms": [ "UL transmission exceeding" ] }, { "element_identifier": "16", "terms": [ "less than", "between" ] }, { "element_identifier": "2510", "terms": [ "coverage" ] }, { "element_identifier": "2520", "terms": [ "coverage" ] }, { "element_identifier": "2650", "terms": [ "contention resolution" ] }, { "element_identifier": "3102", "terms": [ "downlink reference signals" ] }, { "element_identifier": "3202", "terms": [ "At step" ] }, { "element_identifier": "3204", "terms": [ "step" ] }, { "element_identifier": "3206", "terms": [ "At step" ] }, { "element_identifier": "3208", "terms": [ "step" ] }, { "element_identifier": "3210", "terms": [ "DL RSs. At step" ] }, { "element_identifier": "3212", "terms": [ "at step" ] }, { "element_identifier": "3214", "terms": [ "at step" ] }, { "element_identifier": "3216", "terms": [ "at step" ] }, { "element_identifier": "3302", "terms": [ "step" ] }, { "element_identifier": "3304", "terms": [ "step" ] }, { "element_identifier": "3306", "terms": [ "LBT procedure. At step" ] }, { "element_identifier": "3308", "terms": [ "At step" ] }, { "element_identifier": "3310", "terms": [ "step" ] }, { "element_identifier": "3312", "terms": [ "step" ] }, { "element_identifier": "3314", "terms": [ "at step" ] }, { "element_identifier": "41", "terms": [ "clause" ] }, { "element_identifier": "81", "terms": [ "clauses", "clause" ] }, { "element_identifier": "3400", "terms": [ "computing device" ] }, { "element_identifier": "3401", "terms": [ "processor", "processors" ] }, { "element_identifier": "3404", "terms": [ "removable media" ] }, { "element_identifier": "3405", "terms": [ "hard drive" ] }, { "element_identifier": "3402", "terms": [ "ROM storage" ] }, { "element_identifier": "3403", "terms": [ "RAM" ] }, { "element_identifier": "3407", "terms": [ "output device controllers" ] }, { "element_identifier": "3409", "terms": [ "network interface" ] }, { "element_identifier": "3411", "terms": [ "GPS", "microprocessor" ] }, { "element_identifier": "3412", "terms": [ "Bluetooth interface" ] }, { "element_identifier": "3413", "terms": [ "WiFi interface" ] }, { "element_identifier": "3406", "terms": [ "display" ] }, { "element_identifier": "3408", "terms": [ "user input devices" ] }, { "element_identifier": "3410", "terms": [ "network" ] } ]

[ "58", "1" ]

[ "FIG3" ]

[ "FIG3 shows an example wireless device and two base stations" ]

[ "FIG3 shows an example of base stations (base station 1, 120A, and base station 2, 120B) and a wireless device 110. The wireless device 110 may comprise a UE or any other wireless device. The base station (e.g., 120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other base station. A wireless device and/or a base station may perform one or more functions of a relay node. The base station 1, 120A, may comprise at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, and/or the like), at least one processor 321A, and at least one set of program code instructions 323A that may be stored in non-transitory memory 322A and executable by the at least one processor 321A. The base station 2, 120B, may comprise at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B that may be stored in non-transitory memory 322B and executable by the at least one processor 321B." ]

[ { "element_identifier": "310", "terms": [ "communication interface" ] }, { "element_identifier": "313", "terms": [ "touchpad" ] }, { "element_identifier": "1", "terms": [ "clauses", "clause" ] }, { "element_identifier": "2", "terms": [ "Octets", "Octet" ] }, { "element_identifier": "319", "terms": [ "peripherals" ] }, { "element_identifier": "314", "terms": [ "processor" ] }, { "element_identifier": "311", "terms": [ "microphone" ] }, { "element_identifier": "315", "terms": [ "stored in non-transitory memory" ] }, { "element_identifier": "318", "terms": [ "chipset" ] }, { "element_identifier": "316", "terms": [ "program code instructions" ] }, { "element_identifier": "110", "terms": [ "wireless device", "wireless devices" ] }, { "element_identifier": "317", "terms": [ "power source" ] }, { "element_identifier": "312", "terms": [ "keypad" ] } ]

[ "110", "310", "1", "322", "311", "317", "312", "313", "314", "318", "76", "2", "322", "319", "315", "316" ]

[ "FIG21C" ]

[ "FIG21C shows an example of MAC CEs for SCell state transitions" ]

[ "FIG21C shows example configurations of a field of the first MAC CE. The field may comprise, for example, a Ci field of the first MAC CE (e.g., an activation/deactivation MAC CE), a Ci field of the second MAC CE (e.g., a hibernation MAC CE), and corresponding resulting SCell status (e.g., activated/deactivated/dormant). The wireless device may deactivate an SCell associated with SCell index i, for example, if Ci of hibernation MAC CE is set to 0, and Ci of the activation/deactivation MAC CE is set to 0. The wireless device may activate an SCell associated with SCell index i, for example, if Ci of hibernation MAC CE is set to 0, and Ci of the activation/deactivation MAC CE is set to 1. The wireless device may ignore the hibernation MAC CE and the activation/deactivation MAC CE, for example, if Ci of hibernation MAC CE is set to 1, and Ci of the activation/deactivation MAC CE is set to 0. The wireless device may transition an SCell associated with SCell index I to a dormant state, for example, if Ci of hibernation MAC CE is set to 1, and Ci of the activation/deactivation MAC CE is set to 1." ]

[ { "element_identifier": "9", "terms": [ "August" ] }, { "element_identifier": "1", "terms": [ "clauses", "clause" ] }, { "element_identifier": "2", "terms": [ "Octets", "Octet" ] }, { "element_identifier": "110", "terms": [ "wireless device", "wireless devices" ] }, { "element_identifier": "310", "terms": [ "communication interface" ] }, { "element_identifier": "314", "terms": [ "processor" ] }, { "element_identifier": "316", "terms": [ "program code instructions" ] }, { "element_identifier": "315", "terms": [ "stored in non-transitory memory" ] }, { "element_identifier": "311", "terms": [ "microphone" ] }, { "element_identifier": "312", "terms": [ "keypad" ] }, { "element_identifier": "313", "terms": [ "touchpad" ] }, { "element_identifier": "317", "terms": [ "power source" ] }, { "element_identifier": "318", "terms": [ "chipset" ] }, { "element_identifier": "319", "terms": [ "peripherals" ] }, { "element_identifier": "506", "terms": [ "uplink DM-RS" ] }, { "element_identifier": "503", "terms": [ "PUSCH" ] }, { "element_identifier": "504", "terms": [ "PUCCH" ] }, { "element_identifier": "507", "terms": [ "uplink PT-RS" ] }, { "element_identifier": "508", "terms": [ "SRS" ] }, { "element_identifier": "0", "terms": [ "BFR-RS-resource" ] }, { "element_identifier": "501", "terms": [ "UL-SCH" ] }, { "element_identifier": "502", "terms": [ "RACH" ] }, { "element_identifier": "505", "terms": [ "PRACH" ] }, { "element_identifier": "511", "terms": [ "DL-SCH" ] }, { "element_identifier": "512", "terms": [ "PCH" ] }, { "element_identifier": "513", "terms": [ "BCH" ] }, { "element_identifier": "509", "terms": [ "UCI" ] }, { "element_identifier": "517", "terms": [ "DCI" ] }, { "element_identifier": "515", "terms": [ "PDCCH" ] }, { "element_identifier": "522", "terms": [ "CSI-RS" ] }, { "element_identifier": "523", "terms": [ "downlink DM-RSs" ] }, { "element_identifier": "524", "terms": [ "PT-RS" ] }, { "element_identifier": "521", "terms": [ "PSS/SSS" ] }, { "element_identifier": "516", "terms": [ "PBCH" ] }, { "element_identifier": "32", "terms": [ "wireless device with", "less than" ] }, { "element_identifier": "514", "terms": [ "PDSCH" ] }, { "element_identifier": "12", "terms": [ "ADM-RS configuration may support", "slot may be", "may comprise" ] }, { "element_identifier": "601", "terms": [ "organized into radio frames" ] }, { "element_identifier": "10", "terms": [ "frame duration may be" ] }, { "element_identifier": "602", "terms": [ "ten equally sized subframes" ] }, { "element_identifier": "603", "terms": [ "slots" ] }, { "element_identifier": "15", "terms": [ "subframe with", "carrier is", "compliant with 3GPP Release" ] }, { "element_identifier": "604", "terms": [ "OFDM symbols" ] }, { "element_identifier": "14", "terms": [ "slot may be", "subframe may have" ] }, { "element_identifier": "700", "terms": [ "channel bandwidth" ] }, { "element_identifier": "701", "terms": [ "arrow" ] }, { "element_identifier": "702", "terms": [ "subcarrier spacing" ] }, { "element_identifier": "703", "terms": [ "subcarriers" ] }, { "element_identifier": "704", "terms": [ "guard bands" ] }, { "element_identifier": "705", "terms": [ "guard bands" ] }, { "element_identifier": "706", "terms": [ "subcarriers" ] }, { "element_identifier": "709", "terms": [ "first subcarrier spacing" ] }, { "element_identifier": "707", "terms": [ "subcarriers" ] }, { "element_identifier": "710", "terms": [ "second subcarrier spacing" ] }, { "element_identifier": "708", "terms": [ "subcarriers" ] }, { "element_identifier": "711", "terms": [ "third subcarrier spacing" ] }, { "element_identifier": "801", "terms": [ "transmission bandwidth" ] }, { "element_identifier": "802", "terms": [ "frequency domain" ] }, { "element_identifier": "803", "terms": [ "time domain" ] }, { "element_identifier": "805", "terms": [ "resource element" ] }, { "element_identifier": "807", "terms": [ "OFDM symbols" ] }, { "element_identifier": "28", "terms": [ "subframe may have" ] }, { "element_identifier": "30", "terms": [ "numerology is" ] }, { "element_identifier": "56", "terms": [ "subframe may have" ] }, { "element_identifier": "60", "terms": [ "numerology is", "clause" ] }, { "element_identifier": "806", "terms": [ "resource block" ] }, { "element_identifier": "940", "terms": [ "SS burst", "SS bursts" ] }, { "element_identifier": "950", "terms": [ "SS burst set" ] }, { "element_identifier": "120", "terms": [ "base station", "base stations" ] }, { "element_identifier": "910", "terms": [ "P1 procedure" ] }, { "element_identifier": "920", "terms": [ "P2 procedure" ] }, { "element_identifier": "930", "terms": [ "P3 procedure" ] }, { "element_identifier": "1010", "terms": [ "BWP1" ] }, { "element_identifier": "1050", "terms": [ "BWP1" ] }, { "element_identifier": "1020", "terms": [ "BWP2" ] }, { "element_identifier": "1040", "terms": [ "BWP2" ] }, { "element_identifier": "1030", "terms": [ "BWP3" ] }, { "element_identifier": "1130", "terms": [ "MN" ] }, { "element_identifier": "1150", "terms": [ "SN" ] }, { "element_identifier": "1110", "terms": [ "SDAP" ] }, { "element_identifier": "1111", "terms": [ "NR PDCP" ] }, { "element_identifier": "1114", "terms": [ "MN RLC" ] }, { "element_identifier": "1118", "terms": [ "MN MAC" ] }, { "element_identifier": "1112", "terms": [ "NR PDCP" ] }, { "element_identifier": "1115", "terms": [ "MN RLC" ] }, { "element_identifier": "1116", "terms": [ "SN RLC" ] }, { "element_identifier": "1119", "terms": [ "MAC" ] }, { "element_identifier": "1113", "terms": [ "NR PDCP" ] }, { "element_identifier": "1117", "terms": [ "SN RLC" ] }, { "element_identifier": "1120", "terms": [ "SDAP" ] }, { "element_identifier": "1140", "terms": [ "SDAP" ] }, { "element_identifier": "1121", "terms": [ "NR PDCP" ] }, { "element_identifier": "1142", "terms": [ "NR PDCP" ] }, { "element_identifier": "1124", "terms": [ "MN RLC" ] }, { "element_identifier": "1125", "terms": [ "MN RLC" ] }, { "element_identifier": "1128", "terms": [ "MN MAC" ] }, { "element_identifier": "1122", "terms": [ "NR PDCP" ] }, { "element_identifier": "1143", "terms": [ "NR PDCP" ] }, { "element_identifier": "1146", "terms": [ "SN RLC" ] }, { "element_identifier": "1147", "terms": [ "SN RLC" ] }, { "element_identifier": "1148", "terms": [ "SN MAC" ] }, { "element_identifier": "1123", "terms": [ "NR PDCP" ] }, { "element_identifier": "1141", "terms": [ "NR PDCP" ] }, { "element_identifier": "1126", "terms": [ "MN RLC" ] }, { "element_identifier": "1144", "terms": [ "SN RLC" ] }, { "element_identifier": "1145", "terms": [ "SN RLC" ] }, { "element_identifier": "1127", "terms": [ "MN RLC" ] }, { "element_identifier": "1230", "terms": [ "Msg2" ] }, { "element_identifier": "1240", "terms": [ "Msg3" ] }, { "element_identifier": "1250", "terms": [ "contention resolution" ] }, { "element_identifier": "3", "terms": [ "Msg" ] }, { "element_identifier": "1220", "terms": [ "Msg1" ] }, { "element_identifier": "1210", "terms": [ "RACH configuration" ] }, { "element_identifier": "1355", "terms": [ "Control" ] }, { "element_identifier": "1365", "terms": [ "Control" ] }, { "element_identifier": "1352", "terms": [ "Multiplexing" ] }, { "element_identifier": "1362", "terms": [ "Multiplexing" ] }, { "element_identifier": "1351", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1361", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1354", "terms": [ "Random Access Control" ] }, { "element_identifier": "1364", "terms": [ "Random Access Control" ] }, { "element_identifier": "1530", "terms": [ "RRC Connected" ] }, { "element_identifier": "1510", "terms": [ "RRC Idle" ] }, { "element_identifier": "1520", "terms": [ "RRC Inactive" ] }, { "element_identifier": "1540", "terms": [ "connection release" ] }, { "element_identifier": "1570", "terms": [ "connection inactivation" ] }, { "element_identifier": "1580", "terms": [ "connection resume" ] }, { "element_identifier": "1560", "terms": [ "connection release" ] }, { "element_identifier": "111011", "terms": [ "LCID with" ] }, { "element_identifier": "31", "terms": [ "maycomprise four octets comprising" ] }, { "element_identifier": "2402", "terms": [ "base station" ] }, { "element_identifier": "2401", "terms": [ "wireless device" ] }, { "element_identifier": "2403", "terms": [ "moving vehicle" ] }, { "element_identifier": "2411", "terms": [ "wireless device" ] }, { "element_identifier": "2414", "terms": [ "first TRP" ] }, { "element_identifier": "2412", "terms": [ "second TRP" ] }, { "element_identifier": "2413", "terms": [ "moving vehicle" ] }, { "element_identifier": "2500", "terms": [ "At step" ] }, { "element_identifier": "2502", "terms": [ "BFR parameters. At step" ] }, { "element_identifier": "2504", "terms": [ "At step" ] }, { "element_identifier": "2506", "terms": [ "At step" ] }, { "element_identifier": "2508", "terms": [ "PUSCH resource. At step" ] }, { "element_identifier": "2510", "terms": [ "At step" ] }, { "element_identifier": "2514", "terms": [ "at step" ] }, { "element_identifier": "2600", "terms": [ "time T" ] }, { "element_identifier": "2602", "terms": [ "2T" ] }, { "element_identifier": "2606", "terms": [ "4T" ] }, { "element_identifier": "2608", "terms": [ "5T" ] }, { "element_identifier": "2610", "terms": [ "6T" ] }, { "element_identifier": "2604", "terms": [ "between time 3T" ] }, { "element_identifier": "64", "terms": [ "system may use" ] }, { "element_identifier": "8", "terms": [ "Approximately", "from" ] }, { "element_identifier": "3010", "terms": [ "base station" ] }, { "element_identifier": "3020", "terms": [ "wireless device" ] }, { "element_identifier": "256", "terms": [ "from" ] }, { "element_identifier": "3610", "terms": [ "base station" ] }, { "element_identifier": "3620", "terms": [ "device" ] }, { "element_identifier": "3710", "terms": [ "base station" ] }, { "element_identifier": "3720", "terms": [ "wireless device" ] }, { "element_identifier": "3810", "terms": [ "recovery procedure. At step" ] }, { "element_identifier": "3820", "terms": [ "step" ] }, { "element_identifier": "3830", "terms": [ "then at step" ] }, { "element_identifier": "3840", "terms": [ "then at step" ] }, { "element_identifier": "3910", "terms": [ "configuration procedure. At step" ] }, { "element_identifier": "3920", "terms": [ "preamble index. At step" ] }, { "element_identifier": "3930", "terms": [ "active cell. At step" ] }, { "element_identifier": "36", "terms": [ "clause" ] }, { "element_identifier": "39", "terms": [ "clauses", "clause" ] }, { "element_identifier": "63", "terms": [ "clauses", "clause" ] }, { "element_identifier": "84", "terms": [ "clause" ] }, { "element_identifier": "87", "terms": [ "clauses", "clause" ] }, { "element_identifier": "100", "terms": [ "random access channel resource.Clause" ] }, { "element_identifier": "103", "terms": [ "clause" ] }, { "element_identifier": "106", "terms": [ "clauses", "clause" ] }, { "element_identifier": "126", "terms": [ "clause" ] }, { "element_identifier": "129", "terms": [ "clauses", "clause" ] }, { "element_identifier": "149", "terms": [ "clause" ] }, { "element_identifier": "152", "terms": [ "clauses", "clause" ] }, { "element_identifier": "168", "terms": [ "clause" ] }, { "element_identifier": "171", "terms": [ "clauses", "clause" ] }, { "element_identifier": "207", "terms": [ "clause" ] }, { "element_identifier": "210", "terms": [ "clauses", "clause" ] }, { "element_identifier": "219", "terms": [ "clause" ] }, { "element_identifier": "222", "terms": [ "clauses", "clause" ] }, { "element_identifier": "4000", "terms": [ "computing device" ] }, { "element_identifier": "4001", "terms": [ "processor", "processors" ] }, { "element_identifier": "4004", "terms": [ "removable media" ] }, { "element_identifier": "4005", "terms": [ "hard drive" ] }, { "element_identifier": "4002", "terms": [ "ROM storage" ] }, { "element_identifier": "4003", "terms": [ "RAM" ] }, { "element_identifier": "4007", "terms": [ "output device controllers" ] }, { "element_identifier": "4009", "terms": [ "network interface" ] }, { "element_identifier": "4011", "terms": [ "GPS", "microprocessor" ] }, { "element_identifier": "4012", "terms": [ "Bluetooth interface" ] }, { "element_identifier": "4013", "terms": [ "WiFi interface" ] }, { "element_identifier": "4006", "terms": [ "display" ] }, { "element_identifier": "4008", "terms": [ "user input devices" ] }, { "element_identifier": "4010", "terms": [ "network" ] } ]

[ "5", "2", "3", "4", "94" ]

[ "FIG1" ]

[ "FIG1 shows an example radio access network (RAN) architecture" ]

[ "FIG1 shows an example Radio Access Network (RAN) architecture. A RAN node may comprise a next generation Node B (gNB) (e.g., 120A, 120B) providing New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g., 110A). A RAN node may comprise a base station such as a next generation evolved Node B (ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device (e.g., 110B). A first wireless device 110A may communicate with a base station, such as a gNB 120A, over a Uu interface. A second wireless device 110B may communicate with a base station, such as an ng-eNB 120D, over a Uu interface. The wireless devices 110A and/or 110B may be structurally similar to wireless devices shown in and/or described in connection with other drawing figures. The Node B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120D may be structurally similar to Nodes B and/or base stations shown in and/or described in connection with other drawing figures." ]

[ { "element_identifier": "9", "terms": [ "August" ] }, { "element_identifier": "1", "terms": [ "clauses", "clause" ] }, { "element_identifier": "2", "terms": [ "Octets", "Octet" ] }, { "element_identifier": "110", "terms": [ "wireless device", "wireless devices" ] }, { "element_identifier": "310", "terms": [ "communication interface" ] }, { "element_identifier": "314", "terms": [ "processor" ] }, { "element_identifier": "316", "terms": [ "program code instructions" ] }, { "element_identifier": "315", "terms": [ "stored in non-transitory memory" ] }, { "element_identifier": "311", "terms": [ "microphone" ] }, { "element_identifier": "312", "terms": [ "keypad" ] }, { "element_identifier": "313", "terms": [ "touchpad" ] }, { "element_identifier": "317", "terms": [ "power source" ] }, { "element_identifier": "318", "terms": [ "chipset" ] }, { "element_identifier": "319", "terms": [ "peripherals" ] }, { "element_identifier": "506", "terms": [ "uplink DM-RS" ] }, { "element_identifier": "503", "terms": [ "PUSCH" ] }, { "element_identifier": "504", "terms": [ "PUCCH" ] }, { "element_identifier": "507", "terms": [ "uplink PT-RS" ] }, { "element_identifier": "508", "terms": [ "SRS" ] }, { "element_identifier": "0", "terms": [ "BFR-RS-resource" ] }, { "element_identifier": "501", "terms": [ "UL-SCH" ] }, { "element_identifier": "502", "terms": [ "RACH" ] }, { "element_identifier": "505", "terms": [ "PRACH" ] }, { "element_identifier": "511", "terms": [ "DL-SCH" ] }, { "element_identifier": "512", "terms": [ "PCH" ] }, { "element_identifier": "513", "terms": [ "BCH" ] }, { "element_identifier": "509", "terms": [ "UCI" ] }, { "element_identifier": "517", "terms": [ "DCI" ] }, { "element_identifier": "515", "terms": [ "PDCCH" ] }, { "element_identifier": "522", "terms": [ "CSI-RS" ] }, { "element_identifier": "523", "terms": [ "downlink DM-RSs" ] }, { "element_identifier": "524", "terms": [ "PT-RS" ] }, { "element_identifier": "521", "terms": [ "PSS/SSS" ] }, { "element_identifier": "516", "terms": [ "PBCH" ] }, { "element_identifier": "32", "terms": [ "wireless device with", "less than" ] }, { "element_identifier": "514", "terms": [ "PDSCH" ] }, { "element_identifier": "12", "terms": [ "ADM-RS configuration may support", "slot may be", "may comprise" ] }, { "element_identifier": "601", "terms": [ "organized into radio frames" ] }, { "element_identifier": "10", "terms": [ "frame duration may be" ] }, { "element_identifier": "602", "terms": [ "ten equally sized subframes" ] }, { "element_identifier": "603", "terms": [ "slots" ] }, { "element_identifier": "15", "terms": [ "subframe with", "carrier is", "compliant with 3GPP Release" ] }, { "element_identifier": "604", "terms": [ "OFDM symbols" ] }, { "element_identifier": "14", "terms": [ "slot may be", "subframe may have" ] }, { "element_identifier": "700", "terms": [ "channel bandwidth" ] }, { "element_identifier": "701", "terms": [ "arrow" ] }, { "element_identifier": "702", "terms": [ "subcarrier spacing" ] }, { "element_identifier": "703", "terms": [ "subcarriers" ] }, { "element_identifier": "704", "terms": [ "guard bands" ] }, { "element_identifier": "705", "terms": [ "guard bands" ] }, { "element_identifier": "706", "terms": [ "subcarriers" ] }, { "element_identifier": "709", "terms": [ "first subcarrier spacing" ] }, { "element_identifier": "707", "terms": [ "subcarriers" ] }, { "element_identifier": "710", "terms": [ "second subcarrier spacing" ] }, { "element_identifier": "708", "terms": [ "subcarriers" ] }, { "element_identifier": "711", "terms": [ "third subcarrier spacing" ] }, { "element_identifier": "801", "terms": [ "transmission bandwidth" ] }, { "element_identifier": "802", "terms": [ "frequency domain" ] }, { "element_identifier": "803", "terms": [ "time domain" ] }, { "element_identifier": "805", "terms": [ "resource element" ] }, { "element_identifier": "807", "terms": [ "OFDM symbols" ] }, { "element_identifier": "28", "terms": [ "subframe may have" ] }, { "element_identifier": "30", "terms": [ "numerology is" ] }, { "element_identifier": "56", "terms": [ "subframe may have" ] }, { "element_identifier": "60", "terms": [ "numerology is", "clause" ] }, { "element_identifier": "806", "terms": [ "resource block" ] }, { "element_identifier": "940", "terms": [ "SS burst", "SS bursts" ] }, { "element_identifier": "950", "terms": [ "SS burst set" ] }, { "element_identifier": "120", "terms": [ "base station", "base stations" ] }, { "element_identifier": "910", "terms": [ "P1 procedure" ] }, { "element_identifier": "920", "terms": [ "P2 procedure" ] }, { "element_identifier": "930", "terms": [ "P3 procedure" ] }, { "element_identifier": "1010", "terms": [ "BWP1" ] }, { "element_identifier": "1050", "terms": [ "BWP1" ] }, { "element_identifier": "1020", "terms": [ "BWP2" ] }, { "element_identifier": "1040", "terms": [ "BWP2" ] }, { "element_identifier": "1030", "terms": [ "BWP3" ] }, { "element_identifier": "1130", "terms": [ "MN" ] }, { "element_identifier": "1150", "terms": [ "SN" ] }, { "element_identifier": "1110", "terms": [ "SDAP" ] }, { "element_identifier": "1111", "terms": [ "NR PDCP" ] }, { "element_identifier": "1114", "terms": [ "MN RLC" ] }, { "element_identifier": "1118", "terms": [ "MN MAC" ] }, { "element_identifier": "1112", "terms": [ "NR PDCP" ] }, { "element_identifier": "1115", "terms": [ "MN RLC" ] }, { "element_identifier": "1116", "terms": [ "SN RLC" ] }, { "element_identifier": "1119", "terms": [ "MAC" ] }, { "element_identifier": "1113", "terms": [ "NR PDCP" ] }, { "element_identifier": "1117", "terms": [ "SN RLC" ] }, { "element_identifier": "1120", "terms": [ "SDAP" ] }, { "element_identifier": "1140", "terms": [ "SDAP" ] }, { "element_identifier": "1121", "terms": [ "NR PDCP" ] }, { "element_identifier": "1142", "terms": [ "NR PDCP" ] }, { "element_identifier": "1124", "terms": [ "MN RLC" ] }, { "element_identifier": "1125", "terms": [ "MN RLC" ] }, { "element_identifier": "1128", "terms": [ "MN MAC" ] }, { "element_identifier": "1122", "terms": [ "NR PDCP" ] }, { "element_identifier": "1143", "terms": [ "NR PDCP" ] }, { "element_identifier": "1146", "terms": [ "SN RLC" ] }, { "element_identifier": "1147", "terms": [ "SN RLC" ] }, { "element_identifier": "1148", "terms": [ "SN MAC" ] }, { "element_identifier": "1123", "terms": [ "NR PDCP" ] }, { "element_identifier": "1141", "terms": [ "NR PDCP" ] }, { "element_identifier": "1126", "terms": [ "MN RLC" ] }, { "element_identifier": "1144", "terms": [ "SN RLC" ] }, { "element_identifier": "1145", "terms": [ "SN RLC" ] }, { "element_identifier": "1127", "terms": [ "MN RLC" ] }, { "element_identifier": "1230", "terms": [ "Msg2" ] }, { "element_identifier": "1240", "terms": [ "Msg3" ] }, { "element_identifier": "1250", "terms": [ "contention resolution" ] }, { "element_identifier": "3", "terms": [ "Msg" ] }, { "element_identifier": "1220", "terms": [ "Msg1" ] }, { "element_identifier": "1210", "terms": [ "RACH configuration" ] }, { "element_identifier": "1355", "terms": [ "Control" ] }, { "element_identifier": "1365", "terms": [ "Control" ] }, { "element_identifier": "1352", "terms": [ "Multiplexing" ] }, { "element_identifier": "1362", "terms": [ "Multiplexing" ] }, { "element_identifier": "1351", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1361", "terms": [ "Logical Channel Prioritization" ] }, { "element_identifier": "1354", "terms": [ "Random Access Control" ] }, { "element_identifier": "1364", "terms": [ "Random Access Control" ] }, { "element_identifier": "1530", "terms": [ "RRC Connected" ] }, { "element_identifier": "1510", "terms": [ "RRC Idle" ] }, { "element_identifier": "1520", "terms": [ "RRC Inactive" ] }, { "element_identifier": "1540", "terms": [ "connection release" ] }, { "element_identifier": "1570", "terms": [ "connection inactivation" ] }, { "element_identifier": "1580", "terms": [ "connection resume" ] }, { "element_identifier": "1560", "terms": [ "connection release" ] }, { "element_identifier": "111011", "terms": [ "LCID with" ] }, { "element_identifier": "31", "terms": [ "maycomprise four octets comprising" ] }, { "element_identifier": "2402", "terms": [ "base station" ] }, { "element_identifier": "2401", "terms": [ "wireless device" ] }, { "element_identifier": "2403", "terms": [ "moving vehicle" ] }, { "element_identifier": "2411", "terms": [ "wireless device" ] }, { "element_identifier": "2414", "terms": [ "first TRP" ] }, { "element_identifier": "2412", "terms": [ "second TRP" ] }, { "element_identifier": "2413", "terms": [ "moving vehicle" ] }, { "element_identifier": "2500", "terms": [ "At step" ] }, { "element_identifier": "2502", "terms": [ "BFR parameters. At step" ] }, { "element_identifier": "2504", "terms": [ "At step" ] }, { "element_identifier": "2506", "terms": [ "At step" ] }, { "element_identifier": "2508", "terms": [ "PUSCH resource. At step" ] }, { "element_identifier": "2510", "terms": [ "At step" ] }, { "element_identifier": "2514", "terms": [ "at step" ] }, { "element_identifier": "2600", "terms": [ "time T" ] }, { "element_identifier": "2602", "terms": [ "2T" ] }, { "element_identifier": "2606", "terms": [ "4T" ] }, { "element_identifier": "2608", "terms": [ "5T" ] }, { "element_identifier": "2610", "terms": [ "6T" ] }, { "element_identifier": "2604", "terms": [ "between time 3T" ] }, { "element_identifier": "64", "terms": [ "system may use" ] }, { "element_identifier": "8", "terms": [ "Approximately", "from" ] }, { "element_identifier": "3010", "terms": [ "base station" ] }, { "element_identifier": "3020", "terms": [ "wireless device" ] }, { "element_identifier": "256", "terms": [ "from" ] }, { "element_identifier": "3610", "terms": [ "base station" ] }, { "element_identifier": "3620", "terms": [ "device" ] }, { "element_identifier": "3710", "terms": [ "base station" ] }, { "element_identifier": "3720", "terms": [ "wireless device" ] }, { "element_identifier": "3810", "terms": [ "recovery procedure. At step" ] }, { "element_identifier": "3820", "terms": [ "step" ] }, { "element_identifier": "3830", "terms": [ "then at step" ] }, { "element_identifier": "3840", "terms": [ "then at step" ] }, { "element_identifier": "3910", "terms": [ "configuration procedure. At step" ] }, { "element_identifier": "3920", "terms": [ "preamble index. At step" ] }, { "element_identifier": "3930", "terms": [ "active cell. At step" ] }, { "element_identifier": "36", "terms": [ "clause" ] }, { "element_identifier": "39", "terms": [ "clauses", "clause" ] }, { "element_identifier": "63", "terms": [ "clauses", "clause" ] }, { "element_identifier": "84", "terms": [ "clause" ] }, { "element_identifier": "87", "terms": [ "clauses", "clause" ] }, { "element_identifier": "100", "terms": [ "random access channel resource.Clause" ] }, { "element_identifier": "103", "terms": [ "clause" ] }, { "element_identifier": "106", "terms": [ "clauses", "clause" ] }, { "element_identifier": "126", "terms": [ "clause" ] }, { "element_identifier": "129", "terms": [ "clauses", "clause" ] }, { "element_identifier": "149", "terms": [ "clause" ] }, { "element_identifier": "152", "terms": [ "clauses", "clause" ] }, { "element_identifier": "168", "terms": [ "clause" ] }, { "element_identifier": "171", "terms": [ "clauses", "clause" ] }, { "element_identifier": "207", "terms": [ "clause" ] }, { "element_identifier": "210", "terms": [ "clauses", "clause" ] }, { "element_identifier": "219", "terms": [ "clause" ] }, { "element_identifier": "222", "terms": [ "clauses", "clause" ] }, { "element_identifier": "4000", "terms": [ "computing device" ] }, { "element_identifier": "4001", "terms": [ "processor", "processors" ] }, { "element_identifier": "4004", "terms": [ "removable media" ] }, { "element_identifier": "4005", "terms": [ "hard drive" ] }, { "element_identifier": "4002", "terms": [ "ROM storage" ] }, { "element_identifier": "4003", "terms": [ "RAM" ] }, { "element_identifier": "4007", "terms": [ "output device controllers" ] }, { "element_identifier": "4009", "terms": [ "network interface" ] }, { "element_identifier": "4011", "terms": [ "GPS", "microprocessor" ] }, { "element_identifier": "4012", "terms": [ "Bluetooth interface" ] }, { "element_identifier": "4013", "terms": [ "WiFi interface" ] }, { "element_identifier": "4006", "terms": [ "display" ] }, { "element_identifier": "4008", "terms": [ "user input devices" ] }, { "element_identifier": "4010", "terms": [ "network" ] } ]

[ "74", "1" ]

[ "FIG10" ]

[ "FIG10 shows another example of a bearer type change procedure according to an embodiment of the present disclosure" ]

[ "FIG10 shows another example of a bearer type change procedure according to an embodiment of the present disclosure. FIG10 shows a bearer type change procedure, triggered by an MN, from an SCG bearer to an SCG split bearer or a bearer type change procedure, triggered by an MN, from an MCG bearer/MCG split bearer to an SCG bearer/SCG split bearer. Through the resource status reporting mechanism exchanged between the MN and the SN, when the MN finds that the SN load is getting higher or near the limit, the MN may initiate a bearer type change procedure that splits the SCG bearer into the SCG split bearer. Accordingly, the MN may preemptively reduce an SN load. Alternatively, the MN may initiate a bearer type change procedure from the MCG bearer/MCG split bearer to the SCG bearer/SCG split bearer. In the foregoing description, the MN may be either an eNB or a gNB, and the SN may be a gNB." ]

[ { "element_identifier": "1", "terms": [ "RAN node", "Table" ] }, { "element_identifier": "2", "terms": [ "RAN node" ] }, { "element_identifier": "10", "terms": [ "UE" ] }, { "element_identifier": "20", "terms": [ "eNB", "eNBs" ] }, { "element_identifier": "30", "terms": [ "MME/S-GW" ] }, { "element_identifier": "3", "terms": [ "as option" ] }, { "element_identifier": "3a", "terms": [ "as option" ] }, { "element_identifier": "3x", "terms": [ "as option" ] }, { "element_identifier": "4", "terms": [ "as option" ] }, { "element_identifier": "4a", "terms": [ "as option" ] }, { "element_identifier": "7", "terms": [ "as option" ] }, { "element_identifier": "7a", "terms": [ "as option" ] }, { "element_identifier": "7x", "terms": [ "as option" ] }, { "element_identifier": "1500", "terms": [ "first RAN node" ] }, { "element_identifier": "1510", "terms": [ "processor" ] }, { "element_identifier": "1520", "terms": [ "memory" ] }, { "element_identifier": "1530", "terms": [ "transceiver" ] }, { "element_identifier": "1600", "terms": [ "second RAN node" ] }, { "element_identifier": "1610", "terms": [ "processor" ] }, { "element_identifier": "1620", "terms": [ "memory" ] }, { "element_identifier": "1630", "terms": [ "transceiver" ] }, { "element_identifier": "1511", "terms": [ "layer" ] }, { "element_identifier": "1512", "terms": [ "layer" ] }, { "element_identifier": "1513", "terms": [ "layer" ] }, { "element_identifier": "1514", "terms": [ "data connection layer" ] }, { "element_identifier": "1515", "terms": [ "physical layer" ] }, { "element_identifier": "1611", "terms": [ "X2-AP layer" ] }, { "element_identifier": "1612", "terms": [ "SCTP layer" ] }, { "element_identifier": "1613", "terms": [ "IP layer" ] }, { "element_identifier": "1614", "terms": [ "data connection layer" ] }, { "element_identifier": "1615", "terms": [ "physical layer" ] } ]

[ "10", "23" ]

[ "FIG11" ]

[ "FIG11 shows another example of a bearer type change procedure according to an embodiment of the present disclosure" ]

[ "FIG11 shows another example of a bearer type change procedure according to an embodiment of the present disclosure. FIG11 shows a bearer type change procedure, triggered by an SN, from an SCG split bearer to an SCG bearer. When the SN determines that an overload status thereof has been resolved or is no longer severe, the SN may initiate a bearer type change procedure that turns back the SCG split bearer to the SCG bearer. In the foregoing description, the MN may be either an eNB or a gNB, and the SN may be a gNB." ]

[ { "element_identifier": "1", "terms": [ "RAN node", "Table" ] }, { "element_identifier": "2", "terms": [ "RAN node" ] }, { "element_identifier": "10", "terms": [ "UE" ] }, { "element_identifier": "20", "terms": [ "eNB", "eNBs" ] }, { "element_identifier": "30", "terms": [ "MME/S-GW" ] }, { "element_identifier": "3", "terms": [ "as option" ] }, { "element_identifier": "3a", "terms": [ "as option" ] }, { "element_identifier": "3x", "terms": [ "as option" ] }, { "element_identifier": "4", "terms": [ "as option" ] }, { "element_identifier": "4a", "terms": [ "as option" ] }, { "element_identifier": "7", "terms": [ "as option" ] }, { "element_identifier": "7a", "terms": [ "as option" ] }, { "element_identifier": "7x", "terms": [ "as option" ] }, { "element_identifier": "1500", "terms": [ "first RAN node" ] }, { "element_identifier": "1510", "terms": [ "processor" ] }, { "element_identifier": "1520", "terms": [ "memory" ] }, { "element_identifier": "1530", "terms": [ "transceiver" ] }, { "element_identifier": "1600", "terms": [ "second RAN node" ] }, { "element_identifier": "1610", "terms": [ "processor" ] }, { "element_identifier": "1620", "terms": [ "memory" ] }, { "element_identifier": "1630", "terms": [ "transceiver" ] }, { "element_identifier": "1511", "terms": [ "layer" ] }, { "element_identifier": "1512", "terms": [ "layer" ] }, { "element_identifier": "1513", "terms": [ "layer" ] }, { "element_identifier": "1514", "terms": [ "data connection layer" ] }, { "element_identifier": "1515", "terms": [ "physical layer" ] }, { "element_identifier": "1611", "terms": [ "X2-AP layer" ] }, { "element_identifier": "1612", "terms": [ "SCTP layer" ] }, { "element_identifier": "1613", "terms": [ "IP layer" ] }, { "element_identifier": "1614", "terms": [ "data connection layer" ] }, { "element_identifier": "1615", "terms": [ "physical layer" ] } ]

[ "11", "24" ]

[ "FIG2" ]

[ "FIG2 is a conceptual diagram illustrating an L2 structure and function of the LTE/LTE-A UE" ]

[ "FIG2 is a conceptual diagram illustrating an L2 structure and function of the LTE/LTE-A UE. The L2 layer may be divided into a Medium Access Control (MAC) sublayer, a Radio Link Control (RLC) sublayer, and a Packet Data Convergence Protocol (PDCP) sublayer. The Service Access Point (SAP) for peer-to-peer communication is an interface between sublayers as represented by a circle. The PDCP sublayer is responsible for compression/decompression of the IP Header of an Internet Protocol (IP) packet received from an upper layer using a Robust Header Compression (RoHC) protocol and for ciphering/deciphering and integrity check on the packet to be transmitted through the radio interface.", "In the case of the 3GPP network-based service/application data, the IP packet from the upper layer is transferred to the physical layer via the PDCP sublayer, RLC sublayer, and MAC sublayer so as to be transmitted through the UL-SCH as a physical channel; and the transport block received through the DL-SCH as a physical channel is delivered to the corresponding upper layer via the MAC sublayer, RLC sublayer, and PDCP sublayer in the form of an IP packet. The operations of the PDCP sublayer, RLC sublayer, and MAC sublayer on the paths 401 and 411 have been described with reference to FIG2." ]

[ { "element_identifier": "2", "terms": [ "logical channel group" ] } ]

[ "2", "16" ]

[ "FIG3" ]

[ "FIG3 is a diagram illustrating D2D communication in a cellular system" ]

[ "FIG3 is a diagram illustrating D2D communication in a cellular system. Referring to FIG3, the eNB 301 serves the UEs 303 and 304 located within the cell 302. The UE 303 is capable of performing cellular communication through the eNB 301 and the UE-eNB link 306. Also, the terminal 304 is capable of performing cellular communication through the UE-eNB link 307. If both the UEs 303 and 304 support D2D communication, they can exchange information directly through the D2D link 305 without involvement of the eNB 301." ]

[ { "element_identifier": "307", "terms": [ "UE-eNB link" ] }, { "element_identifier": "306", "terms": [ "UE-eNB link" ] }, { "element_identifier": "304", "terms": [ "UEs" ] }, { "element_identifier": "303", "terms": [ "UEs" ] }, { "element_identifier": "302", "terms": [ "cell" ] }, { "element_identifier": "3", "terms": [ "logical channel group" ] }, { "element_identifier": "305", "terms": [ "D2D link" ] } ]

[ "3", "302", "303", "306", "305", "304", "30", "307", "17" ]

[ "FIG8" ]

[ "FIG8 is a flowchart illustrating a multiplexing operation of the UE supporting D2D-communicaiton according to an embodiment of the present invention" ]

[ "FIG8 is a flowchart illustrating a multiplexing operation of the UE supporting D2D-communicaiton according to an embodiment of the present invention. If the multiplexing operation is initiated on the MAC sublayer at step 801, the UE determines whether the corresponding transport block is to be transmitted through the D2D link at step 811. The multiplexing is the operation of processing the Tx packets received through a plurality of logical channels to generate a transport block as transmission unit so as to be fit for the allocated/selected radio resources." ]

[ { "element_identifier": "105", "terms": [ "eNBs" ] }, { "element_identifier": "130", "terms": [ "S-GW" ] }, { "element_identifier": "135", "terms": [ "UE" ] }, { "element_identifier": "125", "terms": [ "MME" ] }, { "element_identifier": "301", "terms": [ "eNB" ] }, { "element_identifier": "303", "terms": [ "UEs" ] }, { "element_identifier": "304", "terms": [ "UEs" ] }, { "element_identifier": "302", "terms": [ "cell" ] }, { "element_identifier": "306", "terms": [ "UE-eNB link" ] }, { "element_identifier": "307", "terms": [ "UE-eNB link" ] }, { "element_identifier": "305", "terms": [ "D2D link" ] }, { "element_identifier": "401", "terms": [ "reference number", "paths" ] }, { "element_identifier": "411", "terms": [ "reference number", "paths" ] }, { "element_identifier": "421", "terms": [ "reference numbers", "reference number" ] }, { "element_identifier": "431", "terms": [ "reference numbers", "reference number" ] }, { "element_identifier": "441", "terms": [ "reference numbers" ] }, { "element_identifier": "451", "terms": [ "reference numbers" ] }, { "element_identifier": "501", "terms": [ "higher sublayer at step" ] }, { "element_identifier": "511", "terms": [ "step" ] }, { "element_identifier": "521", "terms": [ "steps", "step" ] }, { "element_identifier": "551", "terms": [ "step", "steps" ] }, { "element_identifier": "525", "terms": [ "at step" ] }, { "element_identifier": "531", "terms": [ "step" ] }, { "element_identifier": "536", "terms": [ "at step" ] }, { "element_identifier": "533", "terms": [ "standard specification at step" ] }, { "element_identifier": "541", "terms": [ "step" ] }, { "element_identifier": "539", "terms": [ "release at step" ] }, { "element_identifier": "543", "terms": [ "step" ] }, { "element_identifier": "553", "terms": [ "timer T2 at step" ] }, { "element_identifier": "561", "terms": [ "timer T2 at step" ] }, { "element_identifier": "563", "terms": [ "timer T2 at step" ] }, { "element_identifier": "566", "terms": [ "step" ] }, { "element_identifier": "546", "terms": [ "step" ] }, { "element_identifier": "621", "terms": [ "MAC CE" ] }, { "element_identifier": "601", "terms": [ "MAC sub-header" ] }, { "element_identifier": "611", "terms": [ "part" ] }, { "element_identifier": "631", "terms": [ "network. Reference numbers" ] }, { "element_identifier": "641", "terms": [ "network. Reference numbers" ] }, { "element_identifier": "651", "terms": [ "Reference numbers", "D2D-combined BSR MAC CE" ] }, { "element_identifier": "661", "terms": [ "Reference numbers", "D2D-combined BSR MAC CE" ] }, { "element_identifier": "701", "terms": [ "network. Steps" ] }, { "element_identifier": "711", "terms": [ "at step" ] }, { "element_identifier": "751", "terms": [ "buffer size at step" ] }, { "element_identifier": "721", "terms": [ "at step" ] }, { "element_identifier": "731", "terms": [ "At step" ] }, { "element_identifier": "741", "terms": [ "MAC CE at step" ] }, { "element_identifier": "761", "terms": [ "triggered at step" ] }, { "element_identifier": "771", "terms": [ "at step" ] }, { "element_identifier": "781", "terms": [ "at step", "at steps" ] }, { "element_identifier": "786", "terms": [ "at step", "at steps" ] }, { "element_identifier": "791", "terms": [ "At step" ] }, { "element_identifier": "795", "terms": [ "At step" ] }, { "element_identifier": "0", "terms": [ "four logical channel groups" ] }, { "element_identifier": "1", "terms": [ "logical channel group" ] }, { "element_identifier": "2", "terms": [ "logical channel group" ] }, { "element_identifier": "3", "terms": [ "logical channel group" ] }, { "element_identifier": "801", "terms": [ "MAC sublayer at step" ] }, { "element_identifier": "811", "terms": [ "D2D link at step" ] }, { "element_identifier": "821", "terms": [ "at step" ] }, { "element_identifier": "831", "terms": [ "logical channels at step" ] }, { "element_identifier": "901", "terms": [ "at step" ] }, { "element_identifier": "911", "terms": [ "timer T3 at step" ] }, { "element_identifier": "921", "terms": [ "D2D link at step" ] }, { "element_identifier": "931", "terms": [ "D2D link at step" ] }, { "element_identifier": "935", "terms": [ "data at step" ] }, { "element_identifier": "941", "terms": [ "at step" ] }, { "element_identifier": "951", "terms": [ "at step" ] }, { "element_identifier": "961", "terms": [ "3GPP network at step" ] }, { "element_identifier": "963", "terms": [ "sub-layer signaling at step" ] }, { "element_identifier": "965", "terms": [ "allocated semi-persistently at step" ] }, { "element_identifier": "967", "terms": [ "other sTAGs at step" ] }, { "element_identifier": "971", "terms": [ "D2D link at step" ] }, { "element_identifier": "973", "terms": [ "data at step" ] }, { "element_identifier": "975", "terms": [ "network at step" ] }, { "element_identifier": "981", "terms": [ "at step" ] }, { "element_identifier": "983", "terms": [ "sub-layer signaling at step" ] }, { "element_identifier": "991", "terms": [ "D2D link at step" ] }, { "element_identifier": "993", "terms": [ "data at step" ] }, { "element_identifier": "995", "terms": [ "TAG at step" ] }, { "element_identifier": "101", "terms": [ "transceiver" ] }, { "element_identifier": "1030", "terms": [ "controller" ] }, { "element_identifier": "1010", "terms": [ "transceiver" ] }, { "element_identifier": "1031", "terms": [ "control unit" ] }, { "element_identifier": "1032", "terms": [ "control unit" ] }, { "element_identifier": "1033", "terms": [ "control unit" ] }, { "element_identifier": "1301", "terms": [ "SR control unit" ] }, { "element_identifier": "1110", "terms": [ "UE at step" ] }, { "element_identifier": "1120", "terms": [ "upper layer at step" ] }, { "element_identifier": "1130", "terms": [ "at step" ] }, { "element_identifier": "1140", "terms": [ "step" ] }, { "element_identifier": "1150", "terms": [ "logical channel. At step" ] } ]

[ "8", "801", "811", "831", "23" ]

[ "FIG1" ]

[ "FIG1 is a conceptual diagram illustrating the 3GPP system architecture to which the present invention is applied" ]

[ "FIG1 is a conceptual diagram illustrating the architecture of an LTE system to which the present invention is applied. Referring to FIG1, a Radio Access Network of the LTE system includes evolved Node Bs (eNBs) 105, 110, 115, and 120, a Mobility Management Entity (MME) 125, and a Serving-Gateway (S-GW) 130. The User Equipment (hereinafter, referred to as UE) 135 connects to an external network via the eNBs 105, 110, 115, and 120 and the S-GW 130. The eNBs 105, 110, 115, and 120 correspond to the legacy node Bs of the UMTS system. The eNBs 105, 110, 115, and 120 allow the UE 135 to establish a radio channel and are responsible for functions more complicated as compared to the legacy node B. In the LTE system, all the user traffic services including real time services such as Voice over Internet Protocol (VoIP) are provided through a shared channel and thus there is a need of a device to schedule data based on the state information (such as buffer status, power headroom status, and channel condition of the UE), the eNBs 105, 110, 115, and 120 being responsible for such functions. Typically, one eNB controls a plurality of cells. In order to secure the data rate of up to 100Mbps, the LTE system adopts Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology in up to 20 MHz bandwidth. Also, the LTE system adopts Adaptive Modulation and Coding (AMC) to determine the modulation scheme and channel coding rate in adaptation to the channel condition of the UE. The S-GW 130 is an entity to provide data bearers so as to establish and release data bearers under the control of the MME 125. The MME 125 is responsible for mobility management of UEs and various control functions and may be connected to a plurality of eNBs." ]

[ { "element_identifier": "1", "terms": [ "logical channel group" ] }, { "element_identifier": "130", "terms": [ "S-GW" ] }, { "element_identifier": "105", "terms": [ "eNBs" ] }, { "element_identifier": "125", "terms": [ "MME" ] }, { "element_identifier": "135", "terms": [ "UE" ] } ]

[ "1", "125", "130", "105", "110", "115", "120", "135", "15" ]

[ "FIG3" ]

[ "FIG3 is a schematic structural diagram of an IoT cloud platform according to an embodiment of the present invention" ]

[ "FIG3 is a schematic structural diagram of an IoT cloud platform according to this embodiment.", "Certainly, FIG3 is merely an example. In other embodiments, the cloud platform may be a set of a plurality of servers shown in FIG3." ]

[ { "element_identifier": "201", "terms": [ "memory" ] }, { "element_identifier": "202", "terms": [ "processors" ] }, { "element_identifier": "2", "terms": [ "value is" ] }, { "element_identifier": "301", "terms": [ "memory" ] }, { "element_identifier": "302", "terms": [ "processors" ] }, { "element_identifier": "300", "terms": [ "IoT cloud platform" ] }, { "element_identifier": "3", "terms": [ "most significant byte is" ] }, { "element_identifier": "200", "terms": [ "NB-IoT device" ] } ]

[ "200", "201", "202", "2", "300", "301", "302", "3", "15" ]

[ "FIG7" ]

[ "FIG7 is a schematic diagram of an application message in a session resumption method according to an embodiment of the present invention" ]

[ "Specifically, as shown in FIG7, a format of the encrypted application message sent by the NB-IoT device to the IoT cloud platform includes two parts: A first part is an N-byte current session identifier in plaintext, and the current session identifier is included in the record layer of DTLS. A second part is a ciphertext and includes service data that needs to be uploaded. The current session identifier is a new session identifier. After receiving the encrypted application message, the IoT cloud platform obtains the current session identifier by parsing information in the record layer, identifies an identity of the NB-IoT device by using the current session identifier, finds the session that is corresponding to the current session identifier and that is obtained through negotiation in the current handshake, decrypts the second part by using the negotiated key in the content of the session, and reports the decrypted service data to an upper-layer protocol." ]

[ { "element_identifier": "801", "terms": [ "transceiver unit" ] }, { "element_identifier": "9", "terms": [ "andFIG." ] }, { "element_identifier": "802", "terms": [ "storage unit" ] }, { "element_identifier": "800", "terms": [ "apparatus" ] }, { "element_identifier": "803", "terms": [ "unit" ] } ]

[ "9", "7", "800", "801", "803", "802", "00", "18" ]

[ "FIG6" ]

[ "FIG6 is a schematic diagram of content of a request message in a session resumption method according to an embodiment of the present invention" ]

[ "As shown in FIG6, content of the client_hello with session_renewal request message includes two parts. A first part is an N-byte session identifier in plaintext, and the identifier is included in a record layer of DTLS and is used by the IoT cloud platform to find, based on the session identifier, a session previously set up with the NB-IoT device. After decrypting a ciphertext in a second part by using a negotiated key in content of the session, the IoT cloud platform replies to the request message." ]

[ { "element_identifier": "900", "terms": [ "server" ] }, { "element_identifier": "903", "terms": [ "processing unit" ] }, { "element_identifier": "902", "terms": [ "unit" ] }, { "element_identifier": "901", "terms": [ "transceiver unit" ] } ]

[ "900", "901", "903", "902", "6", "19" ]

[ "FIG3" ]

[ "FIG3 is a circuit diagram of a working coil and power module of an induction heating device according to an embodiment" ]

[ "FIG3 is a circuit diagram of a working coil and power module of an induction heating device according to an embodiment.", "Referring to FIG3, the induction heating device according to an embodiment includes two power modules, i.e., a first power module 202 and a second power module 204. The first power module 202 and the second power module 204 convert alternating current power supplied by an external power source 30 into power for driving, and supply the power for driving to the first working coil 102, the second working coil 104, and the third working coil 106a, 106b respectively." ]

[ { "element_identifier": "202", "terms": [ "first power module" ] }, { "element_identifier": "30", "terms": [ "external power source" ] }, { "element_identifier": "306", "terms": [ "rectifying unit" ] }, { "element_identifier": "304", "terms": [ "smoothing unit" ] }, { "element_identifier": "204", "terms": [ "second power module" ] }, { "element_identifier": "104", "terms": [ "second working coil" ] }, { "element_identifier": "302", "terms": [ "rectifying unit" ] }, { "element_identifier": "308", "terms": [ "smoothing unit" ] }, { "element_identifier": "102", "terms": [ "first working coil" ] }, { "element_identifier": "3", "terms": [ "is" ] }, { "element_identifier": "32", "terms": [ "control unit" ] } ]

[ "3", "202", "302", "304", "30", "102", "104", "306", "308", "204", "32", "13" ]

[ "FIG2" ]

[ "FIG2 is a plan view illustrating an arrangement of a working coil included in an induction heating device according to an embodiment" ]

[ "FIG2 is a plan view illustrating an arrangement of a working coil included in an induction heating device according to an embodiment.", "Referring to FIG2, the induction heating device 10 according to an embodiment includes a first working coil 102, a second working coil 104, and a third working coil 106a, 106b.", "As illustrated in FIG2, the central point of the first working coil 102 and the central point of the second working coil 104 may be placed on the same straight line. The central point of the third working coil 106a, 106b may be placed on a straight line perpendicular to the straight line that connects the central point of the first working coil 102 and the central point of the second working coil 104. Accordingly, the third working coil 106a, 106b may be disposed on the right-side surface or the left-side surface with respect to the straight line that connects the central point of the first working coil 102 and the central point of the second working coil 104.", "Referring back to FIG2, the induction heating device 10 according to an embodiment includes a first power module 202 and a second power module 204 that supply power for driving the first working coil 102, the second working coil 104 and the third working coil 106a, 106b.", "As illustrated in FIG2, the first power module 202 is electrically connected with the first working coil 102 and the inner coil 106a. Accordingly, the first power module 202 supplies power for driving to at least one of the first working coil 102 and the inner coil 106a." ]

[ { "element_identifier": "202", "terms": [ "first power module" ] }, { "element_identifier": "142", "terms": [ "first heating area" ] }, { "element_identifier": "204", "terms": [ "second power module" ] }, { "element_identifier": "104", "terms": [ "second working coil" ] }, { "element_identifier": "118", "terms": [ "operation area" ] }, { "element_identifier": "102", "terms": [ "first working coil" ] }, { "element_identifier": "10", "terms": [ "induction heating device" ] }, { "element_identifier": "108", "terms": [ "interface unit" ] }, { "element_identifier": "106", "terms": [ "upper plate" ] }, { "element_identifier": "144", "terms": [ "second heating area" ] }, { "element_identifier": "146", "terms": [ "third heating area" ] } ]

[ "144", "142", "146", "106", "102", "104", "118", "102", "10", "108", "102", "202", "204", "12" ]

[ "FIG2" ]

[ "FIG2 shows an exemplary mixed spectrum corresponding to a weighted combination of five different types of LEDs, each having an emission spectrum, where the value of all the weights is 1" ]

[ "Calculating a plurality of mixed spectra 4, each being a weighted combination of said individual emission spectra of said plurality of light sources 2. An example of a mixed spectrum 4 is shown if FIG2. In this case is an equal-weighted combination of the five LED types.For each mixed spectra 4 of said plurality of mixed spectra 4, calculating its colour coordinates: u' and v' for the example with CIELUV. Also calculating its optimization parameter, which in this example is Rf.Partitioning in sectors a modelling region 5 of said colour space. The example uses a grid of rectangular sectors in the CIELUV colour space. In the example, the modelling region 5 contains the target region 7.For each sector, selecting an optimized spectrum as the mixed spectrum contained in said sector having the best optimization parameter; thus obtaining an optimized weighted combination for said colour sector, as the weighted combination of said optimized mixed spectrum. Therefore, for the example, for each sector it will be selected the mixed spectrum having a higher Rf value calculated in the previous step. In the case that a particular sector in the modelling region 5 does not contain any suitable mixed spectrum, the exemplary embodiment has an interpolation step to provide one interpolated mixed spectrum based on its neighbouring sectors.Using the optimized weighted combination of each of said sectors, establishing a correspondence between colour coordinates and weighted combinations for the target region 7 of the colour space.Thus obtaining said output model 3." ]

[ { "element_identifier": "400", "terms": [ "emission wavelength between", "time information" ] }, { "element_identifier": "2", "terms": [ "light sources", "light source" ] }, { "element_identifier": "600", "terms": [ "emission wavelength between" ] }, { "element_identifier": "500", "terms": [ "sensor module" ] }, { "element_identifier": "700", "terms": [ "emission wavelength between" ] } ]

[ "23", "400", "450", "500", "550", "2", "600", "650", "700", "750" ]

[ "FIG2", " FIG3" ]

[ "FIG3 is a circuit diagram showing a configuration example of an LED circuit (lighting circuit) shown in FIG1 ", "FIG2 shows lighting patterns of LED circuits according to one embodiment" ]

[ "FIG3 is a circuit diagram showing a configuration example of LED circuit 12 (lighting circuit) shown in FIG1. With reference to FIG3, LED circuit 12 includes a diode 50, Zener diodes 51, 52, 53, 54, resistors 61, 62, 63, 64, and LEDs 71, 72, 73, 74. ", "FIG2 shows lighting patterns of the LED circuits according to one embodiment. In FIG2, \"input 1\", \"input 2\", and \"output 1\" respectively represent LED circuit 12, LED circuit 13, and LED circuit 31. Each of LED circuits 12, 13, 31 has two states, ON and OFF, and therefore there are 2 × 2 × 2 = 8 patterns in total. FIG2 describes all possible lighting patterns.", "In an embodiment, the lighting mode of LED circuit 12 is varied depending on the input voltage of power supply device 100. Thus, in patterns 1 to 4 shown in FIG2 (i.e., the patterns in which \"input 1\" is ON), the lighting mode of LED circuit 12 is varied depending on the input voltage of power supply device 100. This enables the user to check whether or not an intended input voltage is being applied to power supply device 100. Thus, a power supply device that enables the user to easily check the level of input voltage can be provided." ]

[ { "element_identifier": "8", "terms": [ "example. Pattern" ] }, { "element_identifier": "7", "terms": [ "this pattern. Pattern" ] }, { "element_identifier": "5", "terms": [ "Pattern" ] }, { "element_identifier": "12", "terms": [ "circuit", "circuits" ] }, { "element_identifier": "73", "terms": [ "LED" ] }, { "element_identifier": "1", "terms": [ "input" ] }, { "element_identifier": "2", "terms": [ "input" ] }, { "element_identifier": "4", "terms": [ "Pattern" ] }, { "element_identifier": "50", "terms": [ "diode" ] }, { "element_identifier": "3", "terms": [ "Pattern" ] } ]

[ "2", "1", "2", "3", "4", "5", "6", "7", "8", "50", "12", "73" ]

[ "FIG4" ]

[ "FIG4 schematically shows one example external appearance of a power supply device according to an embodiment of the present invention " ]

[ "FIG4 schematically shows one example external appearance of power supply device 100 according to an embodiment of the present invention. As shown in FIG4, on the face of power supply device 100 where INPUT terminals and DC-OUTPUT terminals are disposed, display circuits 81a to 81f, LED circuit 12 (LEDs 71 to 74), a display switching/resetting key 82, a communication port 83, and an output voltage adjusting trimmer 84 are placed. The layout shown in FIG4 is by way of example.", "The power supply device shown in FIG4 is disposed on a control board at a manufacturing location, for example. At a manufacturing location, interconnections (power-supply lines) for different power-supply voltages may be laid. If a power supply device meant for a certain power-supply line (e.g. a line for AC of 230 V) is connected to a power-supply line for a lower voltage (e.g. a line for AC of 115 V), the output or efficiency of the power supply device may reduce." ]

[ { "element_identifier": "8", "terms": [ "example. Pattern" ] }, { "element_identifier": "72", "terms": [ "LED" ] }, { "element_identifier": "83", "terms": [ "communication port" ] }, { "element_identifier": "12", "terms": [ "circuit", "circuits" ] }, { "element_identifier": "73", "terms": [ "LED" ] }, { "element_identifier": "100", "terms": [ "power supply device" ] }, { "element_identifier": "84", "terms": [ "output voltage adjusting trimmer" ] }, { "element_identifier": "82", "terms": [ "display switching/resetting key" ] }, { "element_identifier": "74", "terms": [ "LED" ] }, { "element_identifier": "71", "terms": [ "LEDs" ] } ]

[ "100", "74", "73", "12", "72", "71", "84", "82", "83", "8" ]

[ "FIG1" ]

[ "FIG1 is a block diagram showing one configuration example of a power supply device according to an embodiment" ]

[ "First of all, one example situation to which the present invention is applicable is described with reference to FIG1. FIG1 is a block diagram showing one configuration example of a power supply device 100 according to an embodiment. As shown in FIG1, power supply device 100 is, for example, a switching power supply device. Power supply device 100 includes an input unit 10 to receive an input voltage from outside, a power supply unit 20, and an output unit 30.", "Output unit 30 includes output terminals 32, 33. The power-supply voltage generated in power supply unit 20 is outputted from output terminals 32, 33 (also denoted by \"DC OUTPUT\"). In the configuration shown in FIG1, a DC voltage is outputted as the power-supply voltage.", "Each of display circuits 81b, 81c, 81d includes an LED. For example, when an input voltage is normally inputted to power supply unit 20 of power supply device 100, the LED of display circuit 81d is ON. When a DC voltage is outputted from power supply device 100, the LED of display circuit 81b is ON. On the other hand, when an abnormality occurs in power supply device 100, the LED of display circuit 81c is ON. Display circuit 81d and display circuit 81b are implementations of LED circuit 12 and LED circuit 31, respectively, shown in FIG1, for example." ]

[ { "element_identifier": "28", "terms": [ "drive control circuit" ] }, { "element_identifier": "30", "terms": [ "output unit" ] }, { "element_identifier": "14", "terms": [ "input terminal", "input terminals" ] }, { "element_identifier": "11", "terms": [ "fuse" ] }, { "element_identifier": "100", "terms": [ "power supply device" ] }, { "element_identifier": "3", "terms": [ "Pattern" ] }, { "element_identifier": "2", "terms": [ "input" ] }, { "element_identifier": "20", "terms": [ "power supply unit" ] }, { "element_identifier": "25", "terms": [ "rush current limiting circuit" ] }, { "element_identifier": "42", "terms": [ "overvoltage detection circuit" ] }, { "element_identifier": "16", "terms": [ "protective earth terminal" ] }, { "element_identifier": "10", "terms": [ "input unit" ] }, { "element_identifier": "26", "terms": [ "noise filter" ] }, { "element_identifier": "29", "terms": [ "overcurrent detection circuit" ] }, { "element_identifier": "23", "terms": [ "MOSFET" ] }, { "element_identifier": "32", "terms": [ "output terminals", "output terminal" ] } ]

[ "100", "30", "32", "33", "10", "14", "11", "15", "20", "2", "25", "26", "28", "29", "23", "3", "42", "16" ]

[ "FIG2" ]

[ "FIG2 shows voltage and current waveforms associated with a leading-edge phase-cut dimmer" ]

[ "An example of an unacceptable or critical phase-cut input Vcut is shown in FIG2. Here, a leading-edge dimmer set at a phase-cut angle ϕ of about 60° has cut a portion of the mains voltage (indicated by the dotted line) at the beginning of each half-cycle, resulting in the phase-cut input Vcut. The result is a sudden voltage change, which in turn results in a spike in the current Ispike through the output capacitor of the lamp's driver. The current spike at large phase-cut angles is problematic for the type of filter circuit that is generally used in a low power-factor LED driver design. In such a driver, a pi-filter is used to suppress electromagnetic interference (EMI), with a relatively large capacitor across the outputs of the filter. Such a phase-cut input Vcut and the resulting current spike will eventually damage the LED lamp 10. Furthermore, the phase-cut results in a reduction in average voltage, which in turn increases the ripple current of the LED lamp, which in turn leads to a significant increase in temperature. To avoid damage resulting from current spikes and high temperatures, the LED lamp 10 according to the invention is provided with a phase-cut detector that can detect a phase-cut input to the LED lamp 10. If the phase-cut detector detects such a phase-cut input, the lighting system 1 applies a protection circuit to prevent operation of the LED lamp 10 with the phase-cut input. The phase-cut detector and protection circuit are explained below. FIG2 also indicates an acceptable or uncritical phase-cut input VOK (indicated by the broken line), for which the legacy phase-cut dimmer is set at a relatively small phase-cut angle ϕOK of about 20°, corresponding to a low dimmer setting, i.e. maximum or near-maximum light output." ]

[ { "element_identifier": "1", "terms": [ "lighting system" ] }, { "element_identifier": "11", "terms": [ "bridge", "wireless communication arrangement" ] }, { "element_identifier": "12", "terms": [ "router" ] }, { "element_identifier": "10", "terms": [ "lamp", "lamps" ] }, { "element_identifier": "100", "terms": [ "driver arrangement" ] }, { "element_identifier": "2", "terms": [ "mains power supply" ] }, { "element_identifier": "3", "terms": [ "dimmer" ] }, { "element_identifier": "110", "terms": [ "light source", "LEDs" ] }, { "element_identifier": "101", "terms": [ "driver" ] }, { "element_identifier": "102", "terms": [ "MCU" ] }, { "element_identifier": "104", "terms": [ "driver control signal", "driver control signals" ] }, { "element_identifier": "106", "terms": [ "protection circuit" ] }, { "element_identifier": "107", "terms": [ "output current" ] }, { "element_identifier": "1031", "terms": [ "first filter module" ] }, { "element_identifier": "1032", "terms": [ "further filter module" ] }, { "element_identifier": "1033", "terms": [ "comparator" ] }, { "element_identifier": "4", "terms": [ "smartphone" ] }, { "element_identifier": "5", "terms": [ "remote-controlled dimmer device" ] }, { "element_identifier": "7", "terms": [ "example" ] } ]

[ "12" ]

[ "FIG4" ]

[ "FIG4 shows a second embodiment of an LED lamp according to the invention" ]

[ "FIG4 shows a second simplified embodiment of an LED lamp 10 according to the invention, showing an alternative realization of a phase-cut detector 103B. In this case, the phase-cut detector 103B is realized as an overcurrent detector 103B which can detect a spike on the current through the output capacitor C. The presence of such a spike is notified to the MCU 102 in the form of a signal 105B, and the MCU 102 can react in any of the ways already described in Fig. above 3." ]

[ { "element_identifier": "100", "terms": [ "driver arrangement" ] }, { "element_identifier": "4", "terms": [ "smartphone" ] }, { "element_identifier": "104", "terms": [ "driver control signal", "driver control signals" ] }, { "element_identifier": "102", "terms": [ "MCU" ] }, { "element_identifier": "101", "terms": [ "driver" ] }, { "element_identifier": "106", "terms": [ "protection circuit" ] }, { "element_identifier": "110", "terms": [ "light source", "LEDs" ] } ]

[ "101", "110", "104", "106", "102", "100", "4", "14" ]

[ "FIG5" ]

[ "FIG5 shows a third embodiment of an LED lamp according to the invention" ]

[ "FIG5 shows a third simplified embodiment of an LED lamp 10 according to the invention, showing a further realization of a phase-cut detector 103C. In this case, the phase-cut detector 103C is realized as a driver output current monitor 103C which monitors the output current 107 of the driver 101 and compares this to an expected value. The driver output current is in the form of a modulated square wave at the switching frequency of the lamp's driver 101. To monitor the average driver output current, therefore, the phase-cut detector 103C comprises a first filter module 1031 for filtering and amplifying the driver output current. A further filter module 1032 serves to filter a pulse-width modulated (PWM) dimming signal originating from the MCU 102, and to bring this to a level corresponding to a maximum acceptable legacy dimmer setting, for example a level corresponding to 70% light output. The filter module outputs are compared in a comparator 1033, whose output 105C indicates to the MCU 102 when a phase-cut dimmer with an unacceptably large phase-cut angle is in active use with this lamp 10. The MCU 102 can respond as described in the preceding two embodiments, for example, the protection circuit 106 can output a driver control signal 104 which instructs the driver 101 to place the LEDs 110 in standby, thus protecting the lamp circuitry from spike damage." ]

[ { "element_identifier": "5", "terms": [ "remote-controlled dimmer device" ] }, { "element_identifier": "1031", "terms": [ "first filter module" ] }, { "element_identifier": "100", "terms": [ "driver arrangement" ] }, { "element_identifier": "1032", "terms": [ "further filter module" ] }, { "element_identifier": "104", "terms": [ "driver control signal", "driver control signals" ] }, { "element_identifier": "102", "terms": [ "MCU" ] }, { "element_identifier": "101", "terms": [ "driver" ] }, { "element_identifier": "110", "terms": [ "light source", "LEDs" ] }, { "element_identifier": "107", "terms": [ "output current" ] } ]

[ "101", "110", "107", "033", "1031", "104", "102", "100", "5", "1032", "15" ]

[ "FIG1" ]

[ "FIG1 shows a first embodiment of an LED lighting system according to the invention" ]

[ "FIG1 shows a first embodiment of an LED lighting system 1 according to the invention. In this exemplary embodiment, the LED lighting system 1 comprises a protocol bridge 11 such as a Zigbee® bridge, and a router 12 which can communicate with the bridge over a wireless LAN, for example using an Ethernet protocol. The lighting system 1 comprises at least one LED lamp 10. To keep the drawing simple, only one LED lamp 10 is shown. The LED lamp 10 comprises a driver arrangement 100 with driver and control circuitry. The driver arrangement 100 has a communications interface to allow it to exchange data D10_11 with the bridge 11. In this way, the bridge 11 can send commands to the lamp 10, and the lamp 10 can send a report or feedback to the bridge 11. Furthermore, each lamp 10 of the lighting system 1 can act as a Zigbee® router in a mesh network and can forward commands (originating from the bridge 11) to other lamps of the lighting system 1. In this way, the physical range of the network can be extended. The bridge 11 and any LED lamps 10 can exchange data D10_11 using a suitable protocol such as Zigbee® Light Link." ]

[ { "element_identifier": "12", "terms": [ "router" ] }, { "element_identifier": "11", "terms": [ "bridge", "wireless communication arrangement" ] }, { "element_identifier": "1", "terms": [ "lighting system" ] }, { "element_identifier": "100", "terms": [ "driver arrangement" ] }, { "element_identifier": "10", "terms": [ "lamp", "lamps" ] } ]

[ "10", "100", "12", "1", "11" ]

[ "FIG3" ]

[ "FIG3 is a cross-sectional view showing the internal structure of the plasma head" ]

[ "Next, the internal structure of plasma head 11 will be described with reference to FIG3. A pair of cylindrical recesses 60 are formed on the lower surface of main body block 20. Further, first gas flow path 62 and two second gas flow paths 66 are formed inside main body block 20. First gas flow path 62 opens between the pair of cylindrical recesses 60, and the two second gas flow paths 66 open inside the pair of cylindrical recesses 60. Second gas flow paths 66 extend from the left and right surfaces of main body block 20 toward the center of main body block 20 by a predetermined distance along the X axis direction, and then are bent downward. Further, first gas flow path 62 extends downward from the upper surface of main body block 20 by a predetermined distance along the Z-axis direction, then bends backward, and further bends downward." ]

[ { "element_identifier": "28", "terms": [ "first connecting block" ] }, { "element_identifier": "35", "terms": [ "reaction chamber" ] }, { "element_identifier": "30", "terms": [ "reaction chamber block" ] }, { "element_identifier": "11", "terms": [ "plasma head" ] }, { "element_identifier": "22", "terms": [ "electrodes" ] }, { "element_identifier": "63", "terms": [ "Insertion section" ] }, { "element_identifier": "64", "terms": [ "insertion section" ] }, { "element_identifier": "20", "terms": [ "main body block" ] }, { "element_identifier": "76", "terms": [ "insertion section" ] }, { "element_identifier": "66", "terms": [ "second gas flow path", "second gas flow paths" ] }, { "element_identifier": "26", "terms": [ "buffer member" ] }, { "element_identifier": "58", "terms": [ "conductive sections" ] }, { "element_identifier": "36", "terms": [ "connecting holes" ] }, { "element_identifier": "62", "terms": [ "first gas flow path" ] }, { "element_identifier": "60", "terms": [ "cylindrical recesses", "cylindrical recess" ] }, { "element_identifier": "32", "terms": [ "second connecting block" ] } ]

[ "3", "60", "99", "58", "62", "58", "66", "09", "52", "20", "22", "26", "76", "28", "64", "30", "63", "32", "22", "35", "36", "11" ]

[ "FIG5" ]

[ "FIG5 is a block diagram showing the electrical configuration of a detection module" ]

[ "As shown in FIG5, power source device 140 supplied from a commercial power supply (not shown) includes AC power supplies 141 and 142 and DC power supply 143. Detection module 120 includes current transformer CT, comparison circuit 121, power supply circuit 122, and switch 123. Power cable 40 includes first cable 41, second cable 42, and ground cable 43. Each of first cable 41, second cable 42, and ground cable 43 has an insulating body surrounding an electric wire. First cable 41, second cable 42, and ground cable 43 are shielded by a mesh-type conductive shield member 45. AC power supply 141 supplies AC power to plasma head 11 via first cable 41 and the second power supply cable. More specifically, each of first cable 41 and the second power supply cable supplies power to electrodes 22 and 22 of plasma head 11. Shield member 45 is grounded via ground cable 43." ]

[ { "element_identifier": "1", "terms": [ "patent literature" ] }, { "element_identifier": "10", "terms": [ "device", "devices" ] }, { "element_identifier": "11", "terms": [ "plasma head" ] }, { "element_identifier": "110", "terms": [ "control device" ] }, { "element_identifier": "40", "terms": [ "power cable" ] }, { "element_identifier": "80", "terms": [ "gas tube" ] }, { "element_identifier": "120", "terms": [ "detection module" ] }, { "element_identifier": "101", "terms": [ "robot arm" ] }, { "element_identifier": "100", "terms": [ "industrial robot" ] }, { "element_identifier": "5", "terms": [ "workpiece table" ] }, { "element_identifier": "41", "terms": [ "first cable" ] }, { "element_identifier": "42", "terms": [ "second cable" ] }, { "element_identifier": "43", "terms": [ "ground cable" ] }, { "element_identifier": "81", "terms": [ "first gas tube" ] }, { "element_identifier": "82", "terms": [ "second gas tube" ] }, { "element_identifier": "111", "terms": [ "processing gas supply device" ] }, { "element_identifier": "112", "terms": [ "processing gas supply device" ] }, { "element_identifier": "113", "terms": [ "touchscreen panel" ] }, { "element_identifier": "20", "terms": [ "main body block" ] }, { "element_identifier": "22", "terms": [ "electrodes" ] }, { "element_identifier": "26", "terms": [ "buffer member" ] }, { "element_identifier": "28", "terms": [ "first connecting block" ] }, { "element_identifier": "30", "terms": [ "reaction chamber block" ] }, { "element_identifier": "32", "terms": [ "second connecting block" ] }, { "element_identifier": "54", "terms": [ "upper holders" ] }, { "element_identifier": "58", "terms": [ "conductive sections" ] }, { "element_identifier": "62", "terms": [ "first gas flow path" ] }, { "element_identifier": "66", "terms": [ "second gas flow path", "second gas flow paths" ] }, { "element_identifier": "60", "terms": [ "cylindrical recesses", "cylindrical recess" ] }, { "element_identifier": "76", "terms": [ "insertion section" ] }, { "element_identifier": "64", "terms": [ "insertion section" ] }, { "element_identifier": "63", "terms": [ "Insertion section" ] }, { "element_identifier": "35", "terms": [ "reaction chamber" ] }, { "element_identifier": "36", "terms": [ "connecting holes" ] }, { "element_identifier": "130", "terms": [ "controller" ] }, { "element_identifier": "140", "terms": [ "power source device" ] }, { "element_identifier": "132", "terms": [ "drive circuits", "drive circuit" ] }, { "element_identifier": "141", "terms": [ "AC power supply" ] }, { "element_identifier": "142", "terms": [ "includes AC power supplies", "from AC power supply" ] }, { "element_identifier": "143", "terms": [ "DC power supply" ] }, { "element_identifier": "121", "terms": [ "comparison circuit" ] }, { "element_identifier": "122", "terms": [ "power supply circuit" ] }, { "element_identifier": "123", "terms": [ "switch" ] }, { "element_identifier": "45", "terms": [ "shield member" ] }, { "element_identifier": "92", "terms": [ "pressure sensor" ] }, { "element_identifier": "94", "terms": [ "flow rate controller" ] }, { "element_identifier": "134", "terms": [ "CPU" ] }, { "element_identifier": "150", "terms": [ "production line" ] }, { "element_identifier": "160", "terms": [ "administrator terminal" ] }, { "element_identifier": "170", "terms": [ "support desk terminal" ] }, { "element_identifier": "161", "terms": [ "display screen" ] }, { "element_identifier": "172", "terms": [ "display screen" ] }, { "element_identifier": "175", "terms": [ "information divided into five.", "alarm screen" ] }, { "element_identifier": "182", "terms": [ "using up scroll button" ] }, { "element_identifier": "184", "terms": [ "down scroll button" ] }, { "element_identifier": "186", "terms": [ "reset button" ] }, { "element_identifier": "176", "terms": [ "Number" ] }, { "element_identifier": "178", "terms": [ "device." ] } ]

[ "5", "40", "130", "142", "143", "2", "122", "123", "120", "13" ]

[ "FIG6" ]

[ "FIG6 is a schematic diagram showing a configuration related to the supply of processing gas in the plasma-generating device" ]

[ "Next, a configuration related to the supply of processing gas in plasma-generating device 10 will be described. As shown in FIG6, plasma head 11 and control device 110 are connected by gas tube 80. Control device 110 includes pressure sensor 92, flow rate controller 94, controller 130, and the like, and pressure sensor 92 and flow rate controller 94 are controlled by controller 130. Controller 130 is connected to first processing gas supply device 111 and second processing gas supply device 112. Gas tube 80 has first gas tube 81 through which nitrogen gas supplied from first processing gas supply device 111 flows, and second gas tube 82 to which dry air supplied from second processing gas supply device 112 is supplied.", "A program for performing determination processing is executed by CPU 134 (see FIG6) provided in controller 130. In this determination processing, the state of plasma-generating device 10 is determined based on whether the tube pressure between first gas tube 81 and second gas tube 82, which is defined for each flow rate of supplied processing gas, deviates from a standard value. When the pressures in first gas tube 81 and second gas tube 82 are equal to or higher than the standard value, it is determined that plasma is generated in plasma head 11 in a predetermined state. Here, the predetermined state means, for example, a state in which a specified amount of processing gas is supplied to plasma head 11 and plasma is stably generated. Further, when the pressure in first gas tube 81 and second gas tube 82 is equal to or lower than the standard value, the state of plasma-generating device 10 is determined to be abnormal. Here, abnormal means, for example, a case in which first gas tube 81 or second gas tube 82 is disconnected, a case in which processing gas is leaking to the outside due to breakage or breakage of a tube, a case in which the plasma is not being normally generated in plasma head 11, a case in which gas supply is defective, or the like. Further, the amount of leakage of the gas is determined according to the amount of the pressure decrease of the gas." ]

[ { "element_identifier": "1", "terms": [ "patent literature" ] }, { "element_identifier": "10", "terms": [ "device", "devices" ] }, { "element_identifier": "11", "terms": [ "plasma head" ] }, { "element_identifier": "110", "terms": [ "control device" ] }, { "element_identifier": "40", "terms": [ "power cable" ] }, { "element_identifier": "80", "terms": [ "gas tube" ] }, { "element_identifier": "120", "terms": [ "detection module" ] }, { "element_identifier": "101", "terms": [ "robot arm" ] }, { "element_identifier": "100", "terms": [ "industrial robot" ] }, { "element_identifier": "5", "terms": [ "workpiece table" ] }, { "element_identifier": "41", "terms": [ "first cable" ] }, { "element_identifier": "42", "terms": [ "second cable" ] }, { "element_identifier": "43", "terms": [ "ground cable" ] }, { "element_identifier": "81", "terms": [ "first gas tube" ] }, { "element_identifier": "82", "terms": [ "second gas tube" ] }, { "element_identifier": "111", "terms": [ "processing gas supply device" ] }, { "element_identifier": "112", "terms": [ "processing gas supply device" ] }, { "element_identifier": "113", "terms": [ "touchscreen panel" ] }, { "element_identifier": "20", "terms": [ "main body block" ] }, { "element_identifier": "22", "terms": [ "electrodes" ] }, { "element_identifier": "26", "terms": [ "buffer member" ] }, { "element_identifier": "28", "terms": [ "first connecting block" ] }, { "element_identifier": "30", "terms": [ "reaction chamber block" ] }, { "element_identifier": "32", "terms": [ "second connecting block" ] }, { "element_identifier": "54", "terms": [ "upper holders" ] }, { "element_identifier": "58", "terms": [ "conductive sections" ] }, { "element_identifier": "62", "terms": [ "first gas flow path" ] }, { "element_identifier": "66", "terms": [ "second gas flow path", "second gas flow paths" ] }, { "element_identifier": "60", "terms": [ "cylindrical recesses", "cylindrical recess" ] }, { "element_identifier": "76", "terms": [ "insertion section" ] }, { "element_identifier": "64", "terms": [ "insertion section" ] }, { "element_identifier": "63", "terms": [ "Insertion section" ] }, { "element_identifier": "35", "terms": [ "reaction chamber" ] }, { "element_identifier": "36", "terms": [ "connecting holes" ] }, { "element_identifier": "130", "terms": [ "controller" ] }, { "element_identifier": "140", "terms": [ "power source device" ] }, { "element_identifier": "132", "terms": [ "drive circuits", "drive circuit" ] }, { "element_identifier": "141", "terms": [ "AC power supply" ] }, { "element_identifier": "142", "terms": [ "includes AC power supplies", "from AC power supply" ] }, { "element_identifier": "143", "terms": [ "DC power supply" ] }, { "element_identifier": "121", "terms": [ "comparison circuit" ] }, { "element_identifier": "122", "terms": [ "power supply circuit" ] }, { "element_identifier": "123", "terms": [ "switch" ] }, { "element_identifier": "45", "terms": [ "shield member" ] }, { "element_identifier": "92", "terms": [ "pressure sensor" ] }, { "element_identifier": "94", "terms": [ "flow rate controller" ] }, { "element_identifier": "134", "terms": [ "CPU" ] }, { "element_identifier": "150", "terms": [ "production line" ] }, { "element_identifier": "160", "terms": [ "administrator terminal" ] }, { "element_identifier": "170", "terms": [ "support desk terminal" ] }, { "element_identifier": "161", "terms": [ "display screen" ] }, { "element_identifier": "172", "terms": [ "display screen" ] }, { "element_identifier": "175", "terms": [ "information divided into five.", "alarm screen" ] }, { "element_identifier": "182", "terms": [ "using up scroll button" ] }, { "element_identifier": "184", "terms": [ "down scroll button" ] }, { "element_identifier": "186", "terms": [ "reset button" ] }, { "element_identifier": "176", "terms": [ "Number" ] }, { "element_identifier": "178", "terms": [ "device." ] } ]

[ "81", "82", "94", "30", "134", "12", "92", "0", "80", "14" ]

[ "FIG6", " FIG7" ]

[ "FIG6 is a schematic diagram showing a configuration related to the supply of processing gas in the plasma-generating device ", "FIG7 is a graph showing the relationship between the gas flow rate and the pressure in the plasma-generating device" ]

[ "Next, a configuration related to the supply of processing gas in plasma-generating device 10 will be described. As shown in FIG6, plasma head 11 and control device 110 are connected by gas tube 80. Control device 110 includes pressure sensor 92, flow rate controller 94, controller 130, and the like, and pressure sensor 92 and flow rate controller 94 are controlled by controller 130. Controller 130 is connected to first processing gas supply device 111 and second processing gas supply device 112. Gas tube 80 has first gas tube 81 through which nitrogen gas supplied from first processing gas supply device 111 flows, and second gas tube 82 to which dry air supplied from second processing gas supply device 112 is supplied.", "A program for performing determination processing is executed by CPU 134 (see FIG6) provided in controller 130. In this determination processing, the state of plasma-generating device 10 is determined based on whether the tube pressure between first gas tube 81 and second gas tube 82, which is defined for each flow rate of supplied processing gas, deviates from a standard value. When the pressures in first gas tube 81 and second gas tube 82 are equal to or higher than the standard value, it is determined that plasma is generated in plasma head 11 in a predetermined state. Here, the predetermined state means, for example, a state in which a specified amount of processing gas is supplied to plasma head 11 and plasma is stably generated. Further, when the pressure in first gas tube 81 and second gas tube 82 is equal to or lower than the standard value, the state of plasma-generating device 10 is determined to be abnormal. Here, abnormal means, for example, a case in which first gas tube 81 or second gas tube 82 is disconnected, a case in which processing gas is leaking to the outside due to breakage or breakage of a tube, a case in which the plasma is not being normally generated in plasma head 11, a case in which gas supply is defective, or the like. Further, the amount of leakage of the gas is determined according to the amount of the pressure decrease of the gas. ", "FIG7 is a graph showing the relationship between the gas flow rate and the pressure in plasma-generating device 10. The horizontal axis represents the gas flow rate (L/min), and the vertical axis represents the pressure (kPa) in the gas tube. In a normal plasma-generating device 10 in which tubes or the like are not damaged or detached, the internal pressure with respect to the gas flow rate in a state in which plasma is not being generated is shown as a standard value. As the gas flow rate increases, the pressure inside first gas tube 81 and second gas tube 82 increases. Therefore, for each gas flow rate, the pressure corresponding to the gas flow rate is used as a standard value for detection of the internal pressure when determining the state of the device, and the state of the inside of the device is grasped by detecting a change in the pressure from the standard value." ]

[ { "element_identifier": "80", "terms": [ "gas tube" ] }, { "element_identifier": "5", "terms": [ "workpiece table" ] }, { "element_identifier": "30", "terms": [ "reaction chamber block" ] }, { "element_identifier": "100", "terms": [ "industrial robot" ] }, { "element_identifier": "20", "terms": [ "main body block" ] }, { "element_identifier": "40", "terms": [ "power cable" ] }, { "element_identifier": "10", "terms": [ "device", "devices" ] }, { "element_identifier": "60", "terms": [ "cylindrical recesses", "cylindrical recess" ] } ]

[ "7", "60", "50", "40", "30", "20", "10", "10", "15", "20", "25", "8", "100", "90", "80", "70", "60", "50", "40", "30", "20", "10", "5", "10", "15", "20", "25", "6", "100", "06", "80", "70", "60", "50", "40", "30", "20", "10", "0", "2", "4", "10", "12", "14", "16", "15" ]

[ "FIG10" ]

[ "FIG10 is a configuration diagram of a network for browsing various information related to the plasma-generating device" ]

[ "An information browsing system relating to plasma-generating device 10 will be described with reference to FIG10. First, various information such as settings and states of each plasma-generating device 10 installed in production line 10 is transmitted from control device 110 of each plasma-generating device 10 to cloud server CS via internet IN (D1). This transmission is performed periodically, and the information sent to cloud server CS is successively accumulated in cloud server CS. With an administrator who manages plasma-generating device 10 or production line 150 or at a support desk operated by a supplier of plasma-generating device 10, according to needs such as an inquiry from an operator, various kinds of required information for a required period of time can be downloaded from cloud server CS to a terminal of a user, that is, administrator terminal 160 or support desk terminal 170, and browsed (D2, D3). As a result, even when the administrator or the support desk is at a location away from plasma-generating device 10 or production line 150 and is unable to rush to the site in response to an inquiry from an operator, the administrator or the support desk can browse various required information for a required period of time, grasp the abnormal state, confirm the alarm information, refer to the maintenance information, the facility data, and the like, and instruct the operator to take an appropriate measure by telephone or the like." ]

[ { "element_identifier": "160", "terms": [ "administrator terminal" ] }, { "element_identifier": "113", "terms": [ "touchscreen panel" ] }, { "element_identifier": "10", "terms": [ "device", "devices" ] }, { "element_identifier": "150", "terms": [ "production line" ] }, { "element_identifier": "170", "terms": [ "support desk terminal" ] }, { "element_identifier": "161", "terms": [ "display screen" ] } ]

[ "10", "72", "170", "161", "160", "113", "150", "16" ]

[ "FIG1" ]

[ "FIG1 is a schematic diagram showing the configuration of a plasma-generating device attached to an industrial robot" ]

[ "As shown in FIG1, power cable 40 that connects electrodes 22 of plasma head 11 and power source device 140 and supplies power to electrodes 22 is attached to robot arm 101 of industrial robot 100. Therefore, in accordance with the movement of robot arm 101, power cable 40 may be subjected to stress such as bending, resting, or pulling, and may be damaged. Thus, in plasma-generating device 10, detection module 120 detects an abnormal current caused by damage to power cable 40 or the like. Next, a detailed description will be given." ]

[ { "element_identifier": "1", "terms": [ "patent literature" ] }, { "element_identifier": "10", "terms": [ "device", "devices" ] }, { "element_identifier": "11", "terms": [ "plasma head" ] }, { "element_identifier": "110", "terms": [ "control device" ] }, { "element_identifier": "40", "terms": [ "power cable" ] }, { "element_identifier": "80", "terms": [ "gas tube" ] }, { "element_identifier": "120", "terms": [ "detection module" ] }, { "element_identifier": "101", "terms": [ "robot arm" ] }, { "element_identifier": "100", "terms": [ "industrial robot" ] }, { "element_identifier": "5", "terms": [ "workpiece table" ] }, { "element_identifier": "41", "terms": [ "first cable" ] }, { "element_identifier": "42", "terms": [ "second cable" ] }, { "element_identifier": "43", "terms": [ "ground cable" ] }, { "element_identifier": "81", "terms": [ "first gas tube" ] }, { "element_identifier": "82", "terms": [ "second gas tube" ] }, { "element_identifier": "111", "terms": [ "processing gas supply device" ] }, { "element_identifier": "112", "terms": [ "processing gas supply device" ] }, { "element_identifier": "113", "terms": [ "touchscreen panel" ] }, { "element_identifier": "20", "terms": [ "main body block" ] }, { "element_identifier": "22", "terms": [ "electrodes" ] }, { "element_identifier": "26", "terms": [ "buffer member" ] }, { "element_identifier": "28", "terms": [ "first connecting block" ] }, { "element_identifier": "30", "terms": [ "reaction chamber block" ] }, { "element_identifier": "32", "terms": [ "second connecting block" ] }, { "element_identifier": "54", "terms": [ "upper holders" ] }, { "element_identifier": "58", "terms": [ "conductive sections" ] }, { "element_identifier": "62", "terms": [ "first gas flow path" ] }, { "element_identifier": "66", "terms": [ "second gas flow path", "second gas flow paths" ] }, { "element_identifier": "60", "terms": [ "cylindrical recesses", "cylindrical recess" ] }, { "element_identifier": "76", "terms": [ "insertion section" ] }, { "element_identifier": "64", "terms": [ "insertion section" ] }, { "element_identifier": "63", "terms": [ "Insertion section" ] }, { "element_identifier": "35", "terms": [ "reaction chamber" ] }, { "element_identifier": "36", "terms": [ "connecting holes" ] }, { "element_identifier": "130", "terms": [ "controller" ] }, { "element_identifier": "140", "terms": [ "power source device" ] }, { "element_identifier": "132", "terms": [ "drive circuits", "drive circuit" ] }, { "element_identifier": "141", "terms": [ "AC power supply" ] }, { "element_identifier": "142", "terms": [ "includes AC power supplies", "from AC power supply" ] }, { "element_identifier": "143", "terms": [ "DC power supply" ] }, { "element_identifier": "121", "terms": [ "comparison circuit" ] }, { "element_identifier": "122", "terms": [ "power supply circuit" ] }, { "element_identifier": "123", "terms": [ "switch" ] }, { "element_identifier": "45", "terms": [ "shield member" ] }, { "element_identifier": "92", "terms": [ "pressure sensor" ] }, { "element_identifier": "94", "terms": [ "flow rate controller" ] }, { "element_identifier": "134", "terms": [ "CPU" ] }, { "element_identifier": "150", "terms": [ "production line" ] }, { "element_identifier": "160", "terms": [ "administrator terminal" ] }, { "element_identifier": "170", "terms": [ "support desk terminal" ] }, { "element_identifier": "161", "terms": [ "display screen" ] }, { "element_identifier": "172", "terms": [ "display screen" ] }, { "element_identifier": "175", "terms": [ "information divided into five.", "alarm screen" ] }, { "element_identifier": "182", "terms": [ "using up scroll button" ] }, { "element_identifier": "184", "terms": [ "down scroll button" ] }, { "element_identifier": "186", "terms": [ "reset button" ] }, { "element_identifier": "176", "terms": [ "Number" ] }, { "element_identifier": "178", "terms": [ "device." ] } ]

[ "1", "110", "100", "40", "80", "11", "113", "20", "111", "112", "105", "105", "101", "5" ]

[ "FIG3" ]

[ "FIG3 is a cross-sectional view showing the internal structure of the plasma head" ]

[ "Next, the internal structure of plasma head 11 will be described with reference to FIG3. A pair of cylindrical recesses 60 are formed on the lower surface of main body block 20. Further, first gas flow path 62 and two second gas flow paths 66 are formed inside main body block 20. First gas flow path 62 opens between the pair of cylindrical recesses 60, and the two second gas flow paths 66 open inside the pair of cylindrical recesses 60. Second gas flow paths 66 extend from the left and right surfaces of main body block 20 toward the center of main body block 20 by a predetermined distance along the X axis direction, and then are bent downward. Further, first gas flow path 62 extends downward from the upper surface of main body block 20 by a predetermined distance along the Z-axis direction, then bends backward, and further bends downward." ]

[ { "element_identifier": "28", "terms": [ "first connecting block" ] }, { "element_identifier": "35", "terms": [ "reaction chamber" ] }, { "element_identifier": "30", "terms": [ "reaction chamber block" ] }, { "element_identifier": "11", "terms": [ "plasma head" ] }, { "element_identifier": "22", "terms": [ "electrodes" ] }, { "element_identifier": "63", "terms": [ "Insertion section" ] }, { "element_identifier": "64", "terms": [ "insertion section" ] }, { "element_identifier": "20", "terms": [ "main body block" ] }, { "element_identifier": "76", "terms": [ "insertion section" ] }, { "element_identifier": "66", "terms": [ "second gas flow path", "second gas flow paths" ] }, { "element_identifier": "26", "terms": [ "buffer member" ] }, { "element_identifier": "58", "terms": [ "conductive sections" ] }, { "element_identifier": "36", "terms": [ "connecting holes" ] }, { "element_identifier": "62", "terms": [ "first gas flow path" ] }, { "element_identifier": "60", "terms": [ "cylindrical recesses", "cylindrical recess" ] }, { "element_identifier": "32", "terms": [ "second connecting block" ] } ]

[ "3", "60", "66", "58", "62", "58", "66", "09", "52", "20", "22", "26", "76", "28", "64", "30", "63", "32", "22", "35", "36", "11" ]

[ "FIG5" ]

[ "FIG5 is a block diagram showing the electrical configuration of a detection module" ]

[ "As shown in FIG5, power source device 140 supplied from a commercial power supply (not shown) includes AC power supplies 141 and 142 and DC power supply 143. Detection module 120 includes current transformer CT, comparison circuit 121, power supply circuit 122, and switch 123. Power cable 40 includes first cable 41, second cable 42, and ground cable 43. Each of first cable 41, second cable 42, and ground cable 43 has an insulating body surrounding an electric wire. First cable 41, second cable 42, and ground cable 43 are shielded by a mesh-type conductive shield member 45. AC power supply 141 supplies AC power to plasma head 11 via first cable 41 and the second power supply cable. More specifically, each of first cable 41 and the second power supply cable supplies power to electrodes 22 and 22 of plasma head 11. Shield member 45 is grounded via ground cable 43." ]

[ { "element_identifier": "122", "terms": [ "power supply circuit" ] }, { "element_identifier": "5", "terms": [ "workpiece table" ] }, { "element_identifier": "142", "terms": [ "includes AC power supplies", "from AC power supply" ] }, { "element_identifier": "130", "terms": [ "controller" ] }, { "element_identifier": "123", "terms": [ "switch" ] }, { "element_identifier": "40", "terms": [ "power cable" ] }, { "element_identifier": "43", "terms": [ "ground cable" ] }, { "element_identifier": "140", "terms": [ "power source device" ] }, { "element_identifier": "120", "terms": [ "detection module" ] } ]

[ "5", "140", "130", "142", "43", "21", "122", "120", "123", "43", "120", "40", "13" ]

[ "FIG6" ]

[ "FIG6 is a schematic diagram showing a configuration related to the supply of processing gas in the plasma-generating device" ]

[ "Next, a configuration related to the supply of processing gas in plasma-generating device 10 will be described. As shown in FIG6, plasma head 11 and control device 110 are connected by gas tube 80. Control device 110 includes pressure sensor 92, flow rate controller 94, controller 130, and the like, and pressure sensor 92 and flow rate controller 94 are controlled by controller 130. Controller 130 is connected to first processing gas supply device 111 and second processing gas supply device 112. Gas tube 80 has first gas tube 81 through which nitrogen gas supplied from first processing gas supply device 111 flows, and second gas tube 82 to which dry air supplied from second processing gas supply device 112 is supplied.", "A program for performing determination processing is executed by CPU 134 (see FIG6) provided in controller 130. In this determination processing, the state of plasma-generating device 10 is determined based on whether the tube pressure between first gas tube 81 and second gas tube 82, which is defined for each flow rate of supplied processing gas, deviates from a standard value. When the pressures in first gas tube 81 and second gas tube 82 are equal to or higher than the standard value, it is determined that plasma is generated in plasma head 11 in a predetermined state. Here, the predetermined state means, for example, a state in which a specified amount of processing gas is supplied to plasma head 11 and plasma is stably generated. Further, when the pressure in first gas tube 81 and second gas tube 82 is equal to or lower than the standard value, the state of plasma-generating device 10 is determined to be abnormal. Here, abnormal means, for example, a case in which first gas tube 81 or second gas tube 82 is disconnected, a case in which processing gas is leaking to the outside due to breakage or breakage of a tube, a case in which the plasma is not being normally generated in plasma head 11, a case in which gas supply is defective, or the like. Further, the amount of leakage of the gas is determined according to the amount of the pressure decrease of the gas." ]

[ { "element_identifier": "80", "terms": [ "gas tube" ] }, { "element_identifier": "92", "terms": [ "pressure sensor" ] }, { "element_identifier": "130", "terms": [ "controller" ] }, { "element_identifier": "94", "terms": [ "flow rate controller" ] }, { "element_identifier": "112", "terms": [ "processing gas supply device" ] }, { "element_identifier": "134", "terms": [ "CPU" ] }, { "element_identifier": "81", "terms": [ "first gas tube" ] }, { "element_identifier": "82", "terms": [ "second gas tube" ] } ]

[ "6", "81", "82", "94", "130", "134", "112", "92", "80", "14" ]

[ "FIG6" ]

[ "FIG6 is a schematic diagram showing a configuration related to the supply of processing gas in the plasma-generating device" ]

[ "Next, a configuration related to the supply of processing gas in plasma-generating device 10 will be described. As shown in FIG6, plasma head 11 and control device 110 are connected by gas tube 80. Control device 110 includes pressure sensor 92, flow rate controller 94, controller 130, and the like, and pressure sensor 92 and flow rate controller 94 are controlled by controller 130. Controller 130 is connected to first processing gas supply device 111 and second processing gas supply device 112. Gas tube 80 has first gas tube 81 through which nitrogen gas supplied from first processing gas supply device 111 flows, and second gas tube 82 to which dry air supplied from second processing gas supply device 112 is supplied.", "A program for performing determination processing is executed by CPU 134 (see FIG6) provided in controller 130. In this determination processing, the state of plasma-generating device 10 is determined based on whether the tube pressure between first gas tube 81 and second gas tube 82, which is defined for each flow rate of supplied processing gas, deviates from a standard value. When the pressures in first gas tube 81 and second gas tube 82 are equal to or higher than the standard value, it is determined that plasma is generated in plasma head 11 in a predetermined state. Here, the predetermined state means, for example, a state in which a specified amount of processing gas is supplied to plasma head 11 and plasma is stably generated. Further, when the pressure in first gas tube 81 and second gas tube 82 is equal to or lower than the standard value, the state of plasma-generating device 10 is determined to be abnormal. Here, abnormal means, for example, a case in which first gas tube 81 or second gas tube 82 is disconnected, a case in which processing gas is leaking to the outside due to breakage or breakage of a tube, a case in which the plasma is not being normally generated in plasma head 11, a case in which gas supply is defective, or the like. Further, the amount of leakage of the gas is determined according to the amount of the pressure decrease of the gas." ]

[ { "element_identifier": "80", "terms": [ "gas tube" ] }, { "element_identifier": "5", "terms": [ "workpiece table" ] }, { "element_identifier": "30", "terms": [ "reaction chamber block" ] }, { "element_identifier": "100", "terms": [ "industrial robot" ] }, { "element_identifier": "20", "terms": [ "main body block" ] }, { "element_identifier": "40", "terms": [ "power cable" ] }, { "element_identifier": "10", "terms": [ "device", "devices" ] }, { "element_identifier": "60", "terms": [ "cylindrical recesses", "cylindrical recess" ] } ]

[ "09", "50", "40", "30", "20", "10", "5", "10", "15", "20", "25", "8", "100", "90", "80", "70", "60", "50", "40", "30", "20", "10", "5", "10", "15", "20", "25", "6", "100", "90", "80", "70", "09", "50", "40", "30", "20", "10", "0", "2", "4", "8", "10", "12", "14", "16", "15" ]

[ "FIG10" ]

[ "FIG10 is a configuration diagram of a network for browsing various information related to the plasma-generating device" ]

[ "An information browsing system relating to plasma-generating device 10 will be described with reference to FIG10. First, various information such as settings and states of each plasma-generating device 10 installed in production line 10 is transmitted from control device 110 of each plasma-generating device 10 to cloud server CS via internet IN (D1). This transmission is performed periodically, and the information sent to cloud server CS is successively accumulated in cloud server CS. With an administrator who manages plasma-generating device 10 or production line 150 or at a support desk operated by a supplier of plasma-generating device 10, according to needs such as an inquiry from an operator, various kinds of required information for a required period of time can be downloaded from cloud server CS to a terminal of a user, that is, administrator terminal 160 or support desk terminal 170, and browsed (D2, D3). As a result, even when the administrator or the support desk is at a location away from plasma-generating device 10 or production line 150 and is unable to rush to the site in response to an inquiry from an operator, the administrator or the support desk can browse various required information for a required period of time, grasp the abnormal state, confirm the alarm information, refer to the maintenance information, the facility data, and the like, and instruct the operator to take an appropriate measure by telephone or the like." ]

[ { "element_identifier": "172", "terms": [ "display screen" ] }, { "element_identifier": "160", "terms": [ "administrator terminal" ] }, { "element_identifier": "113", "terms": [ "touchscreen panel" ] }, { "element_identifier": "10", "terms": [ "device", "devices" ] }, { "element_identifier": "170", "terms": [ "support desk terminal" ] } ]

[ "10", "172", "170", "6", "160", "113", "50", "16" ]

[ "FIG1" ]

[ "FIG1 is a schematic diagram showing the configuration of a plasma-generating device attached to an industrial robot" ]

[ "As shown in FIG1, power cable 40 that connects electrodes 22 of plasma head 11 and power source device 140 and supplies power to electrodes 22 is attached to robot arm 101 of industrial robot 100. Therefore, in accordance with the movement of robot arm 101, power cable 40 may be subjected to stress such as bending, resting, or pulling, and may be damaged. Thus, in plasma-generating device 10, detection module 120 detects an abnormal current caused by damage to power cable 40 or the like. Next, a detailed description will be given." ]

[ { "element_identifier": "80", "terms": [ "gas tube" ] }, { "element_identifier": "5", "terms": [ "workpiece table" ] }, { "element_identifier": "11", "terms": [ "plasma head" ] }, { "element_identifier": "1", "terms": [ "Problem In patent literature" ] }, { "element_identifier": "100", "terms": [ "industrial robot" ] }, { "element_identifier": "113", "terms": [ "touchscreen panel" ] }, { "element_identifier": "40", "terms": [ "power cable" ] }, { "element_identifier": "112", "terms": [ "processing gas supply device" ] }, { "element_identifier": "111", "terms": [ "processing gas supply device" ] }, { "element_identifier": "101", "terms": [ "robot arm" ] }, { "element_identifier": "110", "terms": [ "control device" ] }, { "element_identifier": "120", "terms": [ "detection module" ] } ]

[ "1", "110", "100", "40", "80", "11", "113", "120", "111", "112", "3", "105", "105", "101", "5" ]

[ "FIG9" ]

[ "FIG9 is an exploded view showing a conventional atmospheric pressure plasma-generating device" ]

[ "On the other hand, as shown in FIG9, conventional atmospheric pressure plasma-generating device 150 includes pair of holders 152, internal block 154, connecting member 156, lower block 158, an emitting nozzle (not shown), and an upper block (not shown). Here, with atmospheric pressure plasma-generating device 150, the inner portion of internal block 154 functions as a reaction chamber by assembling the lower surfaces of pair of holders 152 to the upper surface of internal block 154. Therefore, only holders 152 and internal block 154 will be described." ]

[ { "element_identifier": "166", "terms": [ "main body section" ] }, { "element_identifier": "158", "terms": [ "lower block" ] }, { "element_identifier": "40", "terms": [ "connecting recess" ] }, { "element_identifier": "152", "terms": [ "holders" ] }, { "element_identifier": "46", "terms": [ "stepped surfaces" ] }, { "element_identifier": "36", "terms": [ "cylindrical recesses" ] }, { "element_identifier": "154", "terms": [ "internal block", "internal blocks" ] }, { "element_identifier": "48", "terms": [ "stepped surfaces" ] }, { "element_identifier": "156", "terms": [ "connecting member" ] }, { "element_identifier": "170", "terms": [ "recess" ] }, { "element_identifier": "24", "terms": [ "electrodes", "electrode" ] }, { "element_identifier": "140", "terms": [ "contact surface" ] }, { "element_identifier": "146", "terms": [ "single-dash broken line" ] }, { "element_identifier": "38", "terms": [ "cylindrical recesses" ] }, { "element_identifier": "168", "terms": [ "flange section" ] }, { "element_identifier": "148", "terms": [ "broken lines" ] }, { "element_identifier": "34", "terms": [ "flange section" ] }, { "element_identifier": "26", "terms": [ "electrodes", "electrode" ] } ]

[ "8", "40", "46", "36", "140", "24", "48", "38", "140", "26", "148", "148", "146", "34", "9", "50", "52", "152", "156", "170", "168", "166", "154", "158", "15" ]

[ "FIG1" ]

[ "FIG1 is a diagrammatical representation of an assembly, for example an electronic circuit board assembly for a high temperature operating device in accordance with an embodiment" ]

[ "Referring to FIG1, therein is illustrated, an apparatus, for example specifically referred to as an electronic circuit board assembly 10 including an electronic circuit board 12, such as a printed circuit board (PCB), in accordance with an embodiment and having coupled thereto a high operating temperature electronic device 14 in accordance with an embodiment. In an embodiment, the apparatus may be configured to include a printed wiring board (PWB). In an embodiment, the PCB or PWB and the high temperature operating device may form a printed circuit assembly (PCA), or a printed circuit board assembly (PCBA).", "In a further step 66, the deposited coating layer is patterned to form the plurality of conductive traces 20 on the substrate 16. Patterning the deposited coating layer to form the conductive traces 20 may be accomplished through well-known processing techniques, such as known subtractive processing techniques utilizing photoresist. At a step 68, areas for electrical connections, such as for the set of first metal contact pads, are masked or otherwise coated to protect them from subsequent processing steps. Coating materials may include, but are not limited to, nickel (Ni), silver (Ag), gold (Au), or the like. The device next undergoes an annealing process, at step 70. More specifically, the device is subject to an annealing process in which the coating layer is annealed in a vacuum or forming gas at approximately 300-400 degrees Celsius, for approximately one hour to allow for the aluminum (Al) material to migrate to the surface. This migration of the aluminum (Al) material forms an alumina passivation or protective layer, such a protective layer 26 (FIG1)." ]

[ { "element_identifier": "30", "terms": [ "coating layer" ] }, { "element_identifier": "12", "terms": [ "electronic circuit board" ] }, { "element_identifier": "22", "terms": [ "metal bumps" ] }, { "element_identifier": "18", "terms": [ "metal contact pads" ] }, { "element_identifier": "1", "terms": [ "clause" ] }, { "element_identifier": "20", "terms": [ "conductive traces" ] }, { "element_identifier": "16", "terms": [ "substrate" ] }, { "element_identifier": "10", "terms": [ "electronic circuit board assembly" ] }, { "element_identifier": "26", "terms": [ "protective layer" ] }, { "element_identifier": "32", "terms": [ "uppermost surface" ] } ]

[ "10", "24", "18", "12", "26", "22", "20", "16", "1", "16", "32", "30", "16", "10" ]

[ "FIG1" ]

[ "FIG1 is a schematic diagram illustrating a slide rail mechanism mounted on a rack according to an embodiment of the present invention" ]

[ "As shown in FIG1, a slide rail mechanism 20 of an embodiment of the present invention is applicable to a rack 22. The slide rail mechanism 20 includes a rail member 24 (also known as a first rail), and is able to be mounted on a first post 22a and a second post 22b of the rack 22 through a first bracket device 26 (also known as a bracket device) and a second bracket device 27." ]

[ { "element_identifier": "24", "terms": [ "rail member" ] }, { "element_identifier": "26", "terms": [ "first bracket device" ] } ]

[ "24", "26", "11", "42" ]