WO2024004160A1 - Nœud de réseau et procédé de communication - Google Patents

Nœud de réseau et procédé de communication Download PDF

Info

Publication number
WO2024004160A1
WO2024004160A1 PCT/JP2022/026345 JP2022026345W WO2024004160A1 WO 2024004160 A1 WO2024004160 A1 WO 2024004160A1 JP 2022026345 W JP2022026345 W JP 2022026345W WO 2024004160 A1 WO2024004160 A1 WO 2024004160A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
network node
information
error
network
Prior art date
Application number
PCT/JP2022/026345
Other languages
English (en)
Japanese (ja)
Inventor
寛 石川
淳 巳之口
俊輔 土尻
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2022/026345 priority Critical patent/WO2024004160A1/fr
Publication of WO2024004160A1 publication Critical patent/WO2024004160A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control

Definitions

  • the present invention relates to a network node and a communication method in a wireless communication system.
  • NR New Radio
  • 5G New Radio
  • EPC Evolved Packet Core
  • the network architecture includes 5GC (5G Core Network) and NG-RAN (Next Generation - Radio Access Network), which corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is RAN (Radio Access Network) in LTE network architecture.
  • 5GC 5G Core Network
  • NG-RAN Next Generation - Radio Access Network
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • RAN Radio Access Network
  • the content of the error that has occurred is mapped to a code value (Cause Code) that indicates the reason for the error included in a NAS (Non Access Stratum) signal, and is notified to the terminal.
  • a code value (Cause Code) that indicates the reason for the error included in a NAS (Non Access Stratum) signal.
  • the code values to be mapped differ depending on the implementation method of the mapping process, and there are not enough types of code values, so there is a problem that the content of the error occurring in the core network is not accurately notified to the terminal.
  • the present invention has been made in view of the above points, and it is an object of the present invention to improve the accuracy of notifications to terminals regarding errors occurring in the core network.
  • a receiving unit that receives information indicating the content of an error from another network node included in a core network in wireless communication, and a receiving unit that receives information that can identify the content of the error that has occurred in the other network node.
  • a network node comprising: a transmitter for transmitting to a terminal.
  • a technology that makes it possible to improve the accuracy of notifications to terminals regarding errors that occur in the core network.
  • FIG. 1 is a diagram for explaining a wireless communication system according to an embodiment of the present invention.
  • 1 is a diagram showing an example of a configuration of a wireless communication system according to an embodiment of the present invention.
  • FIG. 2 is a first diagram for explaining a conventional error notification method.
  • FIG. 2 is a second diagram for explaining a conventional error notification method.
  • FIG. 2 is a first diagram for explaining problems with the conventional error notification method.
  • FIG. 2 is a second diagram for explaining problems with the conventional error notification method.
  • FIG. 2 is a diagram for explaining an error notification method according to Example 1 of the embodiment of the present invention.
  • FIG. 3 is a diagram for explaining attributes of an HTTP signal according to Example 1 of the embodiment of the present invention.
  • FIG. 3 is a diagram showing an example of an HTTP signal according to Example 1 of the embodiment of the present invention.
  • FIG. 7 is a diagram for explaining an error notification method according to Example 2 of the embodiment of the present invention.
  • FIG. 7 is a diagram for explaining information elements of a NAS signal according to Example 2 of the embodiment of the present invention.
  • FIG. 7 is a diagram showing an example of a NAS signal according to Example 2 of the embodiment of the present invention.
  • 1 is a diagram showing an example of a functional configuration of a base station according to an embodiment of the present invention.
  • 1 is a diagram illustrating an example of a functional configuration of a terminal according to an embodiment of the present invention.
  • FIG. 1 is a diagram showing an example of the hardware configuration of a base station or a terminal according to an embodiment of the present invention.
  • 1 is a diagram showing an example of the configuration of a vehicle according to an embodiment of the present invention.
  • LTE Long Term Evolution
  • NR NR-Advanced
  • SS Synchronization signal
  • PSS Primary SS
  • SSS Secondary SS
  • PBCH Physical broadcast channel
  • PRACH Physical Terms such as random access channel
  • PDCCH Physical Downlink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or another method (for example, Flexible Duplex, etc.). This method may also be used.
  • “configuring" wireless parameters etc. may mean pre-configuring predetermined values, or It may also be possible to set wireless parameters notified from.
  • FIG. 1 is a diagram for explaining a wireless communication system according to an embodiment of the present invention.
  • the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20, as shown in FIG. Although FIG. 1 shows one base station 10 and one terminal 20, this is just an example, and there may be a plurality of each.
  • the base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20.
  • the physical resources of a radio signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Good too.
  • a TTI Transmission Time Interval
  • a TTI Transmission Time Interval
  • the base station 10 transmits a synchronization signal and system information to the terminal 20.
  • the synchronization signals are, for example, NR-PSS and NR-SSS.
  • System information is transmitted, for example, on NR-PBCH, and is also referred to as broadcast information.
  • the synchronization signal and system information may be called SSB (SS/PBCH block).
  • the base station 10 transmits a control signal or data to the terminal 20 on the DL (Downlink), and receives the control signal or data from the terminal 20 on the UL (Uplink).
  • Both the base station 10 and the terminal 20 can perform beamforming to transmit and receive signals. Further, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL.
  • MIMO Multiple Input Multiple Output
  • both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell) and a primary cell (PCell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary SCG cell (PSCell) of another base station 10 using DC (Dual Connectivity).
  • SCell secondary cell
  • PCell primary cell
  • DC Direct Connectivity
  • the terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or a communication module for M2M (Machine-to-Machine). As shown in FIG. 1, the terminal 20 receives control signals or data from the base station 10 via DL, and transmits control signals or data to the base station 10 via UL, thereby receiving various types of information provided by the wireless communication system. Use communication services. Furthermore, the terminal 20 receives various reference signals transmitted from the base station 10, and measures the channel quality based on the reception results of the reference signals. Note that the terminal 20 may be called a UE, and the base station 10 may be called a gNB.
  • FIG. 2 is a diagram illustrating an example of the configuration of a wireless communication system according to an embodiment of the present invention.
  • the wireless communication system includes a RAN 10, a terminal 20, a core network 30, and a DN (Data Network) 40.
  • the core network 30 is a network that includes an exchange, a subscriber information management device, and the like.
  • the core network 30 includes a network node that implements a U-Plane function and a network node group that implements a C-Plane function group.
  • the U-Plane function is a function that executes user data transmission and reception processing.
  • a network node that realizes the U-Plane function is, for example, a UPF (User plane function) 380.
  • the UPF 380 is a network node that has functions such as a PDU (Protocol Data Unit) session point to the outside for interconnection with the DN 40, packet routing and forwarding, and user plane QoS (Quality of Service) handling.
  • the UPF 380 controls data transmission and reception between the DN 40 and the terminal 20.
  • UPF 380 and DN 40 may be composed of one or more network slices.
  • the C-Plane function group is a function group that executes a series of control processes for establishing communication and the like.
  • the network nodes that realize the C-Plane function group include, for example, AMF (Access and Mobility Management Function) 310, UDM (Unified Data Management) 320, EIR (Equipment Identity Register) 330, and NSSF (Network Slice Selection Function). ) 340, an Authentication Server Function (AUSF) 350, a Policy Control Function (PCF) 360, a Session Management Function (SMF) 370, and an Application Function (AF) 390.
  • AMF Access and Mobility Management Function
  • UDM Unified Data Management
  • EIR Equipment Identity Register
  • NSSF Network Slice Selection Function
  • PCF Policy Control Function
  • SMF Session Management Function
  • AF Application Function
  • the RAN 10 is a network node that is communicably connected between the core network 30 and the terminal 20 and includes a base station, a line control device, and the like.
  • RAN10 is communicatively connected to AMF310 and UPF380.
  • the base station 10 is also called RAN10.
  • the AMF 310 is a network node that has functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management.
  • NSSF 340 is a network node that has the ability to select a set of network slice instances to serve terminal 20.
  • UDM 320 is a network node that manages subscriber data and authentication data.
  • the UDM 320 includes a UDR (User Data Repository) 321 that holds the data, and a FE (Front End) 322.
  • FE 322 processes subscriber information.
  • the SMF 370 is a network node that has functions such as session management, IP (Internet Protocol) address assignment and management of the terminal 20, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function.
  • EIR 330 is a network node that has the function of checking the status of PEI.
  • the PCF 360 is a network node that has a function of controlling network policy.
  • An AF (Application Function) 390 is a network node that has a function of controlling an application server.
  • the terminal 20 and AMF 310 are communicably connected as an N1 link.
  • AMF 310 and RAN 10 are communicably connected as an N2 link.
  • the UPF 380 and the RAN 10 are communicably connected as an N3 link.
  • the UPF 380 and the SMF 370 are communicably connected as an N4 link.
  • the UPF 380 and the DN 40 are communicably connected as an N6 link.
  • FIG. 3 is a first diagram for explaining a conventional error notification method.
  • MM mobility management
  • an error occurs in each network node (for example, NF Producer such as UDM 320, EIR 330, NSSF 340, AUSF 350, SMF 370, etc.) included in the core network 30.
  • each network node notifies the AMF 310 (NFConsumer) of the response code (error) and the application level error using an HTTP (HyperText Transfer Protocol) signal.
  • AMF 310 NFConsumer
  • HTTP HyperText Transfer Protocol
  • the AMF 310 converts these error codes into a code value (5GMM Reject cause value) specified in the NAS signal and transmits it to the terminal 20.
  • FIG. 4 is a second diagram for explaining the conventional error notification method.
  • SM session management
  • each network node included in the core network 30 for example, NFProducer such as UDM320, PCF360, etc.
  • HTTP HyperText Transfer Protocol
  • each network node uses HTTP (HyperText Transfer Protocol).
  • SMF Packet Forwarding Control Protocol
  • the UPF 380 notifies the SMF 370 (NFConsumer) of the PFCP (Packet Forwarding Control Protocol) error and the application level error.
  • PFCP Packet Forwarding Control Protocol
  • the SMF 370 converts these error codes into a code value (5GMM Reject cause value) specified in the NAS signal and sends it to the AMF 310.
  • AMF 310 transmits a NAS signal including the transmitted information to terminal 20.
  • the code values mapped differ depending on the implementation method of the mapping process, and there are not enough types of code values, so there is a problem that the details of errors occurring in the core network are not accurately notified to the terminal.
  • FIG. 5 is a first diagram for explaining the problems of the conventional error notification method.
  • the AMF 310 converts it to one of the following code values (1) to (4) (5GMM Reject cause value).
  • (1) Cause #11 - PLMN not allowed
  • (2) Cause #73 - Serving network not authorized
  • (3) Cause #12 - Tracking area not allowed
  • (4) Cause #15 - No suitable cells in tracking area
  • the terminal 20 behaves differently depending on the code value (5GMM Reject cause value) received. However, since the AMF 310 does not convert the generated error into a NAS code value on a one-to-one basis, the error notified by the UDM 320 is not transmitted to the terminal 20, and the UDM 320 cannot unify the expected behavior of the terminal 20. .
  • the UDM 320 does not know how the AMF 310 converts the error code, so it does not know how the error is notified to the terminal 20. do not have. For example, if the home operator (UDM 320) cannot select the code value of the NAS signal (NAS cause code), which has a great influence on the selection of the PLMN (Public Land Mobile Network) to which the terminal 20 roams, the service cannot be provided. Risk arises.
  • NAS cause code Public Land Mobile Network
  • FIG. 6 is a second diagram for explaining problems with the conventional error notification method.
  • a "SERVING_NETWORK_NOT_AUTHORIZED" error occurs in the UDM320, it is up to the UDM320 whether the AMF310 converts it to "(1) Cause #11 - PLMN not allowed” or "(3) Cause #12 - Tracking area not allowed” and is unknown to the home operator managing the said business.
  • the terminal 20 When the terminal 20 receives "Cause #12" and moves to another location (Tracking Area), the terminal 20 becomes able to select the PLMN again. On the other hand, when the terminal 20 receives "Cause #11", it is stored in the "Forbidden PLMN list" and will never select the PLMN again.
  • Example 1 In this embodiment, an example will be described in which an error code value (NAS Reject cause) of the NAS signal is included in the HTTP signal. Specifically, in the core network 30, a network node belonging to each NFProducer notifies the terminal of the error code value of the NAS signal (NAS Reject Cause value) in addition to the conventional code value of the error reason. Controls the value notified for 20.
  • NAS Reject cause an error code value of the NAS signal
  • FIG. 7 is a diagram for explaining an error notification method according to Example 1 of the embodiment of the present invention. For example, if the error content is "SERVING_NETWORK_NOT_AUTHORIZED" and the terminal 20 moves in the tracking area, if you want to make the PLMN selectable, the UDM 320 will write the NAS code value along with the error code. Send the recommended value (suggested NAS cause code #12) to the AMF310.
  • the AMF 310 notifies the terminal 20 of "(3) Cause #12 - Tracking area not allowed" based on the recommended NAS code value received from the UDM 320.
  • the UDM 320 will send the NAS code value along with the error code. Send the recommended value (suggested NAS cause code #11).
  • the AMF 310 notifies the terminal 20 of "(1) Cause #11 - PLMN not allowed" based on the recommended NAS code value received from the UDM 320.
  • the intended value of the UDM 320 is transmitted to the terminal 20, the expected operations of the terminal 20 can be unified.
  • a network node belonging to an NFProducer such as the PCF 360 transmits a recommended NAS code value along with an HTTP response code.
  • the SMF 370 transmits the content to be notified to the terminal 20 to the AMF 310 based on the received recommended NAS code value.
  • AMF 310 transmits a NAS signal including the received content to terminal 20.
  • the UPF 380 may transmit the recommended value of the NAS code value along with the PFCP error.
  • the SMF 370 transmits the content to be notified to the terminal 20 to the AMF 310 based on the recommended value of the received NAS code value.
  • AMF 310 transmits a NAS signal including the received content to terminal 20.
  • FIG. 8 is a diagram for explaining attributes of an HTTP signal according to Example 1 of the embodiment of the present invention.
  • a new attribute (Attribute) is added to the conventionally defined problem detail type (Definition of type ProblemDetails) as an attribute of an HTTP signal.
  • This enables notification of a code value (cause code) to be set in a NAS signal destined for the terminal 20 from a network node (such as UDM 320) belonging to the NFProducer.
  • an attribute for mobility management (nas5gmmCauseCode) and an attribute for session management (nas5gsmCauseCode) may be added.
  • FIG. 9 is a diagram showing an example of an HTTP signal according to Example 1 of the embodiment of the present invention.
  • ProblemDetails written in JSON (JavaScript (registered trademark) Object Notation) in the body portion of the HTTP signal is defined by RFC7807.
  • JSON JavaScript (registered trademark) Object Notation
  • RFC7807 JavaScript (registered trademark) Object Notation
  • values that can be set in a cause attribute unique to each API are defined as usable attributes.
  • the AMF 310 or SMF 370 selects the received recommended value as is when converting the code value.
  • the recommended value is an example of information that can identify the content of the error that has occurred. This ensures end-to-end value consistency and ensures consistency in the expected behavior of the NFProducer for the terminal 20.
  • Example 2 In this embodiment, an example will be described in which the code value (Cause) of ProblemDetails of the HTTP signal is included in the NAS signal.
  • the specifications of the NAS signal can be expanded to notify the terminal 20 of the conventional error code (Cause) used in the core network 30 together with the error code (NAS Reject Cause) value of the NAS signal. It can be so. This allows the terminal 20 to understand both code values, interpret and act on the expected behavior of the network node belonging to the NFProducer.
  • FIG. 10 is a diagram for explaining an error notification method according to Example 2 of the embodiment of the present invention. For example, if the error content is "SERVING_NETWORK_NOT_AUTHORIZED", the UDM 320 transmits the error code to the AMF 310.
  • the AMF 310 converts it into one of the following code values (1) to (4) (5GMM Reject cause value) as in the conventional case.
  • (1) Cause #11 - PLMN not allowed
  • (2) Cause #73 - Serving network not authorized
  • (3) Cause #12 - Tracking area not allowed
  • (4) Cause #15 - No suitable cells in tracking area
  • the AMF 310 includes the error code received from the UDM 320 in the NAS signal as a Service Based Interface (SBI), and notifies the terminal 20 of the error code.
  • SBI Service Based Interface
  • the intended value of the UDM 320 is transmitted to the terminal 20, so that the expected operations of the terminal 20 can be unified.
  • the SMF 370 transmits an error code received from a network node belonging to the NFProducer, such as the PCF 360 or the UPF 380, to the AMF 310 as a service standards interface (SBI).
  • AMF 310 transmits a NAS signal including the received content to terminal 20.
  • FIG. 11 is a diagram for explaining information elements of a NAS signal according to Example 2 of the embodiment of the present invention.
  • the service standard interface error reason (SBI reject cause) has been added as an information element of the NAS signal, and the code value (Cause) of ProblemDetails described in the JSON format body of the HTTP signal can be set in the information element. Make it.
  • the terminal 20 can understand the ProblemDetails themselves in addition to the error code converted by the AMF 310 or the SMF 370, and can perform an operation according to the value.
  • FIG. 12 is a diagram showing an example of a NAS signal according to Example 2 of the embodiment of the present invention. What is shown in FIG. 12 is an example of the prescribed value of each bit in the newly defined format as the service standard interface error reason (SBI reject cause).
  • SBI reject cause the service standard interface error reason
  • the AMF 310 or SMF 370 converts the code value and notifies the received error code by including it as is in the NAS signal.
  • the error code is an example of information that can identify the content of the error that has occurred. This ensures end-to-end value consistency and ensures consistency in the expected behavior of the NFProducer for the terminal 20.
  • the terminal 20 may transmit information indicating the terminal capability to the base station 10.
  • the terminal 20 may transmit information indicating the terminal ability to support the second embodiment described above.
  • the AMF 310 or SMF 370 uses information indicating the terminal capability notified from the terminal 20 and whether or not the AMF 310 or SMF 370 itself supports either or both of the first embodiment and the second embodiment.
  • Information indicating the ability to support either or both of Embodiment 1 and Embodiment 2 may be transmitted to each network node belonging to the NFProducer depending on the ability to support the NFProducer.
  • the core network 30 may realize either or both of the functions based on whether or not it is compatible with either the first embodiment or the second embodiment, or if both functions can be realized, the core network 30 may further Either or both functions may be implemented based on the terminal capabilities described above.
  • the AMF 310 when roaming, has the option of converting to multiple code values (cause codes), and the home network side converts the intended code value (cause code) regardless of the implementation of the AMF 310 in the other network.
  • Cause code can be selected.
  • the correspondence is made according to the mobile model used, and the code value (cause code) used can be changed for each model or terminal, making it possible to respond flexibly to the impact on services.
  • Base station 10, terminal 20, and various network nodes include functionality to implement the embodiments described above. However, the base station 10, the terminal 20, and various network nodes may each have only some of the functions in the embodiment.
  • FIG. 13 is a diagram illustrating an example of the functional configuration of the base station 10.
  • base station 10 includes a transmitting section 110, a receiving section 120, a setting section 130, and a control section 140.
  • the functional configuration shown in FIG. 13 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
  • the network node may have the same functional configuration as the base station 10. Further, a network node having a plurality of different functions in the system architecture may be configured from a plurality of network nodes separated for each function.
  • the transmitting unit 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node, and transmitting the signal by wire or wirelessly.
  • the receiving unit 120 includes a function of receiving various signals transmitted from the terminal 20 or other network nodes, and acquiring, for example, information on a higher layer from the received signals.
  • the setting unit 130 stores preset setting information and various setting information to be sent to the terminal 20 in a storage device, and reads them from the storage device as necessary.
  • the contents of the setting information include, for example, settings related to communication using NTN.
  • control unit 140 performs processing related to communication using NTN. Further, the control unit 140 performs processing related to communication with the terminal 20. Further, the control unit 140 performs processing related to verifying the geographical position of the terminal 20.
  • a functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.
  • FIG. 14 is a diagram showing an example of the functional configuration of the terminal 20.
  • the terminal 20 includes a transmitting section 210, a receiving section 220, a setting section 230, and a control section 240.
  • the functional configuration shown in FIG. 14 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
  • the USIM attached to the terminal 20 may include a transmitting section 210, a receiving section 220, a setting section 230, and a control section 240, similarly to the terminal 20.
  • the transmitter 210 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal.
  • the receiving unit 220 wirelessly receives various signals and obtains higher layer signals from the received physical layer signals. Furthermore, the receiving unit 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, reference signals, etc. transmitted from network nodes.
  • the setting unit 230 stores various setting information received from the network node by the receiving unit 220 in a storage device, and reads it from the storage device as necessary.
  • the setting unit 230 also stores setting information that is set in advance.
  • the network node of this embodiment may be configured as a network node shown in each section below. Additionally, the following communication method may be implemented.
  • a receiving unit that receives information indicating error details from other network nodes included in a core network in wireless communication; a transmitter that transmits information that can identify the content of the error that has occurred in the other network node to the terminal; network node.
  • the receiving unit receives information indicating a recommended value to be transmitted to the terminal from the other network node, the transmitter transmits a NAS signal including the recommended value to the terminal; Network node according to paragraph 1.
  • the transmitter transmits a NAS signal including information indicating the content of the error received from the other network node to the terminal.
  • Network node according to paragraph 1. (Section 4) receiving information indicating the content of the error from another network node included in the core network in wireless communication; transmitting information that can identify the content of the error that occurred in the other network node to the terminal; A communication method performed by network nodes.
  • any of the above configurations provides a technology that makes it possible to improve the accuracy of notifications to terminals regarding errors that occur in the core network.
  • information that can identify the content of an error that has occurred in another network node can be transmitted to the terminal.
  • a NAS signal containing a recommended value to be transmitted to the terminal from another network node can be transmitted to the terminal.
  • each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices.
  • the functional block may be realized by combining software with the one device or the plurality of devices.
  • Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't.
  • a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.
  • the network node, terminal 20, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 15 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure.
  • the network node may have a similar hardware configuration to the base station 10.
  • the USIM may have the same hardware configuration as the terminal 20.
  • the base station 10 and terminal 20 described above are physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc. Good too.
  • the word “apparatus” can be read as a circuit, a device, a unit, etc.
  • the hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured not to include some of the devices.
  • Each function in the base station 10 and the terminal 20 is performed by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs calculations and controls communication by the communication device 1004. This is realized by controlling at least one of reading and writing data in the storage device 1002 and the auxiliary storage device 1003.
  • the processor 1001 for example, operates an operating system to control the entire computer.
  • the processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like.
  • CPU central processing unit
  • control unit 140, control unit 240, etc. may be implemented by the processor 1001.
  • the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes in accordance with these.
  • programs program codes
  • software modules software modules
  • data etc.
  • the control unit 140 of the base station 10 shown in FIG. 13 may be realized by a control program stored in the storage device 1002 and operated on the processor 1001.
  • control unit 240 of the terminal 20 shown in FIG. 14 may be realized by a control program stored in the storage device 1002 and operated on the processor 1001.
  • Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.
  • the storage device 1002 is a computer-readable recording medium, such as at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be configured.
  • the storage device 1002 may be called a register, cache, main memory, or the like.
  • the storage device 1002 can store executable programs (program codes), software modules, and the like to implement a communication method according to an embodiment of the present disclosure.
  • the auxiliary storage device 1003 is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu-ray disk, etc.). -ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, etc.
  • the above-mentioned storage medium may be, for example, a database including at least one of the storage device 1002 and the auxiliary storage device 1003, a server, or other suitable medium.
  • the communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example.
  • the communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of.
  • FDD frequency division duplex
  • TDD time division duplex
  • the transmitting and receiving unit may be physically or logically separated into a transmitting unit and a receiving unit.
  • the input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
  • each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses for each device.
  • the base station 10 and the terminal 20 also include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA).
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • a part or all of each functional block may be realized by the hardware.
  • processor 1001 may be implemented using at least one of these hardwares.
  • FIG. 16 shows an example of the configuration of the vehicle 2001.
  • the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, a front wheel 2007, a rear wheel 2008, an axle 2009, an electronic control unit 2010, and various sensors 2021 to 2029. , an information service section 2012 and a communication module 2013.
  • Each aspect/embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, may be applied to communication module 2013.
  • the drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.
  • the steering unit 2003 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
  • the electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and communication port (IO port) 2033. Signals from various sensors 2021 to 2029 provided in the vehicle 2001 are input to the electronic control unit 2010.
  • the electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
  • Signals from various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the motor current, a front wheel and rear wheel rotation speed signal obtained by a rotation speed sensor 2022, and a front wheel rotation speed signal obtained by an air pressure sensor 2023. and rear wheel air pressure signals, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression amount signals acquired by accelerator pedal sensor 2029, and brake pedal sensor 2026. These include a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 2027, a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028, and the like.
  • the information service department 2012 controls various devices such as car navigation systems, audio systems, speakers, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and these devices. It is composed of one or more ECUs.
  • the information service unit 2012 provides various multimedia information and multimedia services to the occupants of the vehicle 2001 using information acquired from an external device via the communication module 2013 and the like.
  • the information service department 2012 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device that performs output to the outside (for example, display, speaker, LED lamp, touch panel, etc.).
  • an input device for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.
  • an output device that performs output to the outside (for example, display, speaker, LED lamp, touch panel, etc.).
  • the driving support system unit 2030 includes a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (for example, GNSS, etc.), map information (for example, a high-definition (HD) map, an autonomous vehicle (AV) map, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden.
  • the system is comprised of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 2030 transmits and receives various information via the communication module 2013, and realizes a driving support function or an automatic driving function.
  • Communication module 2013 can communicate with microprocessor 2031 and components of vehicle 2001 via a communication port.
  • the communication module 2013 communicates with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, electronic Data is transmitted and received between the microprocessor 2031, memory (ROM, RAM) 2032, and sensors 2021 to 29 in the control unit 2010.
  • the communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, various information is transmitted and received with an external device via wireless communication.
  • the communication module 2013 may be located either inside or outside the electronic control unit 2010.
  • the external device may be, for example, a base station, a mobile station, or the like.
  • the communication module 2013 receives signals from the various sensors 2021 to 2029 described above that are input to the electronic control unit 2010, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 2012. At least one of the information based on the information may be transmitted to an external device via wireless communication.
  • the electronic control unit 2010, various sensors 2021-2029, information service unit 2012, etc. may be called an input unit that receives input.
  • the PUSCH transmitted by the communication module 2013 may include information based on the above input.
  • the communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device, and displays it on the information service section 2012 provided in the vehicle 2001.
  • the information service unit 2012 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 2013). may be called.
  • the communication module 2013 also stores various information received from external devices into a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 controls the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, and axle 2009 provided in the vehicle 2001. , sensors 2021 to 2029, etc. may be controlled.
  • the operations of a plurality of functional sections may be physically performed by one component, or the operations of one functional section may be physically performed by a plurality of components.
  • the order of processing may be changed as long as there is no contradiction.
  • Software operated by the processor included in the base station 10 according to the embodiment of the present invention and software operated by the processor included in the terminal 20 according to the embodiment of the present invention are respectively random access memory (RAM), flash memory, and read-only memory. (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.
  • the notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods.
  • the notification of information may be physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling). , broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.
  • RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG xG (x is an integer or decimal number, for example)
  • FRA Fluture Radio Access
  • NR new Radio
  • New radio access NX
  • Future generation radio access FX
  • W-CDMA registered trademark
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access 2000
  • UMB User Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802 .16 WiMAX (registered trademark)
  • IEEE 802.20 UWB (Ultra-WideBand
  • Bluetooth registered trademark
  • the base station 10 may be performed by its upper node in some cases.
  • various operations performed for communication with a terminal 20 are performed by the base station 10 and other network nodes other than the base station 10. It is clear that this can be done by at least one of the following: for example, MME or S-GW (possible, but not limited to).
  • MME Mobility Management Entity
  • S-GW Packet Control Function
  • the other network node may be a combination of multiple other network nodes (for example, MME and S-GW).
  • the information, signals, etc. described in this disclosure may be output from an upper layer (or lower layer) to a lower layer (or upper layer). It may be input/output via multiple network nodes.
  • the input/output information may be stored in a specific location (for example, memory) or may be managed using a management table. Information etc. to be input/output may be overwritten, updated, or additionally written. The output information etc. may be deleted. The input information etc. may be transmitted to other devices.
  • the determination in the present disclosure may be performed based on a value represented by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (e.g. , comparison with a predetermined value).
  • Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.
  • software, instructions, information, etc. may be sent and received via a transmission medium.
  • a transmission medium For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create a website, When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.
  • wired technology coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.
  • wireless technology infrared, microwave, etc.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of
  • At least one of the channel and the symbol may be a signal.
  • the signal may be a message.
  • a component carrier may also be called a carrier frequency, a cell, a frequency carrier, or the like.
  • system and “network” are used interchangeably.
  • radio resources may be indicated by an index.
  • Base Station BS
  • wireless base station base station
  • base station fixed station
  • NodeB eNodeB
  • gNodeB gNodeB
  • a base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into multiple subsystems (e.g., small indoor base stations (RRHs)). Communication services can also be provided by Remote Radio Head).
  • RRHs small indoor base stations
  • Communication services can also be provided by Remote Radio Head).
  • the term "cell” or “sector” refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.
  • the base station transmitting information to the terminal may be read as the base station instructing the terminal to control/operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station is defined by a person skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc.
  • the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like.
  • the moving body refers to a movable object, and the moving speed is arbitrary. Naturally, this also includes cases where the moving object is stopped.
  • the mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, ships and other watercraft.
  • the mobile object may be a mobile object that autonomously travels based on a travel command. It may be a vehicle (e.g. car, airplane, etc.), an unmanned moving object (e.g. drone, self-driving car, etc.), or a robot (manned or unmanned). good.
  • the base station and the mobile station includes devices that do not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be replaced by a user terminal.
  • communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (for example, it may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.).
  • the terminal 20 may have the functions that the base station 10 described above has.
  • words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
  • uplink channels, downlink channels, etc. may be replaced with side channels.
  • the user terminal in the present disclosure may be replaced with a base station.
  • the base station may have the functions that the user terminal described above has.
  • determining may encompass a wide variety of operations.
  • “Judgment” and “decision” include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a “judgment” or “decision.”
  • judgment and “decision” refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access.
  • (accessing) may include considering something as a “judgment” or “decision.”
  • judgment and “decision” mean that resolving, selecting, choosing, establishing, comparing, etc. are considered to be “judgement” and “decision.” may be included.
  • judgment and “decision” may include regarding some action as having been “judged” or “determined.”
  • judgment (decision) may be read as “assuming", “expecting", “considering”, etc.
  • connection refers to any connection or coupling, direct or indirect, between two or more elements and to each other. It may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled.”
  • the bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection” may be replaced with "access.”
  • two elements may include one or more electrical wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges.
  • the reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applied standard.
  • RS Reference Signal
  • the phrase “based on” does not mean “based solely on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to elements using the designations "first,” “second,” etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.
  • a radio frame may be composed of one or more frames in the time domain. Each frame or frames in the time domain may be called a subframe. A subframe may also be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
  • the numerology may be a communication parameter applied to the transmission and/or reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, and transmitter/receiver. It may also indicate at least one of a specific filtering process performed in the frequency domain, a specific windowing process performed by the transceiver in the time domain, and the like.
  • SCS subcarrier spacing
  • TTI transmission time interval
  • transmitter/receiver transmitter/receiver. It may also indicate at least one of a specific filtering process performed in the frequency domain, a specific windowing process performed by the transceiver in the time domain, and the like.
  • a slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain.
  • a slot may be a unit of time based on numerology.
  • a slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot.
  • PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A.
  • PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.
  • Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol.
  • one subframe may be called a transmission time interval (TTI)
  • TTI transmission time interval
  • multiple consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI. It's okay.
  • at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be.
  • the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
  • TTI refers to, for example, the minimum time unit for scheduling in wireless communication.
  • a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each terminal 20) to each terminal 20 on a TTI basis.
  • radio resources frequency bandwidth, transmission power, etc. that can be used by each terminal 20
  • TTI is not limited to this.
  • the TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.
  • one slot or one minislot is called a TTI
  • one or more TTIs may be the minimum time unit for scheduling.
  • the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.
  • a TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc.
  • TTI that is shorter than the normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
  • long TTI for example, normal TTI, subframe, etc.
  • short TTI for example, short TTI, etc. It may also be read as a TTI having the above TTI length.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more continuous subcarriers in the frequency domain.
  • the number of subcarriers included in an RB may be the same regardless of the numerology, and may be 12, for example.
  • the number of subcarriers included in an RB may be determined based on newerology.
  • the time domain of an RB may include one or more symbols, and may be one slot, one minislot, one subframe, or one TTI in length.
  • One TTI, one subframe, etc. may each be composed of one or more resource blocks.
  • one or more RBs include physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. May be called.
  • PRBs physical resource blocks
  • SCGs sub-carrier groups
  • REGs resource element groups
  • PRB pairs RB pairs, etc. May be called.
  • a resource block may be configured by one or more resource elements (REs).
  • REs resource elements
  • 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
  • a bandwidth part (which may also be called a partial bandwidth or the like) may represent a subset of consecutive common resource blocks (RBs) for a certain numerology in a certain carrier.
  • the common RB may be specified by an RB index based on a common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within that BWP.
  • the BWP may include a UL BWP (UL BWP) and a DL BWP (DL BWP).
  • UL BWP UL BWP
  • DL BWP DL BWP
  • One or more BWPs may be configured for the terminal 20 within one carrier.
  • At least one of the configured BWPs may be active, and the terminal 20 does not need to assume that it transmits or receives a given signal/channel outside the active BWP.
  • Note that "cell”, “carrier”, etc. in the present disclosure may be replaced with "BWP”.
  • radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples.
  • the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB, Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.
  • a and B are different may mean “A and B are different from each other.” Note that the term may also mean that "A and B are each different from C”. Terms such as “separate” and “coupled” may also be interpreted similarly to “different.”
  • notification of prescribed information is not limited to being done explicitly, but may also be done implicitly (for example, not notifying the prescribed information). Good too.
  • Base station (RAN) 110 Transmitting section 120 Receiving section 130 Setting section 140 Control section 20 Terminal 30 Core network 40 DN 210 Transmitting section 220 Receiving section 230 Setting section 240 Control section 310 AMF 320UDM 330 EIR 340 NSSF 350 AUSF 360 PCF 370 SMF 380 UPF 390 AF 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive section 2003 Steering section 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control section 2012 Information service section 2013 Communication module 2021 Current sensor 2022 Rotational speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving support system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un nœud de réseau comprenant une unité de réception qui reçoit des informations indiquant le contenu d'une erreur provenant d'un autre nœud de réseau inclus dans un réseau central en communication sans fil, et une unité de transmission qui transmet, à un terminal, des informations permettant l'identification du contenu de l'erreur se produisant dans l'autre nœud de réseau.
