Network node and communication method
By receiving incoming calls notifications in the network node and determining forwarding incoming packets, the problem that subscribers find it difficult to forward incoming packets at the terminal is solved, and effective utilization of computing resources and packet forwarding are realized.
Patent Information
- Application Number
- CN202280093654.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-25
- Publication Date
- 2024-11-05
AI Technical Summary
In the prior art, it is difficult for subscribers to forward incoming packets by terminals to computing resources within the network, especially in case of application proxy processing.
It is provided with a network node that receives incoming notifications from external terminals or applications, and determines whether to forward incoming packets to computing resources set by each subscriber through the control unit.
It realizes that the subscriber can use the computing resources on the network and forward incoming packets from terminals or applications to the computing resources when necessary, solving the problem that the subscriber has difficulty forwarding packets.
Smart Images

Figure CN118901229A_ABST
Abstract
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), a network architecture including 5GC (5G Core Network) and NG-RAN (Next Generation-Radio Access Network) is being studied. The 5GC (5G Core Network) corresponds to the core network in the network architecture of LTE (Long Term Evolution), namely EPC (Evolved Packet Core), and the NG-RAN (Next Generation-Radio Access Network) corresponds to the RAN (Radio Access Network) in the network architecture of LTE, namely E-UTRAN (Evolved Universal Terrestrial Radio Access Network) (for example, non-patent document 1 and non-patent document 2).
[0003] Prior art literature
[0004] Non-patent literature
[0005] Non-patent document 1: 3GPP TS23.501V17.2.0 (2021-09)
[0006] Non-patent document 2: 3GPP TS23.502V17.2.1 (2021-09) Summary of the invention
[0007] Problems to be solved by the invention
[0008] It is envisioned that a communication operator provides a service of lending computing resources within the network to subscribers. The subscriber can use the computing resource as the endpoint for outgoing / incoming calls related to the subscriber. The subscriber can also resident an application program equipped with AI, etc., which acts as an agent for the subscriber in the computing resource. The subscriber has two outgoing / incoming endpoints in the terminal and the computing resource. There is a case where the subscriber entrusts the application to perform proxy processing of incoming calls from the terminal. However, in the prior art, it is difficult for the subscriber to forward the incoming packets from the terminal to the computing resource.
[0009] The present invention is made in view of the above problems, and its object is to enable a subscriber to use computing resources on a network and forward incoming packets from a terminal or an application to the computing resources when necessary.
[0010] Means for solving problems
[0011] According to the technology of the present disclosure, there is provided a network node including: a receiving unit that receives a notification of an incoming call from an external terminal or an external application; and a control unit that determines whether to forward the incoming call to a computing resource set for each subscriber.
[0012] Effects of the Invention
[0013] According to the technology of the present disclosure, there is provided a technology that enables a subscriber to use computing resources on a network and forwards incoming packets from a terminal or an application to the computing resources when necessary. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1 It is a diagram for explaining a wireless communication system according to an embodiment of the present invention.
[0015] Figure 2 This is a diagram showing an example of the structure of a core network according to an embodiment of the present invention.
[0016] Figure 3 This is a sequence diagram showing an example of the flow of the CRMF session establishment process according to the embodiment of the present invention.
[0017] Figure 4 This is a sequence diagram showing an example of the flow of the CRMF session change process according to the embodiment of the present invention.
[0018] Figure 5 This is a sequence diagram showing an example of the flow of the service request process according to the embodiment of the present invention.
[0019] Figure 6 This is a sequence diagram showing an example of the flow of the CRMF session release process according to the embodiment of the present invention.
[0020] Figure 7 This is a sequence diagram showing an example of the flow of the CRMF registration process according to the embodiment of the present invention.
[0021] Figure 8 This is a sequence diagram showing an example of the flow of the PDU session establishment process according to an embodiment of the present invention.
[0022] Fig. 9 This is a sequence diagram showing an example of the flow of the incoming packet forwarding determination process according to the embodiment of the present invention.
[0023] Fig.10This is a sequence diagram showing an example of the flow of the incoming packet forwarding process according to the embodiment of the present invention.
[0024] Fig.11 This is a sequence diagram showing an example of the flow of the container registration process according to the embodiment of the present invention.
[0025] Fig.12 This is a sequence diagram showing an example of the flow of the inter-container communication process according to the embodiment of the present invention.
[0026] Fig.13 This is a sequence diagram showing an example of the flow of the container movement process in container movement mode 2 according to the embodiment of the present invention.
[0027] Fig.14 This is a sequence diagram showing an example of the flow of the container movement process in container movement mode 3 according to the embodiment of the present invention.
[0028] Fig.15 This is a diagram showing an example of a functional configuration of a base station according to an embodiment of the present invention.
[0029] Fig.16 This is a diagram showing an example of a functional configuration of a terminal according to an embodiment of the present invention.
[0030] Fig.17 This is a diagram showing an example of the hardware configuration of a base station or a terminal according to an embodiment of the present invention.
[0031] Fig.18 It is a diagram showing an example of the structure of a vehicle according to an embodiment of the present invention. DETAILED DESCRIPTION
[0032] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In addition, the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0033] 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, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and subsequent methods (e.g., NR) unless otherwise specified.
[0034] 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-".
[0035] 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.).
[0036] 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.
[0037] (System Structure)
[0038] Figure 1 It is a diagram for explaining a wireless communication system according to an embodiment of the present invention.
[0039] like Figure 1 As shown, the wireless communication system in the embodiment of the present invention includes a base station 10 and a terminal 20. Figure 1 In the figure, one base station 10 and one terminal 20 are shown, but this is an example and a plurality of base stations 10 and a plurality of terminals 20 may be provided.
[0040] 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 in 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.
[0041] 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 known as 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.
[0042] 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 be referred to as a gNB.
[0043] Figure 2 1 is a diagram showing an example of a core network configuration according to an embodiment of the present invention. The wireless communication system includes a RAN (Radio Access Network) 10 , a terminal 20 , a core network 30 , and a DN (Data Network) 40 .
[0044] The core network 30 is a network including switches, a subscriber information management device, 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.
[0045] The U-Plane function is a function for performing 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. UPF 380 is a network node having functions such as an external PDU (Protocol Data Unit) session point for interconnection with DN 40, routing and forwarding of packets, and QoS (Quality of Service) processing of the user plane. UPF 380 controls the sending and receiving of data between DN 40 and terminal 20. UPF 380 and DN 40 can be composed of one or more network slices.
[0046] The C-Plane function group is a function group that performs a series of control processes for communication establishment, 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.
[0047] The RAN 10 is connected in a communicable manner between the core network 30 and the terminal 20, and is a network node including a base station, a line control device, etc. The RAN 10 is connected in a communicable manner with the AMF 310 and the UPF 380. In addition, the base station 10 is also referred to as the RAN 10 below.
[0048] AMF 310 is a network node having functions such as termination of RAN interface, termination of NAS (Non-Access Stratum), registration management, connection management, reachability management, mobility management, etc. NRF 340 is a network node having a function of discovering NF (Network Function) instances that provide services. UDM 320 is a network node that manages subscriber data and authentication data. UDM 320 includes UDR (User Data Repository) 321 and FE (Front End) 322 that maintain the data. FE 322 processes subscriber information.
[0049] SMF 370 is a network node with functions such as session management, IP (Internet Protocol) address allocation and management of terminal 20, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, roaming function, etc. NEF 330 is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. PCF 360 is a network node with the function of performing policy control of the network.
[0050] AF (Application Function) 390 is a network node having a function of controlling an application server.
[0051] The terminal 20 and the AMF 310 are connected as an N1 link in a manner that allows communication. The AMF 310 and the RAN 10 are connected as an N2 link in a manner that allows communication. The UPF 380 and the RAN 10 are connected as an N3 link in a manner that allows communication. The UPF 380 and the SMF 370 are connected as an N4 link in a manner that allows communication. The UPF 380 and the DN 40 are connected as an N6 link in a manner that allows communication.
[0052] Furthermore, the core network 30 of the present embodiment includes a CRMF (Computing Resource Management Function) 371 and a UCRF (User Computing Resource Function) 381 in addition to the above-mentioned conventional configuration.
[0053] UCRF 381 is a function of providing computing resources that can be used by users (subscribers) (hereinafter also referred to as user computing resource function). Hereinafter, computing resources are also referred to as containers. In addition, computing resources may also include an execution environment for executing various applications installed on the computing resources. That is, UCRF 381 has one or more containers 382. UCRF381 is included in the U-Plane function and is connected to UPF 380 as an Ny link in a manner that allows communication. In addition, UCRF 381 and DN40 are connected as an N6 link in a manner that allows communication.
[0054] CRMF 371 is a function for managing computing resources (hereinafter also referred to as computing resource management function). CRMF 371 is included in the C-Plane functional group and is connected to other network nodes included in the C-Plane functional group in a communicable manner.
[0055] The CRMF 371 and the UCRF 381 are connected to each other as an Nx link so as to be able to communicate. The names of the Nx link and the Ny link are just examples, and other names may be used.
[0056] Figure 3 1 is a sequence diagram showing an example of the process of establishing a CRMF session according to an embodiment of the present invention. In step S101, the terminal 20 sends a CRMF session establishment request to the AMF 310. The terminal 20 may set the CRMF session ID related to the termination in the AMF and the requested resource capability capacity indicating the capacity of the requested computing resource in the CRMF session establishment request. In addition, the "capacity of computing resources" recorded below may also include execution environment, capability, etc. in addition to the capacity of computing resources.
[0057] In the next step S102, AMF 310 sends a CRMF session establishment request to CRMF 371. AMF 310 includes the CRMF session ID set by terminal 20 in the CRMF session establishment request. AMF 310 may also include the requested resource capability set by terminal 20 in the CRMF session establishment request.
[0058] In the next step S103, CRMF 371 sends a subscriber information confirmation to UDM 320 in order to obtain subscriber information. In the next step S104, UDM 320 sends a subscriber information response to CRMF 371. CRMF 371 determines whether to allow the CRMF session establishment request from the terminal 20 based on the obtained subscriber information. In the case where the CRMF session establishment request from the terminal 20 is allowed by the determination, the process may proceed to step S105. On the other hand, in the case where the CRMF session establishment request from the terminal 20 is not allowed by the determination, CRMF 371 may send a response indicating that the CRMF session establishment request is rejected to AMF 310. AMF 310 may send the response to the terminal 20.
[0059] In the next step S105, CRMF 371 sends the requested resource capability capacity obtained through the CRMF session establishment request to PCF 360. In the next step S106, PCF 360 determines the capacity of computing resources provided to Terminal 20 based on the information included in the obtained requested resource capability capacity and the policy of the communication operator, and sends information including the determined capacity to CRMF 371 as a requested resource capability response.
[0060] For example, PCF 360 may decide to provide terminal 20 with computing resources of the same capacity as the requested resource capacity, or may decide to provide terminal 20 with computing resources less than the requested resource capacity, or may decide to provide terminal 20 with computing resources greater than the requested resource capacity.
[0061] In the next step S107, CRMF 371 selects UCRF 381. For example, CRMF 371 may select UCRF 381 close to terminal 20 based on the location information of terminal 20. In the next step S108, CRMF 371 sends a UCRF session establishment request to UCRF 381. CRMF 371 sets a computing resource generation request in the UCRF session establishment request. The computing resource generation request may be set based on the requested resource capability capacity, and may include information indicating the capacity of the computing resource based on the requested resource capability response obtained from PCF 360.
[0062] In the next step S109, UCRF 381 sets a container. The container may be set based on the capacity of the computing resources obtained from CRMF 371. In the next step S110, UCRF 381 sends a UCRF session establishment response to CRMF 371.
[0063] In the next step S111, the CRMF 371 sends a CRMF session establishment response to the AMF 310. In the next step S112, the AMF 310 sends a CRMF session establishment response to the terminal 20.
[0064] In step S113, the UCRF 381 may obtain an external communication IP address from, for example, an interface with the DN. In step S114, the UCRF 381 may start an application in the container. The application may be a communication application that uses the obtained external communication IP address.
[0065] In addition, after step S114 , the terminal 20 may also use the container set in the UCRF 381 to receive the service of the communication carrier.
[0066] Figure 41 is a sequence diagram showing an example of the flow of the CRMF session change process according to the embodiment of the present invention. In step S200, it is assumed that the CRMF session is already established.
[0067] In step S201, the terminal 20 specifies the CRMF session ID and sends a CRMF session change request to the AMF 310. The terminal 20 can set the change resource capability capacity in the CRMF session change request, which is information requesting to change the capacity, capability, execution environment, etc. of the computing resources of the container to be changed.
[0068] In the next step S202, AMF 310 sends a CRMF session change request to CRMF 371. AMF 310 includes the CRMF session ID set by the terminal 20 in the CRMF session change request. AMF 310 may also include the change resource capability capacity set by the terminal 20 in the CRMF session change request.
[0069] In the next step S203, the CRMF 371 determines whether to allow the CRMF session change request from the terminal 20 based on the subscriber information acquired by the own node. If the CRMF session change request from the terminal 20 is allowed by this determination, the process proceeds to step S204.
[0070] In the next step S204, CRMF 371 sends the changed resource capability capacity obtained through the CRMF session change request to PCF 360. In the next step S205, PCF 360 determines the capacity of computing resources provided to Terminal 20 based on the information included in the obtained changed resource capability capacity and the policy of the communication operator, and sends information including the determined capacity to CRMF 371 as a changed resource capability response.
[0071] For example, PCF 360 may decide to provide terminal 20 with computing resources of the same capacity as the changed resource capacity, or may decide to provide terminal 20 with computing resources of less than the changed resource capacity, or may decide to provide terminal 20 with computing resources of greater than the changed resource capacity.
[0072] In the next step S206, CRMF 371 sends a UCRF session change request to UCRF 381. CRMF 371 sets a computing resource change request in the UCRF session change request. The computing resource change request may be set based on a change resource capability capacity, and may include information indicating the capacity of computing resources based on the change resource capability response obtained from PCF 360.
[0073] In the next step S207, UCRF 381 changes the container based on the UCRF session change request. The container may be changed based on the capacity of the computing resources obtained from CRMF 371. In the next step S208, UCRF 381 sends a UCRF session change response to CRMF 371.
[0074] In the next step S209, CRMF 371 sends a CRMF session change response to AMF 310. In the next step S210, AMF 310 sends a CRMF session change response to Terminal 20.
[0075] Figure 5 1 is a sequence diagram showing an example of the flow of the service request process according to the embodiment of the present invention. In step S300, it is assumed that the CRMF session is already established.
[0076] In step S301, UCRF 381 detects that the container is not used. In the next step S302, UCRF 381 does not activate the container. UCRF 381 may not activate the container based on the policy of the communication operator when the container is not used for a certain period of time.
[0077] In step S303, the terminal 20 specifies the CRMF session ID in the list of containers to be activated, and sends a service request to the AMF 310. In the next step S304, the AMF 310 sends a context update request including an information element (IE: Information Element) indicating the container status set to "active" to the CRMF 371. In addition, the value of the information element indicating the container status can be set to "active", "activated" or "deactivated".
[0078] In the next step S305, CRMF 371 sends a UCRF session change request to UCRF 381. CRMF 371 sets a computing resource change request in the UCRF session change request. CRMF 371 may set an information element indicating the container state obtained from the context update request in the computing resource change request.
[0079] In the next step S306 , UCRF 381 activates the container based on the UCRF session change request. In the next step S307 , UCRF 381 sends a UCRF session change response to CRMF 371 .
[0080] In the next step S308, CRMF 371 sends a context update response to AMF 310. In the next step S309, AMF 310 sends a service response to Terminal 20.
[0081] Figure 6 4 is a sequence diagram showing an example of the flow of the CRMF session release process according to the embodiment of the present invention. In step S400, it is assumed that the CRMF session is in an established state.
[0082] In step S401, the terminal 20 specifies the CRMF session ID and sends a CRMF session release request to the AMF 310. In the next step S402, the AMF 310 sends a CRMF session release request to the CRMF 371. The AMF 310 includes the CRMF session ID set by the terminal 20 in the CRMF session release request.
[0083] In the following step S403, CRMF 371 sends a UCRF session release request to UCRF 381 to release the UCRF session corresponding to the CRMF session specified by the received CRMF session release request. In the following step S404, UCRF 381 releases the corresponding container based on the received UCRF session release request. In the following step S405, UCRF 381 sends a UCRF session release response to CRMF 371.
[0084] In the next step S406, CRMF 371 sends a CRMF session release response to AMF 310. In the next step S407, AMF 310 sends a CRMF session release response to Terminal 20.
[0085] (Forwarding of incoming packets to containers)
[0086] Next, the process of forwarding an incoming call to the terminal 20 to the container 382 will be described.
[0087] Figure 7 3 is a sequence diagram showing an example of the flow of the CRMF registration process according to the embodiment of the present invention. The CRMF registration process is a process of registering the CRMF 371 in the UDM 320. As a prerequisite, the "Ncrmf_CRMFSession" service that controls the CRMF session context included in the CRMF 371 is introduced into the C-Plane function group in advance.
[0088] After generating the container 382, the CRMF 371 sends a "Nudm_UECM_Registration" request to the UDM 320 (step S451). The "Nudm_UECM_Registration" request may include the NF instance ID of the CRMF 371, the CRMF session ID assigned by the terminal 20 when requesting to generate the container, the SUPI (Subscription Permanent Identifier) of the terminal, etc. The "Nudm_UECM_Registration" request is an example of requesting the UDM 320 to register the CRMF 371.
[0089] The UDM 320 sends a "Nudm_UECM_Registration" response to the CRFM 371 (step S452).
[0090] Thus, the SMF 370 can access the UDM 320 and find the CRMF 371 that manages the container of the forwarding destination and the UCRF 381 of the forwarding destination.
[0091] Figure 8 This is a sequence diagram showing an example of the process of the PDU session establishment process according to the embodiment of the present invention. The PDU session establishment process is a process of establishing a PDU session, and is the same process as in the past. The following description will focus on the differences from the past.
[0092] The terminal 20 sends a PDU session establishment request to the AMF 310 (step S501). Here, the PDU session establishment request may include an information element requesting "no response container forwarding" in addition to the previous content. "No response container forwarding" means forwarding to the container without responding.
[0093] AMF 310 sends a PDU session establishment request to SMF 370 (step S502). SMF 370 sends a PDU session corresponding policy request to PCF 360 (step S503). PCF 360 sends a PDU session corresponding policy response to SMF 370 (step S504).
[0094] The SMF 370 sends a PDU session establishment response to the AMF 310 (step S505). The AMF 310 notifies the terminal 20 of the PDU session establishment response (step S506).
[0095] Here, the PDU session corresponding policy may include an information element requesting "non-response container forwarding" in addition to the previous contents. In addition, the subscriber can set or change the PDU session corresponding policy held by the PCF 360 via the NEF 330. When the SMF 370 receives a request for "non-response container forwarding" from the terminal 20 or the PCF 360, it may save the information element requesting "non-response container forwarding" as the context of the PDU session.
[0096] The established PDU session is in a maintenance (ie, preservation) state. The following describes the forwarding process when a packet arrives at the PDU session.
[0097] Fig. 9 1 is a sequence diagram showing an example of the flow of the incoming packet forwarding determination process according to the embodiment of the present invention. The incoming packet forwarding determination process is a process for determining whether to forward an incoming packet to the container 382.
[0098] UPF 380 receives a packet from outgoing terminal 20A (step S601). In addition, outgoing terminal 20A is an example of an incoming call source. The incoming call source may be an external terminal or an external application (a network node that executes processing specified by an application, etc.). UPF 380 buffers (stores) the packet. In addition, UPF 380 is an example of a first network node that stores packets to be forwarded to computing resources set for each subscriber. Next, UPF 380 notifies SMF 370 of the incoming packet (step S602).
[0099] The SMF 370 determines whether the context of the PDU session includes "container forwarding without response" (step S603). If the SMF 370 determines that the context of the PDU session includes "container forwarding without response", it determines that the incoming packet should be forwarded to the container (step S604).
[0100] In addition, when SMF 370 determines that the context of the PDU session does not include "no response container forwarding", it sends a terminal call request to AMF 310 (step S605). AMF 310 sends a terminal call to the incoming terminal 20B (step S606). The incoming terminal 20B sends a service request to AMF 310 (step S607).
[0101] AMF 310 determines whether "container forwarding" is included in the service request (step S608). When AMF 310 determines that "container forwarding" is included in the service request, it sends an "Nsmf_PDUSession_UpdateSMContext" request including an information element requesting to forward the incoming packet to the container to SMF 370 (step S609). Therefore, SMF 370 determines that the incoming packet should be forwarded to container 382 (step S610).
[0102] In addition, when AMF 310 determines that the service request does not include "container forwarding", it sends an "Nsmf_PDUSession_UpdateSMContext" request (step S611) that does not include an information element requesting to forward the incoming packet to the container to SMF 370. Therefore, SMF 370 determines that the incoming packet should not be forwarded to container 382 (step S612).
[0103] Fig.10 FIG. 1 is a timing diagram showing an example of the process of the incoming packet forwarding process according to an embodiment of the present invention. Fig. 9 In the incoming packet forwarding judgment process shown, when SMF 370 judges that the incoming packet should be forwarded to container 382, the incoming packet is forwarded.
[0104] The SMF 370 sends a "Nudm_UECM_Get" request to the UDM 320 (step S701). The "Nudm_UECM_Get" request is set to NF type = CRMF 371, SUPI = SUPI of the incoming terminal 20B.
[0105] The UDM 320 sends a "Nudm_UECM_Get" response to the SMF 370 (step S702). The "Nudm_UECM_Get" response contains the CRMF-NF instance ID and the CRMF session ID.
[0106] Next, SMF 370 sends a "Ncrmf_CRMFSession_UpdateCRMContext" request to CRMF 371 (step S703). The "Ncrmf_CRMFSession_UpdateCRMContext" request includes the CRMF session ID and the termination information of UPF 380. In addition, SMF 370 is an example of a third network node that sends a notification to CRMF 371 that UPF 380 stores packets to be forwarded to container 382.
[0107] CRMF 371 sets the termination point of UPF 380 to UCRF 381 (and container 382) corresponding to the CRMF session ID (step S704). The termination point of UPF 380 refers to the termination point that receives the packet sent from UCRF 381 (and container 382). In addition, CRMF 371 is an example of a second network node that notifies UCRF 381 (and container 382) of the setting information for forwarding the packet. UCRF 381 sends the termination point information of UCRF 381 (and container 382) that receives the packet sent from UPF 380 to CRMF 371 (step S705).
[0108] CRMF 371 sends "Ncrmf_CRMFSession_UpdateCRMContext" response to SMF 370 (step S706). SMF 370 sets the termination point of UCRF 381 (and container 382) to UPF 380 (step S707). The termination point of UCRF 381 (and container 382) is a termination point for receiving packets sent from UPF 380.
[0109] Then, UPF 380 forwards the incoming packet to container 382 (step S708). Fig. 9 The packet received and buffered from the outgoing terminal 20A in step S601 of the incoming packet forwarding determination process is shown.
[0110] The core network 30 can be Fig. 9 The incoming packet forwarding judgment process shown and Fig.10 The incoming packet forwarding process shown forwards the incoming packet to container 382.
[0111] (Inter-container communication)
[0112] Next, an example in which a container discovers another container and communicates with the container is described. For example, it is assumed that a container searches for another container by executing an application program equipped with AI or the like, and autonomously communicates with the discovered other container.
[0113] In the following, the container is positioned as a UF (User Function) similar to an NF (Network Function). As a premise, in NRF 340, "Nnrf_UFManagement" is defined as a new service similar to the existing service "Nnrf_NFManagement", and "Nnrf_UFDiscovery" is defined as a new service similar to the existing service "Nnrf_NFDiscovery". In addition, "UFProfile" is defined as a new information element similar to the existing information element "NFProfile".
[0114] Fig.11 It is a sequence diagram showing an example of the flow of the container registration process according to the embodiment of the present invention. In addition, as a premise, when the container 382 (or CRMF 371) generates the container 382, the internal communication IP address and the external communication IP address of the container 382 are obtained in advance.
[0115] The CRMF 371 generates a "UFProfile" of the container 382 (step S801). The "UFProfile" includes a UF instance ID, a SUPI, an internal communication IP address, an external communication IP address, a CRMF-NF instance ID, and the like.
[0116] The CRMF 371 sends a "Nnrf_UFManagement_UFRegister" request to the NRF 340 (step S802). The NRF 340 is an example of a network management node that manages the network in order to discover NF instances that provide services.
[0117] In addition, the container 382 may also generate its own "UFProfile". In this case, the container 382 generates its own "UFProfile" and sends an "Nnrf_UFManagement_UFRegister" request to the NRF 340.
[0118] Fig.12 This is a sequence diagram showing an example of the flow of the inter-container communication process according to the embodiment of the present invention. The communication source container 382-1 sends "Nnrf_UFDiscovery_Request" to the NRF 340 (step S901). "Nnrf_UFDiscovery_Request" sets the SUPI of the recipient as a search keyword.
[0119] The NRF 340 sends "Nnrf_UFDiscovery_Response" to the communication source container 382-1 (step S902). The "Nnrf_UFDiscovery_Response" includes the "UFProfile" of the communication destination container 382-2.
[0120] Next, the communication source container 382-1 starts communicating with the communication destination container 382-2 (step S903).
[0121] Through the container registration step and the inter-container communication step, the communication source container can discover the communication destination container and communicate.
[0122] (Container Movement)
[0123] Next, an example of moving a container in accordance with subscriber movement or the like will be described.
[0124] The core network 30 (CRMF 371) can perform any one of the following three action modes for the movement of the container.
[0125] In the container movement mode 1, the CRMF 371 does not move the container. It is assumed that the container movement mode 1 is used for a network in the form of a converged configuration UCRF.
[0126] In container transfer mode 2, the CRMF 371 stops and deletes the container in use, and then sets a new container at the transfer destination.
[0127] In container migration mode 3, the CRMF 371 sets a new container at the migration destination while activating the container in use. Then, after the application in the container migrates the context, the CRMF 371 stops and deletes the container in use.
[0128] It is assumed that container movement pattern 2 and container movement pattern 3 are used in a network in which UCRF is distributed.
[0129] In addition, CRMF 371 may determine the necessity of container movement and the selection of container movement mode according to the judgment of PCF 360, or determine the necessity of container movement and the selection of container movement mode by itself. PCF 360 or CRMF 371 may receive the terminal location (for example, information obtained from the AMF terminal location disclosure service), the subscriber's preference related to container movement (for example, information notified by the terminal when generating the container to be the object, subscriber information), etc., and perform the necessity of container movement or the selection of container movement mode based on the received information.
[0130] Fig.13This is a sequence diagram showing an example of the flow of the container movement process in container movement mode 2 according to the embodiment of the present invention.
[0131] CRMF 371 decides to move a container (step S1001). Next, CRMF 371 requests "UFProfile" of the moving source container from NRF 340 (step S1002). NRF 340 responds "UFProfile" of the moving source container to CRMF 371 (step S1003).
[0132] Next, the CRMF 371 stops and deletes the migration source container (step S1004). Next, the CRMF 371 sets the migration destination container (step S1005). The specific steps of these steps can be found in Figure 3 Steps S108 to S110 of the CRMF session establishment process shown are the same.
[0133] In addition, the destination container may also be a container having the same "UFProfile" as the source container. In this case, CRMF 371 may assign the same CRMF session ID as the source container to the destination container and add a CRMF session ID subnumber. The destination container obtains an IP address for internal communication and an IP address for external communication.
[0134] The CRMF 371 sends a "Nnrf_UFManagement_UFUpdate" request to the NRF 340 (step S1006). The NRF 340 registers the "UFProfile" corresponding to the migration destination container as an overwrite of the "UFProfile" of the migration source container.
[0135] Fig.14 This is a sequence diagram showing an example of the flow of the container movement process in container movement mode 3 according to the embodiment of the present invention.
[0136] CRMF 371 decides to move the container (step S1101). Next, CRMF 371 requests "UFProfile" of the move source container 382-3 from NRF 340 (step S1102). NRF 340 responds "UFProfile" of the move source container 382-3 to CRMF 371 (step S1103).
[0137] Next, the CRMF 371 sets the destination container 382-4 (step S1104). Figure 3 Steps S108 to S110 of the CRMF session establishment process shown are the same.
[0138] In addition, the destination container 382-4 may be a container having the same "UFProfile" as the source container 382-3. In this case, the CRMF 371 may assign the same CRMF session ID as the source container 382-3 to the destination container 382-4 and add a CRMF session ID subnumber. The CRMF session ID subnumber may be, for example, a sequential number starting from 1. The destination container 382-4 obtains an internal communication IP address and an external communication IP address.
[0139] Next, the CRMF 371 notifies the internal communication IP address of the migration source container 382-3 to the migration destination container 382-4 (step S1105). Then, the CRMF 371 notifies the internal communication IP address of the migration destination container 382-4 to the migration source container 382-3 (step S1106).
[0140] The migration source container 382-3 migrates the context to the migration destination container 382-4 (step S1107). The context may be, for example, various data, applications, setting information, and the like.
[0141] Next, CRMF 371 stops and deletes the move source container 382-3 when the timer expires (step S1108). Then, CRMF 371 sends a "Nnrf_UFManagement_UFUpdate" request to NRF 340 (step S1109). NRF 340 registers the "UFProfile" corresponding to the move destination container 382-4 as an overwrite of the "UFProfile" of the move source container 382-3.
[0142] pass Fig.13 or Fig.14 In the container moving step shown, the core network 30 can move the container along with the movement of the subscriber, etc.
[0143] (Device Structure)
[0144] Next, the functional configuration examples of the base station 10, the terminal 20 and various network nodes that implement the above-described processing and operations are described. The base station 10, the terminal 20 and various network nodes include functions for implementing the above-described 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.
[0145] <Base Station 10 and Network Node>
[0146] Fig.15 1 is a diagram showing an example of the functional configuration of the base station 10. Fig.15As shown, the base station 10 includes a transmission unit 110 , a reception unit 120 , a setting unit 130 , and a control unit 140 . Fig.15 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 have the same functional structure as the base station 10. In addition, a network node having multiple different functions in the system architecture can be composed of multiple network nodes separated by function.
[0147] 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.
[0148] 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.
[0149] 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 verification of the geographical location 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.
[0150] <Terminal 20>
[0151] Fig.16 2 is a diagram showing an example of the functional structure of the terminal 20. Fig.16 As shown, the terminal 20 includes a transmitting unit 210 , a receiving unit 220 , a setting unit 230 , and a control unit 240 . Fig.16 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.
[0152] 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 signal or reference signal, etc. sent from the network node.
[0153] The setting unit 230 stores various setting information received from the network node by the receiving unit 220 in a storage device, and reads it from the storage device as needed. In addition, the setting unit 230 also stores pre-set setting information.
[0154] 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.
[0155] <Structure Related to This Embodiment>
[0156] (Item 1)
[0157] A network node, comprising:
[0158] a receiving unit that receives a notification of an incoming call from an external terminal or an external application; and
[0159] A control unit determines whether to forward the incoming call to a computing resource set for each subscriber.
[0160] (Item 2)
[0161] The network node according to item 1, wherein
[0162] The control unit determines whether to forward the incoming call to the computing resource based on whether an information element indicating that the incoming call is to be forwarded to the computing resource is included in the context of the PDU session.
[0163] (Item 3)
[0164] The network node according to item 1 or 2, wherein:
[0165] The receiving unit receives, from another network node, a determination result based on whether the service request received from the terminal at the incoming call destination includes an information element indicating that the incoming call is forwarded to the computing resource.
[0166] The control unit determines whether to forward the incoming call to the computing resource based on the determination result.
[0167] (Item 4)
[0168] A communication method, which is performed by a network node, comprises the following steps:
[0169] Receiving notification of an incoming call from an external terminal or an external application; and
[0170] A determination is made as to whether to forward the incoming call to a computing resource set for each subscriber.
[0171] According to any of the above structures, a technique is provided for enabling a subscriber to use a computing resource on a network and, when necessary, forwarding incoming packets from a terminal or an application to the computing resource. According to item 2, it is possible to determine whether to forward an incoming call to a computing resource based on the context of a PDU session. According to item 3, it is possible to determine whether to forward an incoming call to a computing resource based on a service request received from a terminal at the destination of the incoming call.
[0172] (Hardware Structure)
[0173] The block diagram used in the description of the above embodiment ( Fig.15 and Fig.16 ) 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.
[0174] 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 performs a sending function is called a transmitting unit or a transmitter. In short, as mentioned above, there is no particular limitation on the implementation method.
[0175] 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.171 is a diagram showing an example of a hardware structure 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 structure as the base station 10. The USIM may 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.
[0176] 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.
[0177] 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.
[0178] 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.
[0179] 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.15 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.16 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.
[0180] 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.
[0181] 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.
[0182] 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.
[0183] 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).
[0184] 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.
[0185] 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.
[0186] Fig.18 FIG. 2 shows a structural example of a vehicle 2001. Fig.18 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 form / 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.
[0187] 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.
[0188] 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 provided 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).
[0189] 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.
[0190] 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 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 provides various multimedia information and multimedia services to passengers of the vehicle 2001 using information obtained from external devices via the communication module 2013 and the like.
[0191] 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.
[0192] 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 transmits and receives 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 2029 via the communication port 2033.
[0193] 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.
[0194] The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to the external device via wireless communication. In addition, the communication module 2013 also transmits the rotation speed signal of the front and rear wheels obtained by the rotation speed sensor 2022, the air pressure signal of the front and rear wheels obtained by the air pressure sensor 2023, the vehicle speed signal obtained by the vehicle speed sensor 2024, the acceleration signal obtained by the acceleration sensor 2025, the accelerator pedal stepping amount signal obtained by the accelerator pedal sensor 2029, the brake pedal stepping amount signal obtained by the brake pedal sensor 2026, the shift lever operation signal obtained by the shift lever sensor 2027, and the detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 2028 to the external device via wireless communication.
[0195] 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. 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.
[0196] (Supplementary Implementation Methods)
[0197] The above describes the embodiments of the present invention, but the disclosed invention is not limited to such embodiments, and those skilled in the art should understand various variations, modifications, alternatives, replacements, etc. In order to promote 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 can be used. The item distinction in the above description is not essential to the present invention. You can use the items recorded in more than two items in combination as needed, or you can apply the items recorded in a certain item 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.
[0198] 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)), high-level 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 be referred to as an RRC message, for example, it may also be an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0199] 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, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A and 5G, etc.) may also be applied.
[0200] 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.
[0201] 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).
[0202] 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.
[0203] 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.
[0204] 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).
[0205] 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.
[0206] 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.
[0207] 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 be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.
[0208] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may 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.
[0209] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0210] 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, a wireless resource may be indicated by an index.
[0211] 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.
[0212] In the present disclosure, 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 are used interchangeably. Sometimes, the base station is also referred to as macro cell, small cell, femto cell, pico cell and the like.
[0213] 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 for indoor use (RRH: Remote Radio Head)). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of at least one of a base station and a base station subsystem that provide communication services within the coverage area.
[0214] In the present disclosure, terms such as “mobile station (MS)”, “user terminal (user terminal)”, “user equipment (UE)”, and “terminal” may be used interchangeably.
[0215] 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.
[0216] 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 may be a means of transportation (e.g., a car, an airplane, etc.), a mobile body that moves in an unmanned manner (e.g., a drone, an autonomous vehicle, 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 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.
[0217] 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.
[0218] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station may have the functions of the user terminal.
[0219] 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 "judged" or "determined", etc. In addition, "determining" and "determining" may include matters that have been received (for example, receiving information), transmitted (for example, sending information), input, output, accessed (for example, accessed data in memory) as matters that have been "judged" 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 "judged" or "determined". That is, "judgment" and "decision" may include certain actions that are considered to be "judged" or "decided". In addition, "judgment (decision)" may also be replaced by "assuming", "expecting", "considering", etc.
[0220] 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 situation where there is 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 to replace "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.
[0221] 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.
[0222] The phrase “based on” used in the present disclosure does not mean “based only on” unless otherwise explicitly stated. In other words, the phrase “based on” means both “based only on” and “based at least on”.
[0223] 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.
[0224] The “unit” in the configuration of each of the above-mentioned devices may be replaced with a “section”, “circuit”, “device” or the like.
[0225] 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.
[0226] 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 be a fixed time length (e.g., 1 ms) that is independent of a numerology.
[0227] 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.
[0228] 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.
[0229] 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.
[0230] 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.
[0231] 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 not be referred to as a subframe, but as a time slot, a mini time slot, or the like.
[0232] 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.
[0233] 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 be shorter than the TTI.
[0234] 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) can be the minimum time unit for scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit for scheduling can be controlled.
[0235] 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.
[0236] In addition, for a 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 (for example, a shortened TTI, etc.), it can be understood as a TTI with a TTI length less than that of a long TTI (long TTI) and greater than 1ms.
[0237] 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.
[0238] 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.
[0239] 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.
[0240] 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.
[0241] 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.
[0242] 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.
[0243] 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".
[0244] 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.
[0245] 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 a case where the noun following the article is in a plural form.
[0246] 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".
[0247] 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 predetermined information (e.g., notification of "yes X") is not limited to being performed explicitly, but may also be performed implicitly (e.g., not notifying the predetermined information).
[0248] 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.
[0249] Description of symbols
[0250] 10: Base Station (RAN)
[0251] 110: Sending Department
[0252] 120: Receiving Department
[0253] 130: Setting department
[0254] 140: Control Department
[0255] 20: Terminal
[0256] 30: Core Network
[0257] 40: DN
[0258] 210: Sending Department
[0259] 220: Receiving Department
[0260] 230: Setting department
[0261] 240: Control Department
[0262] 310:AMF
[0263] 320: UDM
[0264] 330:NEF
[0265] 340: NRF
[0266] 350:AUSF
[0267] 360: PCF
[0268] 370: SMF
[0269] 371: CRMF
[0270] 380:UPF
[0271] 381: UCRF
[0272] 382: Container
[0273] 390:AF
[0274] 1001: Processor
[0275] 1002: Storage device
[0276] 1003: Auxiliary storage device
[0277] 1004: Communication device
[0278] 1005: Input device
[0279] 1006: Output device
[0280] 2001: Vehicles
[0281] 2002: Drive Department
[0282] 2003: Steering
[0283] 2004: Accelerator pedal
[0284] 2005: Brake pedal
[0285] 2006: Gear Lever
[0286] 2007: Front wheel
[0287] 2008: Rear wheel
[0288] 2009: Axles
[0289] 2010: Electronic Control Department
[0290] 2012: Information Services Department
[0291] 2013: Communication Module
[0292] 2021: Current Sensors
[0293] 2022: Speed Sensor
[0294] 2023: Air pressure sensor
[0295] 2024: Vehicle speed sensor
[0296] 2025: Accelerometers
[0297] 2026: Brake pedal sensor
[0298] 2027: Gearshift sensor
[0299] 2028: Object detection sensors
[0300] 2029: Accelerator pedal sensor
[0301] 2030: Driving Assistance Systems Division
[0302] 2031: Microprocessors
[0303] 2032: Memory (ROM, RAM)
[0304] 2033: Communication port (IO port)
Claims
1. A network node, comprising: a receiving unit that receives a notification of an incoming call from an external terminal or an external application; and A control unit determines whether to forward the incoming call to a computing resource set for each subscriber.
2. The network node according to claim 1, wherein: The control unit determines whether to forward the incoming call to the computing resource based on whether an information element indicating that the incoming call is to be forwarded to the computing resource is included in the context of the PDU session.
3. The network node according to claim 1 or 2, wherein: The receiving unit receives, from another network node, a determination result based on whether the service request received from the terminal at the incoming call destination includes an information element indicating that the incoming call is forwarded to the computing resource. The control unit determines whether to forward the incoming call to the computing resource based on the determination result.
4. A communication method, which is performed by a network node, comprising the following steps: Receiving notification of an incoming call from an external terminal or an external application; and A determination is made as to whether to forward the incoming call to a computing resource set for each subscriber.
