Network node and communication method

Abstract

Provided is a network node comprising: a reception unit that receives, from another network node, a request to subscribe to a feature for reporting occurrence of an event to register a network node accommodating a PDU session if the PDU session is established; and a transmission unit that, if an event to register a network node accommodating the PDU session has occurred, transmits a report indicating occurrence of the event to another network node.

Description

[Technical Field]

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

[0002] In NR (New Radio) (also referred to as "5G"), the successor system to LTE (Long Term Evolution), a network architecture is being considered that includes 5GC (5G Core Network), which corresponds to EPC (Evolved Packet Core), which is the core network in the LTE (Long Term Evolution) network architecture, and NG-RAN (Next Generation - Radio Access Network), which corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the LTE network architecture (for example, Non-Patent Document 1 and Non-Patent Document 2).

[0003] Additionally, for future systems such as 6G, mechanisms are being considered that will allow devices to be shared by multiple users. For example, one scenario is envisioned in which, when a person approaches a shared device on a street corner, the app server used by that person sends app data to that device. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 23.501 V17.2.0(2021-09) [Non-patent document 2] 3GPP TS 23.502 V17.2.1(2021-09) Summary of the Invention [Problem to be solved by the invention]

[0005] Conventionally, an authentication device or the like detects when a person approaches a shared terminal and notifies an AF (e.g., an application server). The AF then sends its data to the shared terminal. A system is being considered in which charges are based on the amount of data used by the AF. However, this system does not allow for exclusive control that identifies the user, and there is a problem in that, for example, other application servers of other people can also send other application data to the terminal at the same time.

[0006] The present invention has been made in view of the above points, and has as its object to realize appropriate exclusive control in a terminal shared by multiple users in a wireless communication system. [Means for solving the problem]

[0007] According to the disclosed technology, the device comprises a receiving unit that, when a PDU session is established, receives from another network node a request to subscribe to a function for notifying the occurrence of an event that registers a network node that accommodates the PDU session, and a transmitting unit that, when an event that registers a network node that accommodates the PDU session occurs, transmits a notification indicating the occurrence of the event to the other network node. In a network node, when the other network node is a network node that controls an application, the transmitter transmits information indicating whether the PDU session is occupied by a network node that controls an application different from the network node that controls the other application to the network node that controls the other application. A network node is provided. [Effects of the Invention]

[0008] The disclosed technology provides a technology that enables appropriate exclusive control to be realized in a terminal shared by multiple users in a wireless communication system. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating an example of a configuration of a wireless communication system according to an embodiment of the present invention. [Figure 3]FIG. 10 is a sequence diagram showing an example of a flow of a preparation procedure for a terminal according to an embodiment of the present invention. [Figure 4] FIG. 1 is a first sequence diagram showing an example of a flow of a data transmission procedure according to an embodiment of the present invention. [Figure 5] FIG. 10 is a second sequence diagram showing an example of the flow of a data transmission procedure according to an embodiment of the present invention. [Figure 6] FIG. 10 is a third sequence diagram showing an example of the flow of a data transmission procedure according to an embodiment of the present invention. [Figure 7] FIG. 10 is a fourth sequence diagram showing an example of the flow of a data transmission procedure according to an embodiment of the present invention. [Figure 8] FIG. 10 is a sequence diagram illustrating an example of a flow of a data transmission termination procedure according to an embodiment of the present invention. [Figure 9] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station according to an embodiment of the present invention. [Figure 10] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal according to an embodiment of the present invention. [Figure 11] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station or a terminal according to an embodiment of the present invention. [Figure 12] 1 is a diagram showing an example of a configuration of a vehicle according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] In operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. The existing technologies include, but are not limited to, existing NR or LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0012] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, such as 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), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

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

[0014] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station or a terminal are set.

[0015] (System Configuration) FIG. 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, a wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

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