PCT/JP2022/026345 2022-06-30 2022-06-30 Nœud de réseau et procédé de communication WO2024004160A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/026345 WO2024004160A1 (fr) 2022-06-30 2022-06-30 Nœud de réseau et procédé de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/026345 WO2024004160A1 (fr) 2022-06-30 2022-06-30 Nœud de réseau et procédé de communication

Publications (1)

Publication Number Publication Date
WO2024004160A1 true WO2024004160A1 (fr) 2024-01-04

Family

ID=89382523

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/026345 WO2024004160A1 (fr) 2022-06-30 2022-06-30 Nœud de réseau et procédé de communication

Country Status (1)

Country Link
WO (1) WO2024004160A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021095655A1 (fr) * 2019-11-11 2021-05-20 Nec Corporation Système et procédé pour permettre les politiques et la facturation d'un équipement d'utilisateur présentant une ou plusieurs identités d'utilisateur

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021095655A1 (fr) * 2019-11-11 2021-05-20 Nec Corporation Système et procédé pour permettre les politiques et la facturation d'un équipement d'utilisateur présentant une ou plusieurs identités d'utilisateur

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NEC: "KI#2 Sol#15: Editor’s Note on the Application privacy resolution in Solution 15", 3GPP DRAFT; S2-2204830, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. 20220516 - 20220520, 21 May 2022 (2022-05-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052160316 *

Similar Documents

Publication Publication Date Title
WO2024004160A1 (fr) Nœud de réseau et procédé de communication
WO2023218509A1 (fr) Nœud de réseau, système de communication sans fil, et procédé de communication
WO2024004156A1 (fr) Nœud de réseau, station de base et procédé de communication
WO2024057549A1 (fr) Nœud de réseau et procédé de communication
WO2024062583A1 (fr) Nœud de réseau et procédé de communication
WO2024062582A1 (fr) Nœud de réseau, système de communication, et procédé de communication
WO2024057550A1 (fr) Nœud réseau, système de communication, et procédé de communication
WO2023218671A1 (fr) Nœud de réseau et procédé de communication
WO2023218880A1 (fr) Terminal et procédé de communication
WO2024033986A1 (fr) Station de base et procédé de communication
WO2024034075A1 (fr) Station de base, terminal, nœud de réseau et procédé de communication
WO2024034135A1 (fr) Nœud de réseau et procédé d'autorisation
WO2024034101A1 (fr) Terminal et procédé de communication
WO2023218670A1 (fr) Nœud de réseau et procédé de communication
WO2024034102A1 (fr) Terminal et procédé de communication
WO2023181421A1 (fr) Terminal, station de base et procédé de communication
WO2023223511A1 (fr) Nœud de réseau et procédé de communication
WO2023195111A1 (fr) Nœud de réseau et procédé de communication
WO2023199526A1 (fr) Terminal, station de base et procédé de communication
WO2023223512A1 (fr) Nœud de réseau et procédé de communication
WO2024095490A1 (fr) Nœud de réseau et procédé de communication
WO2024038483A1 (fr) Nœud réseau et procédé de commande de synchronisation
WO2023210012A1 (fr) Terminal, station de base et procédé de communication
WO2023203624A1 (fr) Terminal, station de base et procédé de communication
WO2024038482A1 (fr) Nœud de réseau et procédé de commande de synchronisation

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22949433

Country of ref document: EP

Kind code of ref document: A1