Network node and communication method

Abstract

A network node is provided with: a reception unit that, when a PDU session has been established, receives a session establishment request for communication with a network node that controls an application, the session establishment request including information identifying a user of the network node that controls the application; a control unit that determines whether or not to allow establishment of a session for communication with a network node that controls the application, in accordance with whether or not the PDU session is occupied by a user different from the user; and a transmission unit that, when the establishment of the session is permitted, transmits, to a network node that controls a device that processes user plane data, an instruction to permit transmission and reception of user plane data relating to the application.

Description

Technical Field

[0001] The present invention relates to a network node and a communication method in a wireless communication system. Background Art

[0002] In NR (New Radio) (also called "5G"), which is the successor system to LTE (Long Term Evolution), the network architecture including 5GC (5G Core Network) corresponding to the core network in the network architecture of LTE (Long Term Evolution), namely EPC (Evolved Packet Core), and NG-RAN (Next Generation-Radio Access Network) corresponding to RAN (Radio Access Network) in the network architecture of LTE, namely E-UTRAN (Evolved Universal Terrestrial Radio Access Network) is studied (for example, non-patent document 1 and non-patent document 2).

[0003] In addition, in future systems such as 6G, a mechanism for realizing terminals shared by multiple users is being studied. For example, a scenario is envisioned in which when a person approaches a shared terminal on a street corner, the application server used by the person causes application data to flow to the terminal.

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS23.501 V17.2.0 (2021-09)

[0007] Non-patent document 2: 3GPP TS23.502 V17.2.1 (2021-09) Summary of the invention

[0008] Problems to be solved by the invention

[0009] In the past, authentication devices and the like detected when a person approached a shared terminal and notified the AF (e.g., an application server). The AF caused the AF's data to flow to the shared terminal. A mechanism for charging according to the AF's data usage is being studied. However, there is a problem that exclusive control cannot be performed to identify the user, for example, other application servers of others can also cause other application data to flow to the terminal at the same time.

[0010] The present invention has been made in view of the above-mentioned points, and an object of the present invention is to realize appropriate exclusive control in a terminal shared by a plurality of users in a wireless communication system.

[0011] Means for solving problems

[0012] According to the disclosed technology, a network node is provided, wherein the network node comprises: a receiving unit, which receives a session establishment request for communication with a network node that controls an application when a PDU session is established, the session establishment request including information identifying a user of the network node that controls the application; a control unit, which determines whether to allow establishment of a session for communication with the network node that controls the application based on whether the PDU session is occupied by a user different from the user; and a sending unit, which sends an indication of allowing reception and transmission of user plane data related to the application to the network node that controls a device that processes user plane data when the session establishment is allowed.

[0013] Effects of the Invention

[0014] According to the disclosed technology, a technology capable of realizing appropriate exclusive control in a terminal shared by a plurality of users in a wireless communication system is provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a diagram for explaining a wireless communication system involved in an embodiment of the present invention.

[0016] Figure 2 This is a diagram showing an example of a configuration of a wireless communication system according to an embodiment of the present invention.

[0017] Figure 3 This is a sequence diagram showing an example of the flow of the terminal preparation process according to the embodiment of the present invention.

[0018] Figure 4 This is a first sequence diagram showing an example of the flow of a data transmission process according to an embodiment of the present invention.

[0019] Figure 5 This is a second sequence diagram showing an example of the flow of the data transmission process according to the embodiment of the present invention.

[0020] Figure 6 This is a third sequence diagram showing an example of the flow of the data transmission process according to the embodiment of the present invention.

[0021] Figure 7 This is a fourth sequence diagram showing an example of the flow of the data transmission process according to the embodiment of the present invention.

[0022] Figure 8 This is a sequence diagram showing an example of the flow of the data transmission end process involved in the embodiment of the present invention.

[0023] Fig. 9 This is a diagram showing an example of a functional configuration of a base station according to an embodiment of the present invention.

[0024] Fig.10 This is a diagram showing an example of a functional configuration of a terminal according to an embodiment of the present invention.

[0025] Fig.11 This is a diagram showing an example of a hardware configuration of a base station or a terminal according to an embodiment of the present invention.

[0026] Fig.12 It is a diagram showing an example of the structure of a vehicle according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In addition, the embodiment described below is only an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0028] In the operation of the wireless communication system of the embodiment of the present invention, existing technologies can be appropriately used. The existing technologies are, for example, existing NR or LTE, but are not limited to existing NR or LTE. In addition, unless otherwise specified, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and subsequent methods (for example: NR).

[0029] In addition, in the embodiments of the present invention described below, the terms SS (Synchronization Signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), etc. used in the existing LTE are used. These are for the convenience of recording, and the same signals, functions, etc. may also be referred to by other names. In addition, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used for NR are not necessarily clearly recorded as "NR-".

[0030] Furthermore, in the embodiments of the present invention, the duplexing method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0031] Furthermore, in the embodiments of the present invention, “configuring” wireless parameters and the like may be pre-configuring predetermined values, or may be configuring wireless parameters notified from a base station or a terminal.

[0032] (System Structure)

[0033] Figure 1 It is a diagram for explaining a wireless communication system involved in an embodiment of the present invention.

[0034] like Figure 1 As shown, the wireless communication system involved in the embodiment of the present invention includes a base station 10 and a terminal 20. Figure 1Although one base station 10 and one terminal 20 are shown in each figure, this is only an example and there may be a plurality of base stations 10 and a plurality of terminals 20.

[0035] 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 the wireless signal are defined by the time domain and the frequency domain. The time domain can be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain can be defined by the number of subcarriers or resource blocks. In addition, the TTI (Transmission Time Interval) in the time domain can be a time slot, and the TTI can be a subframe.

[0036] The base station 10 sends a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is, for example, sent via NR-PBCH, also called broadcast information. The synchronization signal and system information may also be referred to as SSB (SS / PBCH block). Figure 1 As shown, the base station 10 sends a control signal or data to the terminal 20 via DL (Downlink), and receives a control signal or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 can perform beamforming to send and receive signals. In addition, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output)-based communications to DL or UL. In addition, the base station 10 and the terminal 20 can also communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) based on CA (Carrier Aggregation). Furthermore, the terminal 20 can also communicate via the primary cell of the base station 10 based on DC (Dual Connectivity) and the primary and secondary cell group cells (PSCell: Primary SCG Cell) of other base stations 10.

[0037] The terminal 20 is a communication device having a wireless communication function, such as a smart phone, a mobile phone, a tablet computer, a wearable terminal, or an M2M (Machine-to-Machine) communication module. Figure 1As shown, the terminal 20 receives a control signal or data from the base station 10 via DL and sends a control signal or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. In addition, the terminal 20 receives various reference signals sent from the base station 10 and performs a measurement of the propagation path quality based on the reception result of the reference signal. In addition, the terminal 20 may also be referred to as a UE and the base station 10 may also be referred to as a gNB.

[0038] Figure 2 1 is a diagram showing an example of a 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 .