[0017] The base station 10 transmits 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 transmitted, for example, via the NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell) and a primary cell (PCell) using Carrier Aggregation (CA). Furthermore, the terminal 20 may perform communication via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0018] 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 an M2M (Machine-to-Machine) communication module. 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 utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals. The terminal 20 may also be referred to as a UE, and the base station 10 may also be referred to as a gNB.

[0019] 2 is a diagram showing 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.

[0020] The core network 30 is a network including an exchange, a subscriber information management device, etc. The core network 30 includes a network node that realizes a U-Plane function and a group of network nodes that realizes a group of C-Plane functions.

[0021] The U-Plane function is a function that executes transmission and reception processing of user data. A network node that realizes the U-Plane function is, for example, the 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 transmission and reception of data between the DN 40 and the terminal 20. The UPF 380 and the DN 40 may be composed of one or more network slices.

[0022] The C-Plane function group is a function group that executes a series of control processes for establishing communications, etc. The network nodes that realize the C-Plane function group include, for example, an Access and Mobility Management Function (AMF) 310, a Unified Data Management (UDM) 320, a Network Exposure Function (NEF) 330, a Network Repository Function (NRF) 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.

[0023] The AMF 310 is a network node that has functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), and managing registration, connection, reachability, and mobility. The NRF 340 is a network node that has a function of discovering NF (Network Function) instances that provide services. The 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 an FE (Front End) 322. The FE 322 processes subscriber information.

[0024] The SMF 370 is a network node that has functions such as session management, IP (Internet Protocol) address allocation and management for the terminal 20, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF 330 is a network node that has a function of notifying other NFs (Network Functions) of capabilities and events. The PCF 360 is a network node that has a function of controlling network policies.

[0025] An AF (Application Function) 390 is a network node that has the function of controlling an application server.

[0026] The AMF 310 and the RAN 10 are connected to be able to communicate with each other as an N2 link. The UPF 380 and the RAN 10 are connected to be able to communicate with each other as an N3 link. The UPF 380 and the SMF 370 are connected to be able to communicate with each other as an N4 link. The UPF 380 and the DN 40 are connected to be able to communicate with each other as an N6 link.

[0027] Next, an example assumed in this embodiment will be described. For example, the terminal 20 is a terminal shared by multiple users. The terminal 20 may be installed on a street corner. When one of the multiple users approaches the terminal 20, the AF390 transmits data (application data, etc.) related to that user to the terminal 20. This allows the terminal 20 to perform an operation targeted at that user, such as displaying information related to the area in which the terminal 20 is installed according to the preferences of that user.

[0028] Next, a shared PDU session will be described. One shared PDU session is established for each of one or more terminals 20. Multiple users share the shared PDU session established for each terminal 20. Here, in conventional specifications, if multiple users approach a terminal 20 at the same time, data related to the multiple users will be transmitted to the terminal 20. Therefore, in this embodiment, a mechanism (exclusive control) is realized that prevents other users from using the terminal 20 while one user approaches the terminal 20 and is using data related to that user.

[0029] Specifically, the following is defined for the PDU session context information held by the SMF 370 and PCF 360 and the information used for SMF registration to the UDM. Shared PDU session display PDU session lock status

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

[0031] The PDU session lock status includes the following information: Lock or not Occupancy type

[0032] The presence or absence of lock is information indicating either "unlocked" or "locked." When the presence or absence of lock indicates "unlocked," 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.

[0033] The occupancy type is information indicating one of AF session occupancy, AF occupancy, and AF group occupancy.

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

[0035] The AF occupancy is information indicating that the AF is occupied, and includes the AF in use, the AF session in use, and the user's intra-AF identifier. The AF in use is information indicating the AF 390 in use, and is expressed, for example, as in the past, as "afAppId." The user's intra-AF identifier is an identifier for identifying the user in the AF 390, and is expressed, for example, as "uid@afAppId." Note that "uid" is the portion that identifies the user, and "@afAppId" is the portion that indicates the AF 390.

[0036] The identifier indicating the user is managed by AF 390. Therefore, the user is a concept defined in AF 390, and is a different concept from the subscriber of terminal 20. The subscriber of terminal 20 may be, for example, a business operator that provides the user with a function or service provided by terminal 20.

