Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/12—Setup of transport tunnels
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/16—Discovering, processing access restriction or access information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/18—Selecting a network or a communication service
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
  • H04W8/08—Mobility data transfer
  • H04W8/14—Mobility data transfer between corresponding nodes
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/11—Allocation or use of connection identifiers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/14—Backbone network devices
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/18—Service support devices; Network management devices

Definitions

• the present disclosure relates generally to the technology of communication system, and in particular, to a method and an apparatus for a network function managing NIDD session.
• a protocol data unit (PDU) Connectivity Service provides exchange of PDUs between a terminal device (such as a user equipment, UE) , and a data network identified by a data network name (DNN) .
• the PDU Connectivity Service is supported via PDU Sessions that may be established upon request from the UE.
• Each PDU Session supports a single PDU Session type, i.e. supports the exchange of a single type of PDU requested by the UE at the establishment of the PDU Session.
• PDU Session types are defined: internet protocol version 4 (IPv4) , IPv6, IPv4v6, Ethernet, and Unstructured.
• IPv4 internet protocol version 4
• IPv6 IPv4v6, Ethernet
• Unstructured IPv6
• the data delivery via an unstructured PUD session may also be named as non-ID data delivery, NIDD.
• MO Mobile Originated
• MT Mobile Terminated
• Non-IP Non-IP
• a network function managing such NIDD session does not know how to select the specific one of the different mechanisms.
• the efficiency of managing NIDD session is affected, or the establishment of the NIDD session might fail sometimes due to an improper selection of the mechanism.
• Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges.
• various embodiments which address one or more of the issues disclosed herein. Namely, according to embodiments of the present disclosure, the selection between the different mechanisms for NIDD session may be configured explicitly. Thus, the efficiency of managing NIDD session is improved.
• a first aspect of the present disclosure provides a method performed at a network function, comprising: receiving a request for establishing a NIDD session, wherein NIDD refers to non-internet protocol data delivery; and selecting a user plane function, UPF, or a network exposure function, NEF, for establishing the NIDD session.
• the network function selects the UPF, or the NEF, based on a session management data.
• the session management data comprises: an indication of the UPF, or the NEF.
• the indication has a boolean value; and a true value of the boolean value indicates to select the NEF, and a false value or an absence of the boolean value indicates to select the UPF.
• the session management data further comprises: an identity of the NEF.
• the session management data further comprises: information for a connection from the network function to the NEF; and the information for the connection from the network function to the NEF includes at least one of: an external group identifier, an external identifier, a mobile station international subscriber directory number, MSISDN, or an application function identifier.
• the method further comprises: obtaining the session management data from a unified data management, UDM.
• the UDM obtains the session management data from a unified data repository, UDR.
• the session management data is provisioned by an operator.
• the method further comprises: obtaining, from a network repository function, NRF, service information about the NEF, when the NEF is selected.
• the method further comprises: transmitting, to the NEF, a create request for the NIDD session; and receiving, from the NEF, a response for the create request for the NIDD session.
• the network function comprises: a session management function, SMF.
• the network function receives the request for establishing the NIDD session from an access and mobility management function, AMF.
• a second aspect of the present disclosure provides an apparatus for a network function, comprising: a processor; and a memory, containing instructions executable by the processor.
• the apparatus is operative to: receive a request for establishing a NIDD session, wherein NIDD refers to non-internet protocol data delivery; and select a user plane function, UPF, or a network exposure function, NEF, for establishing the NIDD session.
• the apparatus is further operative to implement the method according to any of the above embodiments.
• a third aspect of the present disclosure provides an apparatus for a network function, comprising: a reception unit, configured to receive a request for establishing a NIDD session, wherein NIDD refers to non-internet protocol data delivery; and a selection unit, configured to select a user plane function, UPF, or a network exposure function, NEF, for establishing the NIDD session.
• a reception unit configured to receive a request for establishing a NIDD session, wherein NIDD refers to non-internet protocol data delivery
• a selection unit configured to select a user plane function, UPF, or a network exposure function, NEF, for establishing the NIDD session.
• a fourth aspect of the present disclosure provides a computer readable storage medium having a computer program stored thereon, the computer program executable by a device to cause the device to carry out the method according to any of the above embodiments.
• FIG. 1 is an exemplary flow chart showing a method performed at a network function, according to embodiments of the present disclosure
• FIG. 2 is another exemplary flow chart showing a method performed at a network function, according to embodiments of the present disclosure
• FIG. 3 is an exemplary diagram showing a procedure for obtaining the session management data from UDM
• FIG. 4 is an exemplary flow chart showing other steps in the method, according to embodiments of the present disclosure.
• FIG. 5 is an exemplary diagram showing a procedure of provisioning NIDD and non-NIDD session management data
• FIG. 6 is an exemplary diagram showing a procedure of controlling session establishment, based on non-NIDD session management data
• FIG. 7 is an exemplary diagram showing a procedure of controlling session establishment, based on NIDD session management data
• FIG. 8 is a block diagram showing the network node, according to embodiments of the present disclosure.
• FIG. 9 is a block diagram showing a computer readable storage medium, according to embodiments of the present disclosure.
• FIG. 10 is a block diagram showing function units of the network node, according to embodiments of the present disclosure.
• the term “network” refers to a network/system following any suitable communication standards, such as new radio (NR) , long term evolution (LTE) , LTE-Advanced, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , and so on.
• NR new radio
• LTE long term evolution
• WCDMA wideband code division multiple access
• HSPA high-speed packet access
• the communications between a terminal device and a network node in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
• network function refers to a network device/apparatus/entity with accessing capability in a communication network via which a terminal device accesses to the network and receives services therefrom.
• the node/function may include a base station (BS) , an access point (AP) , a multi-cell/multicast coordination entity (MCE) , a server node/function (such as a service capability server/application server, SCS/AS, group communication service application server, GCS AS, application function, AF) , an exposure node (such as a service capability exposure function, SCEF, network exposure function, NEF) , a controller or any other suitable device in a wireless communication network.
• BS base station
• AP access point
• MCE multi-cell/multicast coordination entity
• server node/function such as a service capability server/application server, SCS/AS, group communication service application server, GCS AS, application function, AF
• an exposure node such as a service capability exposure function, SCEF, network exposure function, N
• the BS may be, for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNodeB or gNB) , a remote radio unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth.
• NodeB or NB node B
• eNodeB or eNB evolved NodeB
• gNodeB or gNB next generation NodeB
• RRU remote radio unit
• RH radio header
• RRH remote radio head
• relay a low power node such as a femto, a pico, and so forth.
• the network function/node comprise multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, positioning nodes and/or the like.
• MSR multi-standard radio
• RNCs radio network controllers
• BSCs base station controllers
• BTSs base transceiver stations
• transmission points transmission nodes
• positioning nodes positioning nodes and/or the like.
• the network node may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a terminal device access to a wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network.
• terminal device encompasses a device which is able to communicate with a network function/node such as a base station, or with another wireless device by transmitting and/or receiving wireless signals.
• a network function/node such as a base station
• terminal device encompasses, but is not limited to: a mobile phone, a stationary or mobile wireless device for machine-to-machine communication, an integrated or embedded wireless card, an externally plugged in wireless card, a vehicle, etc.
• a terminal device may also be called an IoT device and represent a machine or other device that performs monitoring, sensing and/or measurements etc., and transmits the results of such monitoring, sensing and/or measurements etc. to another terminal device and/or a network equipment.
• the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3rd generation partnership project (3GPP) context be referred to as a machine-type communication (MTC) device.
• M2M machine-to-machine
• 3GPP 3rd generation partnership project
• the terminal device may be a user equipment, UE, implementing the 3GPP narrow band Internet of things (NB-IoT) standard.
• NB-IoT 3GPP narrow band Internet of things
• machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches etc.
• a terminal device may represent a vehicle or other equipment, for example, a medical instrument that is capable of monitoring, sensing and/or reporting etc. on its operational status or other functions associated with its operation.
• the terms “first” , “second” and so forth refer to different elements.
• the singular forms “a” and “an” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
• the term “based on” is to be read as “based at least in part on” .
• the term “one embodiment” and “an embodiment” are to be read as “at least one embodiment” .
• the term “another embodiment” is to be read as “at least one other embodiment” .
• Other definitions, explicit and implicit, may be included below.
• FIG. 1 is an exemplary flow chart showing a method performed at a network function, according to embodiments of the present disclosure.
• the method performed at a network function comprises: S101, receiving a request for establishing a NIDD session, wherein NIDD refers to non-internet protocol data delivery; and S102, selecting a user plane function, UPF, or a network exposure function, NEF, for establishing the NIDD session.
• the NIDD from the UE to the application function, AF may be accomplished by one of the following two mechanisms:
• the selection between the different mechanisms for NIDD session may be configured explicitly.
• the efficiency of managing NIDD session is improved.
• FIG. 2 is another exemplary flow chart showing a method performed at a network function, according to embodiments of the present disclosure.
• the method may further comprise: S103, obtaining the session management data from a unified data management, UDM. Then, in the step S102, the network function may select the UPF, or the NEF, based on a session management data.
• the session management data, or named as the session management subscription data, in UDM may contain specific information for NIDD session management.
• the network function comprises: a session management function, SMF.
• the SMF may determine which one of the above two mechanisms should be used for Unstructured PDU session establishment: delivery using NEF via NIDD channel or using UPF via N6 channel.
• FIG. 3 is an exemplary diagram showing a procedure for obtaining the session management data from UDM.
• a NF service consumer e.g. SMF 10 sends a request to the UDM 20 to receive the UE's session management subscription data (see also 3rd generation partnership project technical specification, 3GPP TS, 29.503 V15.3.0) .
• the request contains the UE's identity (/ ⁇ supi ⁇ ) , the type of the requested information (/sm-data) , and query parameters (single-nssai, dnn, supported-features, plmn-id) .
• the term “supi” refers to Subscription Permanent Identifier.
• the term “sm-data” refers to session management-data.
• the term “single-nssai” refers to Single Network Slice Selection Assistance Information.
• the term “dnn” refers to data network name.
• the term “plmn-id” refers to Public Land Mobile Network Identifier.
• the NF service consumer (e.g. SMF) 10 sends a GET request to the resource representing the UE's session management subscription data, with query parameters indicating the selected network slice and/or the DNN and/or supported-features and/or plmn-id.
• step 32a on success, the UDM responds with "200 OK" , the message body containing the UE's session management subscription data as relevant for the requesting NF service consumer.
• the exemplary data structure about session management subscription data may be listed as follows.
• SessionManagementSubscriptionData (from 3GPP TS 29.503 V15.3.0, Clause 6.1.6.2.8)
• step 32b if there is no valid subscription data for the UE, or if the UE subscription data exists, but the requested session management subscription is not available (e.g. query parameter contains network slice and/or DNN that does not belong to the UE subscription) , HTTP status code "404 Not Found” shall be returned including additional error information in the response body (in the "ProblemDetails" element) .
• the SMF obtains the session management data from the UDM, utilizing currently existing procedures. Therefore, no extra procedure is needed during NIDD. The efficiency for establishing the NIDD session is improved.
• the session management data comprises: an indication of the UPF, or the NEF.
• the indication has a boolean value; and a true value of the boolean value indicates to select the NEF, and a false value or an absence of the boolean value indicates to select the UPF.
• the session management data further comprises: an identity of the NEF.
• the session management data further comprises: information for a connection from the network function to the NEF; and the information for the connection from the network function to the NEF includes at least one of: an external group identifier, an external identifier, a mobile station international subscriber directory number, MSISDN, or an application function identifier.
• the external group identifier, the external identifier, MSISDN are about the UE, and the application function identifier is about the application function, AF.
• the specific session management data for NIDD may be constructed based on the data structure shown in table 1, and/or table 2.
• the specific session management data in embodiments of the present disclosure comprises: an updated NIDD configuration as follows.
• NiddDnnConfiguration (updated based on table 2)
• the specific session management data for NIDD may be constructed based on the data structure currently existing, by adding an explicit indicator and/or other information.
• the selection by the SMF will be processed explicitly, with an update to the current processing algorithm.
• the update cost to current network functions, in software or hardware, may be reduced.
• numeric rather than a boolean value may be alternatively utilized for the indicator.
• a numeric “1” may replace the true value, and a numeric “0” may replace the false value.
• FIG. 4 is an exemplary flow chart showing other steps in the method, according to embodiments of the present disclosure.
• the method may further comprise: S104, obtaining, from a network repository function, NRF, service information about the NEF, when the NEF is selected.
• the method may further comprise: S105, transmitting, to the NEF, a create request for the NIDD session; and S106, receiving, from the NEF, a response for the create request for the NIDD session.
• FIG. 5 is an exemplary diagram showing a procedure of provisioning NIDD and non-NIDD session management data.
• the session management data is provisioned by an operator.
• FIG. 5 shows following steps of provisioning NIDD configuration:
• Step 501 operator 30 creates the DNN configuration with PDU type as “Structured” , together with other information such as DNN name, S-NSSAI etc. (table 2) through the provisioning system 40; non-NIDD session management data may refers to session management data rather than NIDD type, such as IPv4, IPv6, IPv4v6, Ethernet, etc.
• Step 502 the provisioning system 40 creates the non-NIDD session management data for the applied UE into UDR 50;
• Step 503 UDR 50 persistent the non-NIDD session management data for the UE;
• Step 504 UDR 50 respond to the Provisioning System 40 for the success of the persistence of non-NIDD session management data
• Step 505 The Provisioning system 40 confirmed operator 30’s provisioning operation
• Step 506 operator 30 creates the DNN configuration with PDU type as “Unstructured” , together with other information such as DNN name, S-NSSAI etc. (table 3) through the provisioning system 40;
• Step 507 the provisioning system 40 creates the NIDD session management data for the applied UE into UDR 50;
• Step 508 UDR 50 persistent the NIDD session management data for the UE
• Step 509 UDR 50 responds to the Provisioning System 40 for the success of the persistence of NIDD session management data
• Step 510 The Provisioning system 40 confirmed operator 30’s provisioning operation.
• FIG. 6 is an exemplary diagram showing a procedure of controlling session establishment, based on non-NIDD session management data.
• FIG. 6 shows following steps of controlling session establishment, based on non-NIDD session management data:
• Step 601 SMF 10 received the PDU session establishment request from AMF with requested PDU session type as “Structured” (represent for PDU session type of IPv4, IPv6, IPv4v6 etc. ) ;
• Step 602 SMF 10 could decide to get the non-NIDD session management data from UDM based on the requested PDU session type as Structured, the input data include SUPI, DNN, S-NSSAI etc;
• Step 603 UDM 20 retrieve the non-NIDD session management data from UDR if provisioned in UDR;
• Step 604 UDM 20 respond SMF with non-NIDD session management data
• Step 605 SMF 10 determine on the non-NIDD session management data to select UPF for the requested PDU session ( “Structured” ) ;
• Step 606 SMF 10 start UPF selection
• Step 607 SMF 10 could select UPF 80 form local configuration if has;
• Step 608 SMF 10 try to discover UPF 80 from NRF 70 and select eligible one to serve the PDU session establishment; step 608 is alternative for step 607;
• Step 609 SMF 10 send N4 session establish request to the selected UPF 80;
• Step 610 UPF 80 process the request and respond to the SMF 10 for the session info of the created non-NIDD session.
• FIG. 7 is an exemplary diagram showing a procedure of controlling session establishment, based on NIDD session management data.
• the UDM obtains the session management data from a unified data repository, UDR.
• the network function receives the request for establishing the NIDD session from an access and mobility management function, AMF.
• Figure 7 depicts the sequence flow for the PDU session establishment for NIDD session ( “Unstructured” ) .
• SMF 10 gets the NIDD session management data from UDM 20 and based on that info to decide how to establish the UE requested PDU session, either towards UPF or towards NEF 90.
• SMF 10 determines to execute the UPF selection or use NEF ID, then continue the PDU session establishment procedures.
• FIG. 7 shows following steps of controlling session establishment, based on NIDD session management data:
• Step 701 UE send request to AMF 60 through the radio access network (RAN) to establish a PDU session ( “Unstructured” ) .
• the AMF 60 determines that the message corresponds to a request for a new PDU Session based on that Request Type indicates "initial request” and that the PDU Session ID is not used for any existing PDU Session (s) of the UE.
• AMF 60 selects a SMF 10 and send Nsmf_PDUsession_CreateSMContext request to SMF 10 with requested PDU session type as “Unstructured” ;
• Step 702 SMF 10, based on the requested PDU session type ( “Unstructure” ) , sends a Nudm_SDM GET request to the resource representing the UE's NIDD session management subscription data, with query parameters indicating the selected network slice and/or the DNN and/or supported-features and/or plmn-id;
• Step 703 UDM 20, if stateless, gets the UE NIDD session management subscription data from UDR 50; with the embodiment as table 3, for UE NIDD session management data, both the flag “invoke NEF selection” and NEF ID provisioned before shall be returned to UDM 20;
• Step 704 On success, the UDM 20 responds with "200 OK" , the message body containing the UE's NIDD session management subscription data;
• the UDM 20 will send, in the response to the SMF 20, the NIDD session management data with “invoke NEF selection” set to true and the NEF ID which shall be used for the NIDD session and other NIDD information such as External Group Identifier, External Identifier, MSISDN or AF ID used for the SMF-NEF connection, the protocol data shall be updated as embodiment in table 3;
• Step 705 SMF 10, when received the NIDD session management data, determines, based on whether the “invoke NEF selection” flag is set, to execute UPF selection or use the NEF ID;
• Step 706 SMF 10 decides (base on the NIDD session management data) to execute UPF selection if there is no “invoke NEF selection” flag in the response or the flag is set to false;
• Step 707 SMF 10 select UPF 80 from local configuration if has;
• Step 708 SMF 10 discover UPF 80 from NRF 70 and select one eligible UPF for the UE requested PDU session; step 708 is alternative for step 707;
• Step 709 If Request Type indicates "initial request” , the SMF initiates an N4 Session Establishment procedure with the selected UPF;
• Step 710 UPF 80 processes the request and respond to the SMF 10 for the session info of the created NIDD session;
• Step 711 SMF 10 use the NEF ID if there is “invoke NEF selection” flag in the NIDD session management data set to true and NEF ID present (Step 5) , SMF 10 may query NRF 70 to get service info of this NEF ID;
• Step 712 SMF 10 shall create a PDU session towards the NEF 90, the SMF invokes Nnef_SMContext_Create Request; the parameters in the Nnef_SMContext_Create Request may contain: User identity, PDU session ID, NEF ID, NIDD information, S-NSSAI, DNN etc; if no AF has previously performed the NIDD Configuration procedure with the NEF 90 for the user identity received, then the NEF 90 initiates the NIDD configuration procedure (for configuring necessary information for data delivery via the NIDD) before step 713;
• Step 713 The NEF 90 creates a NEF PDU session Context, the NEF 90 invokes Nnef_SMContext_Create Request Response;
• the NEF 90 creates a NEF PDU session Context and associates it with the User Identity and PDU session ID, the Nef_SMContext_Create Request Response message may contain: User Identity, PDU session ID, NEF ID, S-NSSAI, DNN etc. NEF 90 confirms towards the SMF the establishment of the PDU session in NEF for the UE.
• Steps 711-713 are alternative for steps 706-710.
• the selection between the different mechanisms for NIDD session may be configured explicitly.
• the efficiency of managing NIDD session is improved.
• session management data or named as the session management subscription data, in UDM may contain specific information for NIDD session management.
• the SMF obtains the session management data from the UDM, utilizing currently existing procedures. Therefore, no extra procedure is needed during NIDD session establishment. The efficiency for establishing the NIDD session is improved.
• the specific session management data for NIDD may be constructed based on the data structure shown in table 1, and/or table 2. According to embodiments of the present disclosure, the specific session management data for NIDD may be constructed based on the data structure currently existing, by adding an explicit indicator and/or other information. The selection by the SMF will be processed explicitly, with an update to the current processing algorithm. The update cost to current network functions, in software or hardware, may be reduced.
• FIG. 8 is a block diagram showing the network node, according to embodiments of the present disclosure.
• a second aspect of the present disclosure provides an apparatus for a network function 10, such as the SMF 10, comprising: a processor 1001; and a memory 1002, containing instructions executable by the processor 1001.
• the apparatus is operative to: receive (S101) a request for establishing a NIDD session, wherein NIDD refers to non-internet protocol data delivery; and select (S102) a user plane function, UPF, or a network exposure function, NEF, for establishing the NIDD session.
• the apparatus is further operative to implement the method according to any of the above embodiments, such as the methods in FIGs. 1, 2, 4.
• the processor 1001 may be any kind of processing component, such as one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs) , special-purpose digital logic, and the like.
• the memory 1002 may be any kind of storage component, such as read-only memory (ROM) , random-access memory, cache memory, flash memory devices, optical storage devices, etc.
• FIG. 9 is a block diagram showing a computer readable storage medium, according to embodiments of the present disclosure.
• the computer readable storage medium 130 having a computer program 1301 stored thereon, the computer program 1301 is executable by a device to cause the device to carry out the method according to any of the above embodiments, such as the methods in FIGs. 1, 2, 4.
• the computer readable storage medium 130 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
• memory such as RAM, ROM, programmable read-only memory (PROM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
• FIG. 10 is a block diagram showing function units of the network node, according to embodiments of the present disclosure.
• the apparatus for a network function 10 comprises: a reception unit 1010, configured to receive a request for establishing a NIDD session, wherein NIDD refers to non-internet protocol data delivery; and a selection unit 1020, configured to select a user plane function, UPF, or a network exposure function, NEF, for establishing the NIDD session.
• a reception unit 1010 configured to receive a request for establishing a NIDD session, wherein NIDD refers to non-internet protocol data delivery
• a selection unit 1020 configured to select a user plane function, UPF, or a network exposure function, NEF, for establishing the NIDD session.
• unit/function unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
• the network node 10 may not need a fixed processor or memory, any computing resource and storage resource may be arranged from at least one network node/device/entity/apparatus in the communication system.
• the virtualization technology and network computing technology may be further introduced, so as to improve the usage efficiency of the network resources and the flexibility of the network.
• the various exemplary embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
• some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
• firmware or software may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
• While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
• the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may include circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.
• exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices.
• program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device.
• the computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc.
• the functionality of the program modules may be combined or distributed as desired in various embodiments.
• the functionality may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.
• FPGA field programmable gate arrays

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Databases & Information Systems (AREA)
• Mobile Radio Communication Systems (AREA)
• Computer And Data Communications (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Applications Claiming Priority (2)

Publications (2)

Family

ID=72940684

Family Applications (1)

Country Status (6)

Families Citing this family (1)

Family Cites Families (12)

• 2019
  • 2019-06-28 MX MX2021013027A patent/MX2021013027A/es unknown
  • 2019-06-28 WO PCT/CN2019/093805 patent/WO2020215486A1/en active Search and Examination
  • 2019-06-28 JP JP2021562317A patent/JP7387757B2/ja active Active
  • 2019-06-28 US US17/604,879 patent/US12075496B2/en active Active
  • 2019-06-28 EP EP19926023.3A patent/EP3959940A4/de active Pending
  • 2019-06-28 CN CN201980095800.7A patent/CN113728721B/zh active Active
  • 2019-06-28 CN CN202211566074.2A patent/CN116209093A/zh active Pending

Also Published As

Similar Documents

Legal Events