[0039] The core network 30 is a network including switches, subscriber information management devices, etc. The core network 30 includes a network node group that realizes the U-Plane function and a network node group that realizes the C-Plane function group.

[0040] The U-Plane function is a function that performs the sending and receiving processing of user data. A network node that implements the U-Plane function is, for example, UPF (User plane function) 380. UPF380 is a network node that has functions such as an external PDU (Protocol Data Unit) session point for interconnection with DN40, routing and forwarding of packets, and QoS (Quality of Service) processing of the user plane. UPF380 controls the sending and receiving of data between DN40 and terminal 20. UPF380 and DN40 can be composed of one or more network slices.

[0041] The C-Plane function group is a function group that performs a series of control processes for establishing communication, etc. The network node group that realizes the C-Plane function group includes, for example, AMF (Access and Mobility Management Function) 310, UDM (Unified Data Management) 320, NEF (Network Exposure Function) 330, NRF (Network Repository Function) 340, AUSF (Authentication Server Function) 350, PCF (Policy Control Function) 360, SMF (Session Management Function) 370, and AF (Application Function) 390.

[0042] AMF310 is a network node with functions such as a terminal of a RAN interface, a terminal of a NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. NRF340 is a network node with a function of discovering NF (Network Function) instances that provide services. UDM320 is a network node that manages subscriber data and authentication data. UDM320 includes a UDR (User Data Repository) 321 and a FE (Front End) 322 that maintain the data. FE322 processes subscriber information.

[0043] SMF370 is a network node with functions such as session management, IP (Internet Protocol) address allocation and management of the terminal 20, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, roaming function, etc. NEF330 is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. PCF360 is a network node with the function of performing network policy control.

[0044] AF (Application Function) 390 is a network node having a function of controlling an application server.

[0045] AMF 310 and RAN 10 are communicably connected as an N2 link. In addition, UPF 380 and RAN 10 are communicably connected as an N3 link. UPF 380 and SMF 370 are communicably connected as an N4 link. UPF 380 and DN 40 are communicably connected as an N6 link.

[0046] Next, an example envisioned in this embodiment is described. For example, the terminal 20 is a terminal shared by multiple users. The terminal 20 can also be set up at a street corner. When one of the multiple users approaches the terminal 20, the AF390 sends data (application data, etc.) related to the user to the terminal 20. As a result, the terminal 20 can perform actions for the user, such as displaying information related to the installation area of ​​the terminal 20 in accordance with the user's preferences.

[0047] Next, the shared PDU session is described. For one or more terminals 20, a shared PDU session is established in each terminal 20. Multiple users share the shared PDU session established for each terminal 20. Here, in the previous specifications, when multiple users approach the terminal 20 at the same time, data related to the multiple users is sent to the terminal 20. Therefore, in this embodiment, the following mechanism (exclusive control) is implemented: while one user approaches the terminal 20 and uses the data related to the user, other users cannot use the terminal 20.

[0048] Specifically, the following contents are defined in the context information of the PDU session maintained by SMF370 and PCF360 and the information used for registration with the SMF of the UDM.

[0049] Shared PDU session display

[0050] PDU session lock status

[0051] The shared PDU session display is information indicating whether the PDU session is a session shared by multiple users.

[0052] The PDU session lock status includes the following information:

[0053] ·Whether there is lock

[0054] Occupancy type

[0055] The presence or absence of lock is information indicating either "not locked" or "locked". When the presence or absence of lock indicates "not locked", the information indicating the PDU session lock state is only the presence or absence of lock. On the other hand, when the presence or absence of lock is "locked", the information indicating the PDU session lock state includes information indicating the occupancy type.

[0056] The occupancy type is information showing any one of AF session occupancy, AF occupancy, and AF group occupancy.

[0057] The AF session occupancy is information indicating that the AF session is occupied (AF session in use).

[0058] AF occupancy is information indicating AF occupancy, including AF in use, AF session in use, user's AF internal identifier, etc. AF in use is information indicating AF390 in use, for example, represented as "afAppId" as before. The user's AF internal identifier is an identifier used to identify the user in AF390, for example, represented as "uid@afAppId". In addition, "uid" is the part that identifies the user, and "@afAppId" is the part that represents AF390.

[0059] The identifier indicating the user is managed by AF390. Therefore, the user is a concept defined in AF390 and is different from the subscriber of the terminal 20. The subscriber of the terminal 20 may be, for example, a carrier that provides the functions or services of the terminal 20 to the user.

[0060] AF group occupancy is information indicating the occupancy of the group to which AF390 belongs, including the AF group in use, AF in use, AF session in use, user's AF group internal identifier, etc. The AF group in use is information indicating the group to which AF390 in use belongs, for example, represented as "afAppGid". The user's AF group internal identifier is an identifier used to identify the user in the group to which AF390 belongs, for example, represented as "uid@afAppGid". In addition, "uid" is the part that identifies the user, and "@afAppGid" is the part that indicates the group to which AF390 belongs.

[0061] In addition, a shared PDU session accommodating SMF registration event disclosure service is introduced in UDM320. The shared PDU session accommodating SMF registration event disclosure service is a function for disclosing (notifying) the occurrence of an event of the SMF370 that registers and accommodates the shared PDU session. UDM320 notifies the network nodes that have subscribed to the shared PDU session accommodating SMF registration event disclosure service of the occurrence of the event of the registered SMF370.

[0062] Furthermore, in this embodiment, a PDU session lock request (AF session occupied, AF occupied, AF group occupied), an identifier for identifying AF390 and the group to which AF390 belongs ("afAppId", "afAppGid"), and an identifier for identifying a user ("uid@afAppId", "uid@afAppGid") are added to the input parameters of the existing AF session establishment request with QoS request. The AF session establishment request with QoS request is a request specified in the previous specification, and is a request for establishing an AF session accompanied by a QoS request.

[0063] Next, a preparation procedure for using the terminal 20 will be described.

[0064] Figure 3 1 is a sequence diagram showing an example of the process of the terminal preparation process involved in the embodiment of the present invention. When there are multiple AF390s, the following process is performed for each AF390. In the following, the first AF390-1, the second AF390-2 and the third AF390-3 are assumed. Figure 3 An example of the AF390 is shown, but in the following description, the first AF390-1, the second AF390-2, and the third AF390-3 perform the preparation process respectively.

[0065] AF390 sends a subscription request to UDM320 to register the event disclosure service to the shared PDU session accommodating SMF (step S101). Terminal 20 sends a PDU session establishment request including a shared PDU session display to SMF370 (step S102).

[0066] Next, the SMF 370 sends a request for subscriber information to the UDM 320 (step S103 ), and receives a response for the subscriber information (step S104 ).

[0067] Next, SMF370 sends "SmPolicyContextData" including shared PDU session display to PCF360 (step S105). PCF360 sends "SMPolicyDecision" including PDU session rule (shared PDU session display, PDU session lock state = unlocked) and default PCC rule (gate state = closed) to SMF370 (step S106). Here, "gate state = closed" is a setting that the PDU session is established but data packets are not passed.