[0037] The AF group occupancy is information indicating that a group to which the AF 390 belongs is occupied, and includes the in-use AF group, in-use AF, in-use AF session, and the user's AF group identifier. The in-use AF group is information indicating the group to which the in-use AF 390 belongs, and is represented, for example, as "afAppGid." The user's in-AF group identifier is an identifier for identifying the user in the group to which the AF 390 belongs, and is represented, for example, as "uid@afAppGid." Note that "uid" is a portion that identifies the user, and "@afAppGid" is a portion that indicates the group to which the AF 390 belongs.

[0038] In addition, a shared PDU session accommodation SMF registration event disclosure service is introduced in UDM 320. The shared PDU session accommodation SMF registration event disclosure service is a function for disclosing (notifying) the occurrence of an event that registers SMF 370, which accommodates a shared PDU session. UDM 320 notifies network nodes that have subscribed to the shared PDU session accommodation SMF registration event disclosure service of the occurrence of an event that registers SMF 370.

[0039] Furthermore, in this embodiment, a PDU session lock request (AF session occupancy, AF occupancy, AF group occupancy), identifiers for identifying the AF 390 and the group to which the AF 390 belongs ("afAppId", "afAppGid"), and identifiers for identifying the user ("uid@afAppId", "uid@afAppGid") are added to the input parameters of a conventional AF session establishment request with a QoS request. The AF session establishment request with a QoS request is a request defined in conventional specifications, and is a request for establishing an AF session with a QoS request.

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

[0041] 3 is a sequence diagram showing an example of the flow of a preparation procedure of a terminal according to an embodiment of the present invention. When there are multiple AFs 390, the following procedure is executed for each AF 390. In the following, a first AF 390-1, a second AF 390-2, and a third AF 390-3 are assumed. While FIG. 3 shows an example of AF 390, the following description will assume that the first AF 390-1, the second AF 390-2, and the third AF 390-3 have each executed the preparation procedure.

[0042] The AF 390 transmits a subscribe request to the shared PDU session accommodating SMF registration event disclosure service to the UDM 320 (step S101). The terminal 20 transmits a PDU session establishment request including a shared PDU session indication to the SMF 370 (step S102).

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

[0044] Next, the SMF 370 sends "SmPolicyContextData" including a shared PDU session indication to the PCF 360 (step S105). The PCF 360 sends "SMPolicyDecision" including a PDU session rule (shared PDU session indication, PDU session lock state = no lock) and a default PCC rule (gate state = closed) to the SMF 370 (step S106). Here, gate state = closed is a setting that establishes a PDU session but does not allow packets to pass through.

[0045] 3 shows an example in which the SMF 370 receives a shared PDU session indication from the terminal 20. Alternatively, the SMF 370 may not receive the indication from the terminal 20, but may receive the indication set in the subscriber information from the UDM 320. Furthermore, the SMF 370 may not receive the indication from the terminal 20 or the UDM 320, but may receive the indication set in "SMPolicyDecision" from the PCF 360.

[0046] Furthermore, the above-mentioned default PCC rule may be a PCC rule that matches service data flows with a wildcard.

[0047] Next, the SMF 370 sends a PFCP session establishment request including gate status = closed to the UPF 380 (step S107). The SMF 370 sends an SMF registration request to the UDM 320 including information about the PDU session, such as a shared PDU session indication, a PDU session lock status = not locked, terminal location information, and an IP address (step S108).

[0048] Then, the PDU session establishment is completed (step S109). The UDM 320 notifies the AF 390 that a shared PDU session accommodating SMF has been registered, including a shared PDU session indication, a PDU session lock state = no lock, terminal location information, an IP address, and the like.

[0049] The above-described AF 390 may be realized in various forms. For example, the AF 390 may be an application server, an application in a user container, an application in a user terminal, etc.

[0050] Next, the procedure for transmitting AF390 data will be explained.