[0068] in addition, Figure 3The example in which the SMF 370 receives the shared PDU session display from the terminal 20 is shown. In addition, the SMF 370 may receive the display set in the subscriber information from the UDM 320 instead of receiving the display from the terminal 20. In addition, the SMF 370 may receive the display set in "SMPolicyDecision" from the PCF 360 instead of receiving the display from the terminal 20 or the UDM 320.

[0069] In addition, the above default PCC rule may be a PCC rule that matches a service data flow with a wildcard.

[0070] Next, SMF370 sends a PFCP session establishment request including "door status = closed" to UPF380 (step S107). SMF370 sends a SMF registration request to UDM320 regarding the PDU session, including shared PDU session display, PDU session lock status = unlocked, terminal location information, IP address, etc. (step S108).

[0071] Then, the PDU session establishment is completed (step S109). UDM320 notifies AF390 that there is a shared PDU session accommodating SMF registration in AF390 including shared PDU session display, PDU session lock status = unlocked, terminal location information, IP address, etc.

[0072] In addition, the AF 390 may be implemented in various forms, such as an application server, an application in a user container, an application in a user terminal, etc.

[0073] Next, the process of sending data by AF390 is explained.

[0074] Figure 4 This is a first sequence diagram showing an example of the flow of a data transmission process according to an embodiment of the present invention. Figure 4 An example of a first AF 390 - 1 is shown.

[0075] DN40 notifies the first AF390-1 that the first user is approaching the terminal 20 (step S201). For example, the approach of the user is detected by a sensor included in DN40 and a computer device connected to the sensor, and the user is determined to be the first user through facial recognition, etc. Such a method of notifying the approach is an example, and other methods may also be used.

[0076] The first AF 390-1 sends an AF session establishment request with a QoS request including its own identifier (e.g., afAppId=AF1, afAppGid=AFGx), the user's AF group identifier (uid@afAppGid=abc@AFGx), and the IP address of the PDU session to the PCF 360 (step S202). In addition, the PDU session lock request specifies AF group occupation as supplementary information. The supplementary information specifies any one of AF session occupation, AF occupation, and AF group occupation.

[0077] Next, regarding the PDU session, the PCF 360 recognizes that (PDU session lock status = unlocked), and sends a response to the AF session establishment permission request including (appSessionId = AF session 1) to the first AF 390 - 1 (step S203 ).

[0078] Next, the first AF 390 - 1 uses (appSessionId=AF Session 1 ) to request event subscription from the PCF 360 (step S204 ).