[0051] 4 is a first sequence diagram showing an example of the flow of a data transmission procedure according to an embodiment of the present invention, which illustrates an example for the first AF 390-1.

[0052] The DN 40 notifies the first AF 390-1 that a first user has approached the terminal 20 (step S201). For example, a sensor included in the DN 40 and a computer device connected to the sensor detect the approach of the user, and the user is identified as the first user by facial recognition or the like. This method of notifying the approach is one example, and other methods may be used.

[0053] The first AF 390-1 transmits an AF session establishment request with a QoS request and a PDU session lock request to the PCF 360, including its own identifier (e.g., afAppId=AF1, afAppGid=AFGx), the user's intra-AF group identifier (uid@afAppGid=abc@AFGx), and the IP address of the PDU session (step S202). Note that the PDU session lock request specifies AF group occupancy as additional information. The additional information specifies one of AF session occupancy, AF occupancy, and AF group occupancy.

[0054] Next, the PCF 360 recognizes that the PDU session is (PDU session lock state = not locked) and sends a response permitting the AF session establishment request, including (appSessionId = AF session 1), to the first AF 390-1 (step S203).

[0055] Next, the first AF 390-1 requests the PCF 360 to subscribe to the event using (appSessionId=AF session 1) (step S204).

[0056] The PCF 360 transmits PDU session rule update information and PCC Rule 1 to the SMF 370 (step S205). The PDU session rule update information includes PDU session lock status = locked (AF group occupied (in use AF group = AFGx, in use AF = AF1, in use AF session = AF1:AF session 1, user's AF group identifier = abc@AFGx)). Furthermore, PCC Rule 1 is a rule that sets the gate status = open for the service data flow specified by the first AF 390-1 in the AF session establishment request.

[0057] The SMF 370 transmits an SMF registration update request including (PDU session lock status = locked) for the PDU session to the 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 intra-AF group identifier = abc@AFGx).

[0058] Next, the SMF 370 transmits a PFCP session change request including gate status = open for the service data flow specified by the first AF 390-1 to the UPF 380 (step S207). As described above, the exclusive control is performed in the order of locking to selectively releasing the gate.

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

[0060] Fig. 5 is a second sequence diagram showing an example of the flow of the data transmission procedure according to the embodiment of the present invention. Fig. 5 shows an example of the second AF 390-2 after the procedure of Fig. 4 is executed. Note that the second AF 390-2 belongs to the same group (AFGx) as the first AF 390-1.

[0061] The UDM 320 notifies the second AF 390-2 of information indicating that the shared PDU session accommodating SMF registration has been modified (changed) and that the PDU session lock state is locked (step S301). The information indicating that the PDU session lock state is locked includes AF group occupancy (AF group in use = AFGx, AF in use = AF1, AF session in use = AF1:AF session 1, user's intra-AF group identifier = abc@AFGx).

[0062] The DN 40 notifies the second AF 390-2 that the first user has approached the terminal 20 (step S302). For example, a sensor included in the DN 40 and a computer device connected to the sensor detect the approach of the user, and the user is identified as the first user by facial recognition or the like. This method of notifying the approach is one example, and other methods may be used. Furthermore, the second AF 390-2 may determine that the first user has approached the terminal 20 by receiving the notification in step S301.

[0063] The second AF 390-2 transmits an AF session establishment request with a QoS request and a PDU session lock request to the PCF 360, the 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 (step S303). Note that the PDU session lock request specifies AF group occupancy as additional information.

[0064] Next, the PCF 360 recognizes that the PDU session has a (PDU session lock status = locked) status and transmits a response permitting the AF session establishment request, including (appSessionId = AF session 2), to the second AF 390-2 (step S304). The information indicating the (PDU session lock status = locked) status includes AF group occupancy (in-use AF group = AFGx, in-use AF = AF1, in-use AF session = AF1:AF session 1, user's AF group identifier = abc@AFGx). Here, if AF group occupancy is specified and the PDU session is AF group occupied by the specified group, the PCF 360 permits AF session establishment when the same user belonging to the occupying AF group is in proximity.

[0065] Next, the second AF 390-2 requests the PCF 360 to subscribe to the event using (appSessionId=AF session 2) (step S305).

[0066] The PCF 360 transmits the PDU session rule update information and PCC rule 2 to the SMF 370 (step S306). The PDU session rule update information includes PDU session lock status = locked (AF group occupied (in use AF group = AFGx, in use AF = AF1, AF2, in use AF session = AF1:AF session 1, AF2:AF session 2, user's intra-AF group identifier = abc@AFGx)). In addition, PCC rule 2 is a rule that sets the gate status = open for the service data flow specified by the second AF 390-2 in the AF session establishment request.

[0067] The SMF 370 transmits an SMF registration update request including (PDU session lock status = locked) for the PDU session to the UDM 320 (step S307). The information indicating (PDU session lock status = locked) includes AF group occupancy (AF group in use = AFGx, AFs in use = AF1, AF2, AF sessions in use = AF1:AF session 1, AF2:AF session 2, user's intra-AF group identifier = abc@AFGx).

[0068] Next, the SMF 370 transmits a PFCP session change request including gate status=open for the service data flow specified by the second AF 390-2 to the UPF 380 (step S308).

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

[0070] Fig. 6 is a third sequence diagram showing an example of the flow of a data transmission procedure according to an embodiment of the present invention. Fig. 6 shows an example of the third AF 390-3 after the procedure of Fig. 5 is executed. Note that the third AF 390-3 does not belong to the same group (AFGx) as the first AF 390-1.

[0071] The UDM 320 notifies the third AF 390-3 of information indicating that the shared PDU session accommodating SMF registration has been modified (changed) and that the PDU session lock state is locked (step S401).

[0072] The DN 40 notifies the third AF 390-3 that the first user has approached the terminal 20 (step S402). For example, a sensor included in the DN 40 and a computer device connected to the sensor detect the approach of the user, and the user is identified as the first user by facial recognition or the like. This method of notifying the approach is one example, and other methods may be used.

[0073] The third AF 390-3 transmits an AF session establishment request with a QoS request and a PDU session lock request to the PCF 360, the 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 (step S403). Note that the PDU session lock request specifies AF occupancy as additional information.

[0074] Here, the third AF 390-3 may determine from the information indicating (PDU session lock state = locked) that an AF belonging to another group is occupying the shared PDU session, and may not transmit an AF session establishment request to the PCF 360. In this case, the data transmission procedure ends.

[0075] Next, the PCF 360 recognizes that the PDU session lock state is locked, and transmits a response rejecting the AF session establishment request to the third AF 390-3 (step S404). The information indicating the PDU session lock state is locked includes AF group occupancy (AF group in use = AFGx, AFs in use = AF1, AF2, AF sessions in use = AF1:AF session 1, AF2:AF session 2, user's intra-AF group identifier = abc@AFGx).

[0076] Here, if AF occupancy is specified and the PDU session is AF group occupancy (i.e., if the specified occupancy type is different from the occupancy type currently being occupied), the PCF 360 rejects the establishment of the AF session. Note that the PCF 360 may also reject the establishment of the AF session if AF group occupancy is specified and the PDU session is AF group occupancy by a group different from the specified group.

[0077] Fig. 7 is a fourth sequence diagram showing an example of the flow of a data transmission procedure according to an embodiment of the present invention. Fig. 7 shows an example in which a second user different from the first user approaches terminal 20 after the procedure of Fig. 5 or 6 has been executed.

[0078] The UDM 320 notifies the first AF 390-1 of information indicating that the shared PDU session accommodating SMF registration has been modified (changed) and that the PDU session lock status is locked (step S501). The information indicating the PDU session lock status includes AF group occupancy (AF group in use = AFGx, AFs in use = AF1, AF2, AF sessions in use = AF1:AF session 1, AF2:AF session 2, user's intra-AF group identifier = abc@AFGx).

[0079] The DN 40 notifies the first AF 390-1 that a second user has approached the terminal 20 (step S502). For example, a sensor included in the DN 40 and a computer device connected to the sensor detect the approach of the user, and the user is identified as the second user by facial recognition or the like. This method of notifying the approach is one example, and other methods may be used.

[0080] The first AF 390-1 transmits an AF session establishment request with a QoS request and a PDU session lock request to the PCF 360, the 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 (step S503). Note that the PDU session lock request specifies AF group occupancy as additional information.

[0081] Here, the first AF 390-1 may determine that another user is occupying the session from the information indicating (PDU session lock state = locked) and may not transmit an AF session establishment request to the PCF 360. In this case, the data transmission procedure ends.

[0082] Next, the PCF 360 recognizes that the PDU session lock state is locked, and sends a response rejecting the AF session establishment request to the first AF 390-1 (step S504). The information indicating the PDU session lock state is locked includes AF group occupancy (AF group in use = AFGx, AFs in use = AF1, AF2, AF sessions in use = AF1:AF session 1, AF2:AF session 2, user's intra-AF group identifier = abc@AFGx).

[0083] Here, if a user other than the occupant user approaches, the PCF 360 will reject the establishment of an AF session.

[0084] In addition, the PCF 360 may reject the establishment of an AF session if AF session occupancy is specified and the occupied PDU session is an AF session different from the specified AF session.

[0085] Next, the procedure for ending data transmission will be described.

[0086] 8 is a sequence diagram showing an example of the flow of a data transmission termination procedure according to an embodiment of the present invention. The first AF 390-1 transmits an AF session release request to the PCF 360 by using (appSessionId=AF session 1) (step S601).

[0087] The PCF 360 recognizes that the PDU session lock status is locked for the PDU session. The information indicating that the PDU session lock status is locked includes AF group occupancy (AF group in use = AFGx, AFs in use = AF1, AF2, AF sessions in use = AF1:AF session 1, AF2:AF session 2, user's intra-AF group identifier = abc@AFGx).

[0088] The PCF 360 transmits PDU session rule update information and an instruction to delete PCC rule 1 to the SMF 370 (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 intra-AF group identifier = abc@AFGx)).

[0089] The SMF 370 transmits a PFCP session change request to the UPF 380 (step S603). The PFCP session change request is a request to instruct the deletion of the gate state=open setting for the service data flow specified by the AF1.

[0090] The SMF 370 transmits an SMF registration update request including (PDU session lock status = locked) for the PDU session to the UDM 320 (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 intra-AF group identifier = abc@AFGx).

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

[0092] Next, a procedure for the second AF 390-2 to end data transmission will be described. The second AF 390-2 ends data transmission through a procedure similar to the procedure shown in Fig. 8. Specifically, in step S601, the second AF 390-2 transmits an AF session release request to the PCF 360 by using (appSessionId=AF session 2).

[0093] The PCF 360 recognizes that the PDU session lock status is locked for the PDU session. The information indicating that the PDU session lock status is locked includes AF group occupancy (AF group in use = AFGx, AF in use = AF2, AF session in use = AF2:AF session 2, user's intra-AF group identifier = abc@AFGx).

[0094] Next, in step S602, the PCF 360 transmits PDU session rule update information and an instruction to delete PCC rule 2 to the SMF 370. The PDU session rule update information includes (PDU session lock status = no lock).

[0095] In the following step S603, the SMF 370 transmits a PFCP session change request to the UPF 380. The PFCP session change request is a request to instruct deletion of the gate state = open setting for the service data flow specified by the AF2.

[0096] In the following step S604, SMF370 sends an SMF registration update request including (PDU session lock status = no lock) to UDM320 for the PDU session.

[0097] As described above, the exclusive control is performed in the order of closing the gate and then unlocking it. Then, in step S605, the PDU session change is completed.

[0098] According to this embodiment, in a shared PDU session shared by multiple users, exclusive control is performed to prevent multiple users from using the session simultaneously, thereby realizing appropriate exclusive control in a terminal shared by multiple users in a wireless communication system.

[0099] (Device configuration) Next, a description will be given of examples of the functional configurations of the base station 10, the terminal 20, and various network nodes that perform the processes and operations described above. The base station 10, the terminal 20, and various network nodes include functions for performing the above-described embodiments. However, the base station 10, the terminal 20, and various network nodes may each include only a portion of the functions of the embodiments.

[0100] <Base Station 10 and Network Nodes> FIG. 9 is a diagram showing an example of the functional configuration of base station 10. As shown in FIG. 9, base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in FIG. 9 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that a network node may have the same functional configuration as base station 10. Furthermore, a network node having multiple different functions in the system architecture may be composed of multiple network nodes separated by function.

[0101] The transmitter 110 has 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 receiver 120 has a function of receiving various signals transmitted from the terminal 20 or another network node and acquiring, for example, information of a higher layer from the received signal.

[0102] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads the information from the storage device as needed. The content of the setting information includes, for example, settings related to communication using NTN.

[0103] As described in the embodiment, the control unit 140 performs processing related to communication using NTN. The control unit 140 also performs processing related to communication with the terminal 20. The control unit 140 also performs processing related to geographical position verification 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.

[0104] <Terminal 20> FIG. 10 is a diagram showing an example of the functional configuration of the terminal 20. As shown in FIG. 10, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in FIG. 10 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the functional divisions and names of the functional units may be any. The USIM attached to the terminal 20 may have the transmitting unit 210, the receiving unit 220, the setting unit 230, and the control unit 240, similar to the terminal 20.

[0105] The transmitter 210 generates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, etc. transmitted from a network node.

[0106] 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. The setting unit 230 also stores setting information that is set in advance.

[0107] The network node of this embodiment may be configured as the network node shown in each of the following items. Also, the following communication method may be implemented.

[0108] <Configuration of this embodiment> (Section 1) A receiving unit that, when a PDU session is established, receives from another network node a request to subscribe to a function for notifying the occurrence of an event that registers the network node that accommodates the PDU session; A transmitter that, when an event occurs to register the network node that accommodates the PDU session, transmits a notification indicating the occurrence of the event to the other network node. Network node. (Section 2) When the other network node is a network node that controls an application, The transmitter transmits information indicating whether the PDU session is occupied by a network node controlling an application different from the network node controlling the other application to the network node controlling the other application. 2. The network node of claim 1. (Section 3) When the other network node is a network node that controls an application, The transmitter transmits information indicating whether the PDU session is occupied by a network node controlling an application belonging to a group different from a group to which the network node controlling the other application belongs, to the network node controlling the other application. 3. A network node according to claim 1 or 2. (Section 4) When a PDU session is established, receiving a request from another network node to subscribe to a function for notifying the occurrence of an event that registers the network node accommodating the PDU session; When an event occurs that registers the network node accommodating the PDU session, sending a notification indicating the occurrence of the event to the other network node. The communication method implemented by network nodes.

[0109] Any of the above configurations provides a technology that enables appropriate exclusive control to be achieved in a terminal shared by multiple users in a wireless communication system. According to paragraph 1, when an event occurs that registers a network node accommodating a PDU session, a notification indicating the occurrence of the event can be transmitted to the other network nodes. According to paragraph 2, information indicating whether the PDU session is occupied by a network node controlling an application different from the network node controlling the other application can be transmitted to the network node controlling the other application. According to paragraph 3, information indicating whether the PDU session is occupied by a network node controlling an application belonging to a group different from the group to which the network node controlling the other application belongs can be transmitted to the network node controlling the other application.

[0110] (Hardware configuration) The block diagrams (FIGS. 9 and 10) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and connected directly or indirectly (for example, by wire, wirelessly, etc.). The functional block may be realized by combining software with the one device or the multiple devices.

[0111] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0112] For example, a network node, a terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 11 is a diagram illustrating an example of a hardware configuration of a base station 10 and a terminal 20 according to an embodiment of the present disclosure. The network node may have the same hardware configuration as the base station 10. The USIM may have the same hardware configuration as the terminal 20. The above-described base station 10 and terminal 20 may be 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.

[0113] In the following description, the term "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 the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0114] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0115] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0116] Furthermore, 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 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 10 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0117] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0118] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0119] 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, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0120] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives 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 be integrated into one device (for example, a touch panel).

[0121] Furthermore, 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 between each device.

[0122] Furthermore, base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0123] Fig. 12 shows an example configuration of a vehicle 2001. As shown in Fig. 12, the vehicle 2001 includes a drive 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 aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0124] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), 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.

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

[0126] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0127] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, 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 acquired from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0128] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0129] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0131] 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 an external device. For example, it transmits and receives various information to and from the 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.

[0132] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on 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 be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0133] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0134] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

[0135] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each 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 or any other suitable storage medium.

[0136] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0137] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 decimal number)), 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 The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0138] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0139] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0140] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0141] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0142] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0143] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0144] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0145] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0146] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

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

[0148] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

[0149] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0150] In this disclosure, terms such as "base station (BS)," "radio 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," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0151] A base station can accommodate one or more (e.g., three) 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 be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0152] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0153] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0154] A mobile station may also be referred to by those 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 terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0155] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0156] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0157] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0158] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0159] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling 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 coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0160] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0161] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0162] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0163] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0164] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0165] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0166] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0167] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0168] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0169] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0170] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0171] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0172] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0173] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0174] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0175] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0176] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0177] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0178] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0179] Furthermore, 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.

[0180] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

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

[0182] At least one of the configured BWPs may be active, and the terminal 20 may not expect to transmit or receive a predetermined signal / channel outside the active BWP. Note that the terms "cell," "carrier," and the like in this disclosure may be read as "BWP."

[0183] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, 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 subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0184] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0185] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0186] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0187] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0188] 10 Base station (RAN) 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 30 Core Network 40DN 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 310 AMF 320 UDM 330 NEF 340 NRF 350 AUSF 360 PCF 370 SMF 380 UPF 390 AF 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM 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 Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A receiving unit that receives, when a PDU session is established, a request to subscribe to a function for notifying the occurrence of an event that registers a network node accommodating the PDU session from another network node; A network node comprising: a transmitter that, when an event occurs to register a network node accommodating the PDU session, transmits a notification indicating the occurrence of the event to the other network node; When the other network node is a network node that controls an application, The transmitter transmits information indicating whether the PDU session is occupied by a network node controlling an application different from the network node controlling the other application to the network node controlling the other application. Network node.