[0079] PCF360 sends PDU session rule update information and PCC rule 1 to SMF370 (step S205). The PDU session rule update information includes PDU session lock status = locked (AF group occupied (AF group in use = AFGx, AF in use = AF1, AF session in use = AF1: AF session 1, user's AF group internal identifier = abc@AFGx)). In addition, PCC rule 1 is a rule that sets the door state = open with respect to the service data flow specified by the first AF390-1 in the AF session establishment request.

[0080] Regarding the PDU session, SMF 370 sends an SMF registration update request including (PDU session lock status = locked) to UDM 320 (step S206). The information indicating (PDU session lock status = locked) includes AF group occupancy (AF group in use = AFGx, AF in use = AF1, AF session in use = AF1: AF session 1, user's AF group internal identifier = abc@AFGx).

[0081] Next, the SMF 370 sends a PFCP session change request including door status = open to the UPF 380 regarding the service data flow specified by the first AF 390-1 (step S207). As described above, exclusive control is performed in the order from locking to selective release of the door.

[0082] Then, the PDU session change is completed (step S208). The PCF 360 sends an event notification to the first AF 390-1 (step S209). The first AF 390-1 transmits (sends) AF data to the terminal 20 (step S210).

[0083] Figure 5 This is a second sequence diagram showing an example of the flow of the data transmission process according to the embodiment of the present invention. Figure 5 Shown in execution Figure 4 1. An example of a second AF 390-2 after the process of FIG. 390-2. The second AF 390-2 belongs to the same group (AFGx) as the first AF 390-1.

[0084] UDM320 notifies the second AF390-2 of information indicating that there is a shared PDU session accommodating SMF registration modification (change) and (PDU session lock state = locked) (step S301). The information indicating (PDU session lock state = locked) includes AF group occupancy (AF group in use = AFGx, AF in use = AF1, AF session in use = AF1: AF session 1, user's AF group internal identifier = abc@AFGx).

[0085] DN40 notifies the second AF390-2 that the first user is close to the terminal 20 (step S302). For example, the approach of the user is detected by a sensor included in DN40 and a computer device connected to the sensor, and the user is determined to be the first user through facial recognition. Such a method of notifying the approach is an example, and other methods may also be used. In addition, the second AF390-2 may also determine that the first user is close to the terminal 20 based on the receipt of the notification of step S301.

[0086] The second AF 390-2 sends an AF session establishment request with a QoS request including its own identifier (e.g., afAppId=AF2, afAppGid=AFGx), the user's AF group identifier (uid@afAppGid=abc@AFGx), and the IP address of the PDU session to the PCF 360 (step S303). In addition, the PDU session lock request specifies AF group occupation as additional information.

[0087] Next, regarding the PDU session, PCF360 identifies it as (PDU session lock status = locked), and sends a response to the request to allow AF session establishment including (appSessionId = AF session 2) to the second AF390-2 (step S304). The information indicating (PDU session lock status = locked) includes AF group occupancy (AF group in use = AFGx, AF in use = AF1, AF session in use = AF1:AF session 1, user's AF group internal identifier = abc@AFGx). Here, when AF group occupancy is specified and the PDU session is based on the AF group occupancy of the specified group, PCF360 allows the AF session to be established when the same user belonging to the occupied AF group is approaching.

[0088] Next, the second AF 390 - 2 requests event subscription from the PCF 360 using (appSessionId=AF Session 2) (step S305 ).

[0089] PCF360 sends PDU session rule update information and PCC rule 2 to SMF370 (step S306). The PDU session rule update information includes PDU session lock status = locked (AF group occupied (AF group in use = AFGx, AF in use = AF1, AF2, AF session in use = AF1: AF session 1, AF2: AF session 2, user's AF group internal identifier = abc@AFGx)). In addition, PCC rule 2 is a rule that sets the door state = open for the service data flow specified by the second AF390-2 in the AF session establishment request.

[0090] SMF370 sends an SMF registration update request including (PDU session lock status = locked) to UDM320 regarding the PDU session (step S307). Information indicating (PDU session lock status = locked) includes AF group occupancy (AF group in use = AFGx, AF in use = AF1, AF2, AF session in use = AF1: AF session 1, AF2: AF session 2, user's AF group internal identifier = abc@AFGx).

[0091] Next, SMF370 sends a PFCP session change request including door status = open to UPF380 regarding the service data flow specified by the second AF390-2 (step S308).

[0092] Then, the PDU session change is completed (step S309). The PCF 360 sends an event notification to the second AF 390-2 (step S310). The second AF 390-2 transmits (sends) AF data to the terminal 20 (step S311).

[0093] Figure 6This is a third sequence diagram showing an example of the flow of the data transmission process according to the embodiment of the present invention. Figure 6 Shows that in the implementation Figure 5 The third AF390-3 does not belong to the same group (AFGx) as the first AF390-1.

[0094] The UDM 320 notifies the third AF 390 - 3 of information indicating that there is a shared PDU session accommodating SMF registration modification (change) and (PDU session lock state = locked) (step S401 ).

[0095] DN40 notifies the third AF390-3 that the first user is approaching the terminal 20 (step S402). For example, the approach of the user is detected by a sensor included in DN40 and a computer device connected to the sensor, and the user is determined to be the first user through facial recognition, etc. Such a method of notifying the approach is an example, and other methods may also be used.

[0096] The third AF 390-3 sends an AF session establishment request with a QoS request including its own identifier (e.g., afAppId=AF3, afAppGid=AFGx), the user's AF group identifier (uid@afAppGid=abc@AFGx), and the IP address of the PDU session to the PCF 360 (step S403). In addition, the PDU session lock request specifies AF occupation as additional information.

[0097] Here, the third AF 390-3 may determine that the AF belonging to another group occupies the shared PDU session based on the information indicating (PDU session lock state = locked), and does not send an AF session establishment request to the PCF 360. In this case, the data transmission process ends.

[0098] Next, the PCF 360 identifies the PDU session as (PDU session lock state = locked), and sends a response to the third AF 390-3 rejecting the AF session establishment request (step S404). The information indicating (PDU session lock state = locked) includes AF group occupation (AF group in use = AFGx, AF in use = AF1, AF2, AF session in use = AF1: AF session 1, AF2: AF session 2, user's AF group internal identifier = abc@AFGx).

[0099] Here, PCF360 rejects AF session establishment when AF occupation is specified and the PDU session is AF group occupation (i.e., when the specified occupation type is different from the occupation type in occupation). In addition, PCF360 may reject AF session establishment when AF group occupation is specified and the PDU session is AF group occupation based on a group different from the specified group.

[0100] Figure 7 This is a fourth sequence diagram showing an example of the flow of the data transmission process according to the embodiment of the invention. Figure 7 Shows that the execution Figure 5 or Figure 6 This is an example of a case where a second user different from the first user approaches the terminal 20 after the process.

[0101] UDM320 notifies the first AF390-1 of information indicating that there is a shared PDU session accommodating SMF registration modification (change) and (PDU session lock state = locked) (step S501). The information indicating (PDU session lock state = locked) includes AF group occupancy (AF group in use = AFGx, AF in use = AF1, AF2, AF session in use = AF1: AF session 1, AF2: AF session 2, user's AF group internal identifier = abc@AFGx).

[0102] DN40 notifies the first AF390-1 that the second user is approaching the terminal 20 (step S502). For example, the approach of the user is detected by a sensor included in DN40 and a computer device connected to the sensor, and the user is determined to be the second user through facial recognition, etc. Such a method of notifying the approach is an example, and other methods may also be used.

[0103] The first AF 390-1 sends an AF session establishment request with a QoS request including its own identifier (e.g., afAppId=AF1, afAppGid=AFGx), the user's AF group identifier (uid@afAppGid=def@AFGx), and the IP address of the PDU session to the PCF 360 (step S503). In addition, the PDU session lock request specifies AF group occupation as additional information.

[0104] Here, the first AF 390-1 may also determine that the data is occupied by another user based on the information indicating (PDU session lock status = locked), and does not send an AF session establishment request to the PCF 360. In this case, the data transmission process ends.

[0105] Next, the PCF 360 identifies the PDU session as (PDU session lock state = locked), and sends a response to the first AF 390-1 rejecting the AF session establishment request (step S504). The information indicating (PDU session lock state = locked) includes AF group occupation (AF group in use = AFGx, AF in use = AF1, AF2, AF session in use = AF1: AF session 1, AF2: AF session 2, user's AF group internal identifier = abc@AFGx).

[0106] Here, in the case of an approach by a user different from the occupied user, the PCF 360 rejects the AF session establishment.

[0107] In addition, the PCF 360 may reject the AF session establishment when the AF session occupation is designated and the occupied PDU session is an AF session different from the designated AF session.

[0108] Next, the process of ending data transmission is described.

[0109] Figure 8 This is a sequence diagram showing an example of the flow of the data transmission end process according to the embodiment of the present invention: The first AF 390 - 1 sends an AF session release request to the PCF 360 using (appSessionId=AF session 1) (step S601 ).

[0110] PCF 360 identifies the PDU session as PDU session lock state = locked. Information indicating PDU session lock state = locked includes AF group occupation (AF group in use = AFGx, AF in use = AF1, AF2, AF session in use = AF1: AF session 1, AF2: AF session 2, user's AF group internal identifier = abc@AFGx).

[0111] PCF360 sends PDU session rule update information and a deletion indication of PCC rule 1 to SMF370 (step S602). The PDU session rule update information includes PDU session lock status = locked (AF group occupied (AF group in use = AFGx, AF in use = AF2, AF session in use = AF2: AF session 2, user's AF group internal identifier = abc@AFGx)).

[0112] SMF 370 sends a PFCP session change request to UPF 380 (step S603). The PFCP session change request is a request to instruct to delete the setting of gate status = open related to the service data flow specified by AF1.

[0113] SMF370 sends an SMF registration update request including (PDU session lock status = locked) to UDM320 regarding the PDU session (step S604). The information indicating (PDU session lock status = locked) includes AF group occupancy (AF group in use = AFGx, AF in use = AF2, AF session in use = AF2: AF session 2, user's AF group internal identifier = abc@AFGx).

[0114] As described above, the exclusive control is performed in the order from the closing of the corresponding door to the change of the occupancy information related to the lock. Then, the PDU session change is completed (step S605).

[0115] Next, the process of the second AF390-2 ending data transmission is described. Figure 8 The process is the same as that shown in FIG. 6 , and the data transmission is terminated. Specifically, in step S601 , the second AF 390 - 2 sends an AF session release request to the PCF 360 using (appSessionId=AF session 2).

[0116] PCF 360 identifies the PDU session as PDU session lock state = locked. Information indicating PDU session lock state = locked includes AF group occupation (AF group in use = AFGx, AF in use = AF2, AF session in use = AF2: AF session 2, user's AF group internal identifier = abc@AFGx).

[0117] Next, in step S602, PCF 360 sends PDU session rule update information and a deletion indication of PCC rule 2 to SMF 370. The PDU session rule update information includes (PDU session lock status = not locked).

[0118] In the next step S603, SMF 370 sends a PFCP session change request to UPF 380. The PFCP session change request is a request to instruct to delete the setting of gate status = open related to the service data flow specified by AF2.

[0119] In the next step S604, SMF370 sends an SMF registration update request including (PDU session lock status = unlocked) to UDM320 regarding the PDU session.

[0120] As described above, the exclusive control is performed in the order from the closing of the door to the unlocking of the door. Then, in step S605, the PDU session change is completed.

[0121] According to this embodiment, in a shared PDU session shared by multiple users, simultaneous use by multiple users can be avoided by performing exclusive control. Thus, appropriate exclusive control can be implemented in a terminal shared by multiple users in a wireless communication system.

[0122] (Device Structure)

[0123] Next, the functional configuration examples of the base station 10, the terminal 20, and various network nodes that implement the above-mentioned processing and operation will be described. The base station 10, the terminal 20, and various network nodes include functions for implementing the above-mentioned embodiments. However, the base station 10, the terminal 20, and various network nodes may also only have a part of the functions in the embodiments.

[0124] <Base Station 10 and Network Node>

[0125] Fig. 9 1 is a diagram showing an example of the functional configuration of the base station 10. Fig. 9 As shown, the base station 10 includes a transmission unit 110 , a reception unit 120 , a setting unit 130 , and a control unit 140 . Fig. 9 The functional structure shown is only an example. As long as the actions of the embodiments of the present invention can be implemented, the functional division and the name of the functional unit can be arbitrary. In addition, the network node can also have the same functional structure as the base station 10. In addition, a network node having multiple different functions in the system architecture can also be composed of multiple network nodes separated by function.

[0126] The transmitter 110 includes a function of generating a signal to be sent to the terminal 20 or other network nodes and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals sent from the terminal 20 or other network nodes and obtaining, for example, higher layer information from the received signals.

[0127] The setting unit 130 stores in a storage device the setting information set in advance and various setting information to be transmitted to the terminal 20, and reads out from the storage device as needed. The content of the setting information is, for example, setting related to communication using the NTN.

[0128] As described in the embodiment, the control unit 140 performs processing related to communication using the NTN. In addition, the control unit 140 performs processing related to communication with the terminal 20. In addition, the control unit 140 performs processing related to geographical location verification of the terminal 20. The functional unit related to signal transmission in the control unit 140 may be included in the transmission unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the reception unit 120.

[0129] <Terminal 20>

[0130] Fig.10 2 is a diagram showing an example of the functional structure of the terminal 20. Fig.10 As shown, the terminal 20 includes a transmitting unit 210 , a receiving unit 220 , a setting unit 230 , and a control unit 240 . Fig.10 The functional structure shown is only an example. As long as the operation of the embodiment of the present invention can be implemented, the functional division and the name of the functional unit can be arbitrary. The USIM installed in the terminal 20 can also have a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240 in the same manner as the terminal 20.

[0131] The transmitting unit 210 generates a transmission signal according to the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 receives various signals wirelessly and obtains a higher layer signal from the received physical layer signal. In addition, the receiving unit 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, etc. sent from the network node.

[0132] 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 out from the storage device as needed. In addition, the setting unit 230 also stores pre-set setting information.

[0133] The network node of this embodiment may also be configured as the network node shown in the following items. In addition, the following communication method may also be implemented.

[0134] <Structure Related to This Embodiment>

[0135] (Item 1)

[0136] A network node, wherein the network node has:

[0137] a receiving unit for receiving, when a PDU session is established, a session establishment request for communication with a network node controlling an application, the session establishment request including information identifying a user of the network node controlling the application;

[0138] a control unit that determines whether to allow establishment of a session for communication with a network node controlling the application, according to whether the PDU session is occupied by a user different from the user; and

[0139] A sending unit is configured to send an indication of allowing the sending and receiving of user plane data related to the application to a network node that controls an apparatus for processing user plane data, if the establishment of the session is allowed.

[0140] (Item 2)

[0141] The network node according to item 1, wherein the information identifying the user is managed for each network node controlling the application,

[0142] The receiving unit receives a session establishment request for communication with a network node controlling the application, the session establishment request including information identifying the network node controlling the application,

[0143] The control unit determines whether to allow establishment of a session for communication with a network node controlling the application, according to whether the PDU session is occupied by a network node controlling an application different from the network node controlling the application.

[0144] (Item 3)

[0145] The network node according to item 1 or 2, wherein the information identifying the user is managed for each group to which the network node controlling the application belongs,

[0146] The receiving unit receives a session establishment request for communication with the network node controlling the application, the session establishment request including information identifying a group to which the network node controlling the application belongs.

[0147] The control unit determines whether to permit establishment of a session for communication with a network node controlling the application, according to whether the PDU session is occupied by a group different from the group.

[0148] (Item 4)

[0149] A communication method performed by a network node, wherein the communication method comprises the following steps: receiving a session establishment request for communication with a network node controlling an application when a PDU session is established, the session establishment request comprising information identifying a user of the network node controlling the application;

[0150] determining whether to allow establishment of a session for communication with a network node controlling the application according to whether the PDU session is occupied by a user different from the user; and

[0151] In the case where the session establishment is allowed, an indication of allowing the transmission and reception of user plane data related to the application is sent to a network node that controls the device for processing user plane data.

[0152] According to any of the above structures, a technology capable of implementing appropriate exclusive control in a terminal shared by multiple users in a wireless communication system is provided. According to the first item, it is possible to determine whether to allow the establishment of a session for communication with a network node of a control application based on whether the PDU session is occupied by a user different from the user. According to the second item, it is possible to determine whether to allow the establishment of a session for communication with a network node of a control application based on whether the PDU session is occupied by a network node of a control application different from the network node of the control application. According to the third item, it is possible to determine whether to allow the establishment of a session for communication with a network node of a control application based on whether the PDU session is occupied by a group different from the group.

[0153] (Hardware Structure)

[0154] The block diagram used in the description of the above embodiment ( Fig. 9 and Fig.10 ) shows blocks in units of functions. These functional blocks (structural parts) are implemented by any combination of at least one of hardware and software. In addition, there is no particular limitation on the implementation method of each functional block. That is, each functional block can be implemented using a device that is physically or logically combined, or two or more physically or logically separated devices can be directly or indirectly connected (for example, using wires, wirelessly, etc.) and implemented using these multiple devices. The functional blocks can also be implemented by combining software in the above-mentioned one device or the above-mentioned multiple devices.

[0155] Functions include judging, determining, judging, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, a functional block (structural unit) that enables the transmission function is called a transmitting unit or a transmitter. In short, as mentioned above, there is no particular limitation on the implementation method.

[0156] For example, the network node, the terminal 20, etc. in one embodiment of the present disclosure may also function as a computer that performs the processing of the wireless communication method of the present disclosure. Fig.111 is a diagram showing an example of the hardware structure of the base station 10 and the terminal 20 involved in one embodiment of the present disclosure. The network node may have the same hardware structure as the base station 10. The USIM may also have the same hardware structure as the terminal 20. The base station 10 and the terminal 20 may also be configured as a computer device that physically includes a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0157] In the following description, the word "device" may be replaced by "circuit", "device", "unit", etc. The hardware configuration of the base station 10 and the terminal 20 may include one or more of the devices shown in the figure, or may exclude some of the devices.

[0158] Each function in the base station 10 and the terminal 20 is implemented by the following method: predetermined software (program) is read into hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs calculations and controls the communication of the communication device 1004 or controls at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0159] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, a computing device, registers, etc. For example, the control unit 140, the control unit 240, etc. may also be implemented by the processor 1001.

[0160] In addition, the processor 1001 reads a program (program code), a software module, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and performs various processes accordingly. As a program, a program that causes the computer to execute at least a part of the actions described in the above embodiments is used. For example, Fig. 9 The control unit 140 of the base station 10 shown may also be implemented by a control program stored in the storage device 1002 and executed in the processor 1001. For example, Fig.10 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it is described that the above-mentioned various processes are performed by one processor 1001, the above-mentioned various processes can also be performed simultaneously or sequentially by more than two processors 1001. The processor 1001 can also be implemented by more than one chip. In addition, the program can also be sent from the network via a telecommunication line.

[0161] The storage device 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing the communication method involved in one embodiment of the present disclosure.

[0162] The auxiliary storage device 1003 is a computer-readable recording medium, and may be composed of at least one of an optical disk such as a CD-ROM (CompactDisc ROM), a hard disk drive, a floppy disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk, a smart card, a flash memory (e.g., a card, a stick, a key drive), a Floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, and other appropriate media including at least one of the storage device 1002 and the auxiliary storage device 1003.

[0163] The communication device 1004 is hardware (transceiver device) for communicating between computers via at least one of a wired network and a wireless network, and may also be referred to as a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may also be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to implement at least one of frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD: Time Division Duplex). For example, a transceiver antenna, an amplifier, a transceiver, a transmission path interface, etc. may also be implemented by the communication device 1004. The transceiver may also be implemented by physically or logically separating the transmitter and the receiver.

[0164] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that implements output to the outside (e.g., a display, a speaker, an LED light, etc.). In addition, the input device 1005 and the output device 1006 may also be integrally formed (e.g., a touch panel).

[0165] In addition, the processor 1001 and the storage device 1002 and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured by a single bus or may be configured by different buses between devices.

[0166] In addition, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and a part or all of each functional block may be implemented by the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0167] Fig.12 FIG. 2 shows a structural example of a vehicle 2001. Fig.12 As shown, the vehicle 2001 includes a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each mode / embodiment described in the present disclosure may also be applied to a communication device mounted on the vehicle 2001, for example, may also be applied to the communication module 2013.

[0168] The driving 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 a user.

[0169] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2029 included in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be referred to as an ECU (Electronic Control Unit).

[0170] As signals from various sensors 2021~2029, there are current signals from the current sensor 2021 that monitors the current of the motor, speed signals of the front wheels and rear wheels obtained by the speed sensor 2022, air pressure signals of the front wheels and rear wheels obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression amount signals obtained by the accelerator pedal sensor 2029, brake pedal depression amount signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, detection signals for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 2028, and the like.

[0171] The information service unit 2012 is composed of various devices such as a car navigation system, an audio system, a speaker, a television, and a radio for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013 and the like to provide various multimedia information and multimedia services to passengers of the vehicle 2001.

[0172] The information service unit 2012 may include input devices for receiving input from the outside (such as keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.), and may also include output devices for implementing output to the outside (such as displays, speakers, LED lights, touch panels, etc.).

[0173] The driving assistance system unit 2030 is composed of various devices for preventing accidents or reducing the driver's driving load, such as millimeter wave radar, LiDAR (Light Detection and Ranging), camera, positioning device (such as GNSS, etc.), map information (such as high-definition (HD) map, autonomous driving vehicle (AV) map, etc.), gyroscope system (such as IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chip, AI processor, and one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 sends and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0174] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 2001 via the communication port. For example, the communication module 2013 can send and receive data with the drive unit 2002, the steering unit 2003, the accelerator pedal 2004, the brake pedal 2005, the shift lever 2006, the front wheel 2007, the rear wheel 2008, the axle 2009, the microprocessor 2031 in the electronic control unit 2010, the memory (ROM, RAM) 2032, and the sensors 2021 to 29 via the communication port 2033.

[0175] The communication module 2013 can be controlled by the microprocessor 2031 of the electronic control unit 2010, and is a communication device that can communicate with an external device. For example, various information can be sent and received with the external device via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. The external device can also be, for example, a base station, a mobile station, etc.

[0176] The communication module 2013 may also transmit at least one of the signals from the various sensors 2021-2029 input to the electronic control unit 2010, the information obtained based on the signals, and the information based on the input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2029, the information service unit 2012, etc. may also be referred to as an input unit that receives input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0177] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from an external device, and displays it on the information service unit 2012 of the vehicle 2001. The information service unit 2012 may also be referred to as an output unit that outputs information (for example, outputs information to a display, a speaker, etc. based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0178] In addition, the communication module 2013 stores various information received from the external device in the memory 2032 that can be used by the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, the steering unit 2003, the accelerator pedal 2004, the brake pedal 2005, the shift lever 2006, the front wheel 2007, the rear wheel 2008, the axle 2009, the sensors 2021 to 2029, etc. of the vehicle 2001 based on the information stored in the memory 2032.

[0179] (Supplementary Implementation Methods)

[0180] The above is a description of the embodiments of the present invention, but the disclosed invention is not limited to such an embodiment, and those skilled in the art should understand various variations, modifications, substitutions, replacements, etc. In order to facilitate the understanding of the invention, specific numerical examples are used for description, but unless otherwise specified, these numerical values ​​are only examples, and any appropriate value may also be used. The item distinction in the above description is not essential to the present invention, and the items recorded in more than two items can be combined and used as needed, and the items recorded in a certain item can be applied to the items recorded in another item (as long as there is no contradiction). The boundaries of the functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of the physical components. The actions of multiple functional units can be performed by one physical component, or the actions of one functional unit can be performed by multiple physical components. Regarding the processing steps described in the embodiment, the order of processing can be swapped if there is no contradiction. In order to facilitate the description of the processing, the base station 10 and the terminal 20 are described using a functional block diagram, but such a device can also be implemented by hardware, software, or a combination thereof. The software that operates according to the implementation mode of the present invention through the processor of the base station 10 and the software that operates according to the implementation mode of the present invention through the processor of the terminal 20 can also be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server and any other appropriate storage medium.

[0181] In addition, the notification of information is not limited to the form / implementation method described in the present disclosure, and other methods may also be used. For example, the notification of information may be implemented through 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. In addition, RRC signaling may also be referred to as an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0182] The various modes and embodiments described in the present disclosure may also be applied to mobile communications systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), new radio access (NX), future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE At least one of 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), other appropriate systems, and next-generation systems that are expanded, modified, created, and specified based on these systems. In addition, multiple systems may be combined (for example, a combination of at least one of LTE and LTE-A and 5G, etc.) for application.

[0183] The processing steps, timing, and flow of each form / implementation described in this specification may be reversed in order if there is no contradiction. For example, the method described in this disclosure uses the order of examples to indicate the elements of various steps, but is not limited to the specific order indicated.

[0184] In this specification, specific actions performed by the base station 10 are sometimes also performed by its upper node according to the situation. In a network composed of one or more network nodes having the base station 10, various actions performed for communicating with the terminal 20 can be performed by at least one of the base station 10 and other network nodes other than the base station 10 (for example, MME or S-GW, etc., but not limited to these). In the above, the case where there is one other network node other than the base station 10 is illustrated, but the other network node may also be a combination of multiple other network nodes (for example, MME and S-GW).

[0185] The information or signals described in the present disclosure can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and can also be input or output via a plurality of network nodes.

[0186] The input or output information can be stored in a specific location (e.g., a memory) or managed using a management table. The input or output information can be rewritten, updated, or appended. The output information can also be deleted. The input information can also be sent to other devices.

[0187] The determination in the present disclosure may be performed by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparison of numerical values ​​(for example, comparison with a predetermined value).

[0188] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, shall be interpreted broadly to refer to commands, sets of commands, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0189] In addition, software, commands, information, etc. may also be sent and received via a transmission medium. For example, when software is sent from a web page, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

[0190] The information, signals, etc. described in the present disclosure may also be represented by any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc. that may be involved in the above description as a whole may also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0191] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may also be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may also be a signal (signaling). In addition, a signal may also be a message. In addition, a component carrier (CC) may also be referred to as a carrier frequency, a cell, a frequency carrier, etc.

[0192] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0193] In addition, the information, parameters, etc. described in the present disclosure may be represented by absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources may also be indicated by indexes.

[0194] The names used for the above parameters are non-restrictive in any respect. Furthermore, the formulas etc. using these parameters may sometimes differ from those explicitly disclosed in the present disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by all appropriate names, and therefore the various names assigned to these various channels and information elements are non-restrictive in any respect.

[0195] In the present invention, the terms "base station (BS)," "wireless base station", "base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier" and the like can be used interchangeably. Sometimes, the base station is also referred to as macro cell, small cell, micro-micro cell, micro-micro cell and the like.

[0196] A base station can accommodate one or more (for example, 3) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (for example, a small base station RRH: Remote Radio Head for indoor use). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of ​​at least one of the base station and the base station subsystem that provide communication services within the coverage area.

[0197] In the present disclosure, the base station sending information to the terminal may also be replaced by the base station instructing the terminal to perform a control / action based on the information.

[0198] In the present disclosure, terms such as “mobile station (MS)”, “user terminal (user terminal)”, “user equipment (UE)”, and “terminal” may be used interchangeably.

[0199] For mobile stations, those skilled in the art sometimes also use the following terms: 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 terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terms.

[0200] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. In addition, at least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to an object that can move, and the moving speed is arbitrary. In addition, of course, it also includes the case where the mobile body stops. The mobile body includes, for example, vehicles, transport vehicles, cars, motorcycles, bicycles, connected cars, shovel cars, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trailers (rear cars), rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones (registered trademark), multi-rotor helicopters (multicopters), quadcopters (quadcopters), balloons and objects mounted on them, and are not limited to these. In addition, the mobile body may also be a mobile body that drives autonomously based on operating instructions. It can be a means of transportation (such as a car, airplane, etc.), a mobile body that moves in an unmanned manner (such as a drone, an autonomous car, etc.), or a robot (manned or unmanned). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication. For example, at least one of the base station and the mobile station may also be an IoT (Internet of Things) device such as a sensor.

[0201] In addition, the base station in the present disclosure may also be replaced by a user terminal. For example, a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple terminals 20 (for example, it may also be referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) may also apply various forms / implementations of the present disclosure. In this case, it may also be configured that the terminal 20 has the functions possessed by the above-mentioned base station 10. In addition, terms such as "uplink" and "downlink" may also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. may also be replaced by side channels.

[0202] Likewise, the user terminal in the present disclosure may also be replaced by a base station. In this case, the base station may also have the functions of the user terminal.

[0203] The terms "determining" and "determining" used in the present disclosure sometimes also include a variety of actions. "Determining" and "determining" may include, for example, considering matters that have been judged, calculated, calculated, processed, derived, investigated, searched (for example, searched in a table, database or other data structure), confirmed (ascertaining) as matters that have been "determined" or "determined", etc. In addition, "determining" and "determining" may include matters that have been received (for example, receiving information), transmitted (for example, transmitting information), input, output, accessed (for example, accessing data in a memory) as matters that have been "determined" or "determined", etc. In addition, "determining" and "determining" may include matters that have been resolved (resolving), selected (selecting), chosen (choosing), established (establishing), compared (comparing), etc. as matters that have been "determined" or "determined". That is, "judgment" and "decision" may include matters that regard certain actions as "judgment" and "decision". In addition, "judgment (decision)" may also be replaced by "assuming", "expecting", "considering", etc.

[0204] The terms "connected", "coupled" or all variations of these terms are intended to indicate any direct or indirect connection or combination between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be a physical combination or connection, a logical combination or connection, or a combination of these. For example, "access" may be used instead of "connection". In the context of the present disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, and as some non-limiting and non-inclusive examples, electromagnetic energy having wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible) region may be used to "connect" or "couple" to each other.

[0205] The reference signal may be referred to as RS (Reference Signal) for short, or may be referred to as a pilot signal (Pilot) according to the applied standard.

[0206] The phrase "according to" used in the present disclosure does not mean "only according to" unless otherwise expressly stated. In other words, the phrase "according to" means both "only according to" and "at least according to".

[0207] Any reference to an element using the designations "first," "second," etc. used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, a reference to a first element and a second element does not mean that only two elements can be taken or that the first element must precede the second element in any form.

[0208] The “unit” in the configuration of each of the above-mentioned devices may be replaced with a “section”, “circuit”, “device” or the like.

[0209] When the terms "include", "including" and their variations are used in the present disclosure, these terms are intended to be inclusive like the term "comprising". Furthermore, the term "or" used in the present disclosure does not mean an exclusive or.

[0210] A radio frame may be composed of one or more frames in the time domain. In the time domain, one or more frames may be referred to as a subframe. A subframe may also be composed of one or more time slots in the time domain. A subframe may also be a fixed time length (e.g., 1 ms) that is independent of a numerology.

[0211] A parameter set may be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. The parameter set may, for example, represent at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, specific windowing processing performed by the transceiver in the time domain, and the like.

[0212] 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 time unit based on a parameter set.

[0213] A time slot may contain multiple mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may be composed of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in units of time greater than a mini-slot may be referred to as a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be referred to as a PDSCH (or PUSCH) mapping type B.

[0214] A radio frame, a subframe, a time slot, a mini-time slot, and a symbol all represent time units for transmitting signals. A radio frame, a subframe, a time slot, a mini-time slot, and a symbol may be referred to by other corresponding names.

[0215] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, and one time slot or one mini time slot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing a TTI may be referred to as a time slot, a mini time slot, etc. instead of a subframe.

[0216] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling to allocate wireless resources (frequency bandwidth, transmission power, etc. that can be used in each terminal 20) to each terminal 20 in units of TTI. In addition, the definition of TTI is not limited to this.

[0217] TTI can be a transmission time unit of data packets (transport blocks), code blocks, code words, etc. after channel coding, or a processing unit such as scheduling and link adaptation. In addition, when TTI is given, the time interval (e.g., the number of symbols) to which the transport block, code block, code word, etc. is actually mapped can also be shorter than the TTI.

[0218] In addition, when one time slot or one mini time slot is called TTI, one or more TTIs (i.e., one or more time slots or one or more mini time slots) may also be the minimum time unit for scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit for scheduling may also be controlled.

[0219] A TTI with a time length of 1 ms is also called a normal TTI (TTI in LTE Rel.8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini-time slot, a sub-time slot, a time slot, etc.

[0220] In addition, for a long TTI (long TTI) (for example, a normal TTI, a subframe, etc.), it can be understood as a TTI with a time length exceeding 1ms, and for a short TTI (short TTI) (for example, a shortened TTI, etc.), it can be understood as a TTI with a TTI length less than that of a long TTI (longTTI) and greater than 1ms.

[0221] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain. In the frequency domain, it may include one or more consecutive subcarriers. The number of subcarriers included in an RB may be the same regardless of the parameter set, for example, it may be 12. The number of subcarriers included in an RB may also be determined according to the parameter set.

[0222] In addition, the time domain of an RB may include one or more symbols, and may be the length of one slot, one mini slot, one subframe, or one TTI. One TTI, one subframe, etc. may be composed of one or more resource blocks, respectively.

[0223] In addition, one or more RBs may also be referred to as a physical resource block (PRB: Physical RB), a sub-carrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, etc.

[0224] In addition, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0225] A bandwidth part (BWP) (also referred to as partial bandwidth, etc.) may also represent a subset of contiguous common RBs (common resource blocks) for a parameter set in a carrier. Here, the common RBs may be identified by the index of the RBs relative to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0226] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for the terminal 20 within one carrier.

[0227] At least one of the set BWPs may be active, and it is not assumed that the terminal 20 transmits and receives a predetermined signal / channel outside the activated BWP. In addition, "cell", "carrier" and the like in the present disclosure may be replaced with "BWP".

[0228] The above structures of radio frames, subframes, time slots, mini-time slots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of time slots per subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length may be changed in various ways.

[0229] In the present disclosure, when an article is added by translation, such as a, an, and the in English, for example, the present disclosure also includes the case where the noun following the article is in plural form.

[0230] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other". In addition, the term may mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted in the same way as "different".

[0231] Each form / implementation described in the present disclosure may be used alone or in combination, and may be switched depending on the execution. In addition, notification of scheduled information is not limited to being performed explicitly (e.g., notification of "yes X"), but may also be performed implicitly (e.g., notification of the scheduled information is not performed).

[0232] The present disclosure is described in detail above, but it should be clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as a modification and variation without departing from the subject matter and scope of the present disclosure as determined by the claims. Therefore, the purpose of the description of the present disclosure is to illustrate and not to have any limiting meaning on the present disclosure.

[0233] Description of symbols

[0234] 10 Base Station (RAN)

[0235] 110 Sending Department

[0236] 120 Receiving Department

[0237] 130 Setting Department

[0238] 140 Control Department

[0239] 20 Terminal

[0240] 30 Core Network

[0241] 40 DN

[0242] 210 Sending Department

[0243] 220 Receiving Department

[0244] 230 Setting Department

[0245] 240 Control Department

[0246] 310 AMF

[0247] 320 UDM

[0248] 330 NEF

[0249] 340 NRF

[0250] 350 AUSF

[0251] 360 PCF

[0252] 370 SMF

[0253] 380 UPF

[0254] 390 AF

[0255] 1001 Processor

[0256] 1002 Storage Device

[0257] 1003 Auxiliary storage device

[0258] 1004 Communication device

[0259] 1005 Input Device

[0260] 1006 Output Device

[0261] 2001 Vehicles

[0262] 2002 Drive Department

[0263] 2003 Steering

[0264] 2004 Accelerator pedal

[0265] 2005 Brake Pedal

[0266] 2006 Gear Lever

[0267] 2007 Front wheel

[0268] 2008 Rear wheel

[0269] 2009 Axle

[0270] 2010 Electronic Control Department

[0271] 2012 Information Services Department

[0272] 2013 Communication Module

[0273] 2021 Current Sensor

[0274] 2022 Speed ​​Sensor

[0275] 2023 Air Pressure Sensor

[0276] 2024 Vehicle speed sensor

[0277] 2025 Accelerometer

[0278] 2026 Brake pedal sensor

[0279] 2027 Gear lever sensor

[0280] 2028 Object Detection Sensor

[0281] 2029 Accelerator pedal sensor

[0282] 2030 Driving Assistance Systems Division

[0283] 2031 Microprocessor

[0284] 2032 Memory (ROM, RAM)

[0285] 2033 Communication port (IO port)

Claims

1. A network node, in, The network node has: a receiving unit for receiving, when a PDU session is established, a session establishment request for communication with a network node controlling an application, the session establishment request including information identifying a user of the network node controlling the application; a control unit that determines whether to allow establishment of a session for communication with a network node controlling the application, according to whether the PDU session is occupied by a user different from the user; as well as A sending unit is configured to send an indication of allowing the sending and receiving of user plane data related to the application to a network node that controls an apparatus for processing user plane data, if the establishment of the session is allowed.

2. The network node according to claim 1, in, The user identification information is managed according to each network node controlling the application. The receiving unit receives a session establishment request for communication with a network node controlling the application, the session establishment request including information identifying the network node controlling the application, The control unit determines whether to allow establishment of a session for communication with a network node controlling the application, according to whether the PDU session is occupied by a network node controlling an application different from the network node controlling the application.

3. The network node according to claim 1, in, The information identifying the user is managed for each group to which the network node controlling the application belongs. The receiving unit receives a session establishment request for communication with the network node controlling the application, the session establishment request including information identifying a group to which the network node controlling the application belongs. The control unit determines whether to permit establishment of a session for communication with a network node controlling the application, according to whether the PDU session is occupied by a group different from the group.

4. A communication method performed by a network node, in, The communication method comprises the following steps: In case that the PDU session is established, receiving a session establishment request for communication with a network node controlling the application, the session establishment request including information identifying a user of the network node controlling the application; determining whether to allow establishment of a session for communication with a network node controlling the application according to whether the PDU session is occupied by a user different from the user; as well as In the case where the session establishment is allowed, an indication of allowing the transmission and reception of user plane data related to the application is sent to a network node that controls the device for processing user plane data.

Images