2. A receiving unit that receives, when a PDU session is established, a request to subscribe to a function for notifying the occurrence of an event that registers a network node accommodating the PDU session from another network node; A network node comprising: a transmitter that, when an event occurs to register a network node accommodating the PDU session, transmits a notification indicating the occurrence of the event to the other network node; When the other network node is a network node that controls an application, The transmitter transmits information indicating whether the PDU session is occupied by a network node controlling an application belonging to a group different from a group to which the network node controlling the other application belongs to, to the network node controlling the other application. Network node.

3. When a PDU session is established, receiving a request from another network node to subscribe to a function for notifying the occurrence of an event that registers the network node accommodating the PDU session; When an event occurs that registers the network node accommodating the PDU session, sending a notification indicating the occurrence of the event to the other network node, When the other network node is a network node that controls an application, The specific network node transmits information indicating whether the PDU session is occupied by a network node controlling an application different from the network node controlling the other application to the network node controlling the other application; Communication method.

4. When a PDU session is established, receiving a request from another network node to subscribe to a function for notifying the occurrence of an event that registers the network node accommodating the PDU session; When an event occurs that registers the network node accommodating the PDU session, sending a notification indicating the occurrence of the event to the other network node, When the other network node is a network node that controls an application, The specific network node transmits information indicating whether the PDU session is occupied by a network node controlling an application belonging to a group different from a group to which the network node controlling the other application belongs to, to the network node controlling the other application; Communication method.

Images