WO2020187184A1 - Procédé et appareil d'obtention d'informations de tranche de réseau - Google Patents

Procédé et appareil d'obtention d'informations de tranche de réseau Download PDF

Info

Publication number
WO2020187184A1
WO2020187184A1 PCT/CN2020/079511 CN2020079511W WO2020187184A1 WO 2020187184 A1 WO2020187184 A1 WO 2020187184A1 CN 2020079511 W CN2020079511 W CN 2020079511W WO 2020187184 A1 WO2020187184 A1 WO 2020187184A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice
function
network
terminal device
event
Prior art date
Application number
PCT/CN2020/079511
Other languages
English (en)
Inventor
Cheng Wang
Ping Chen
Xiao Li
Huiwei ZHENG
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020187184A1 publication Critical patent/WO2020187184A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/63—Location-dependent; Proximity-dependent

Definitions

  • the present disclosure relates generally to the technology of communication system, and in particular, to a method and an apparatus for obtaining network slice information.
  • Network slicing concept is used to fulfill rich requirements from various use cases.
  • Various network services with different characteristics will be exposed to third party applications/users/operators as capabilities to enable various new business models.
  • a specific network service can be instantiated according to on demand requirements for third party users/operators, and the business policy between the network service providers and network service consumers.
  • NSSP Network slicing selection Policy
  • a terminal device such as a user equipment, UE
  • UE may run the application using the connection setup within the designated network slice which has pre-defined features, e.g. quality of service that can fulfill certain business model.
  • NSSP is usually pre-configured in the UE, or provisioned to UE from core network e.g. via policy control function, PCF.
  • Slice information about terminal device, such as the slice type cannot be obtained by other network function, nor third party applications/users/operators.
  • network functions, and/or third party applications/users/operators may be able to obtain slice information about a terminal device.
  • a first aspect of the present disclosure provides a method performed at a server function, comprising: sending a request for obtaining slice information about at least one terminal device; and receiving a response including the slice information about the at least one terminal device.
  • the request is an event subscription request for at least one event type.
  • An event type in the at least one event type is about the slice information.
  • the response is an event notification.
  • the event subscription request includes: at least one external slice type.
  • the at least one external slice type includes at least one of: eMBB slice, URLLC slice, or eMTC slice; wherein eMBB refers to enhanced mobile broadband, URLLC refers to ultra reliable low latency communications, and eMTC refers to enhanced machine type communication.
  • the event subscription request includes at least one of: slice tenant information; location information; or at least one event condition.
  • the method further comprises: triggering a pre-determined action, based on the slice information about the at least one terminal device.
  • the server function comprises: an application function, AF, or a service capability server/application server, SCS/AS.
  • the server function sends, to an exposure function, the request for obtaining the slice information about the at least one terminal device; and the server function receives, from the exposure function, the response including the slice information about the at least one terminal device.
  • the exposure function comprises: a network exposure function, NEF.
  • the at least one terminal device comprises: a user equipment, UE.
  • a second aspect of the present disclosure provides a method performed at an exposure function, comprising: receiving a first request for obtaining slice information about at least one terminal device; mapping the first request to a second request; sending, to at least one network function, the second request; receiving, from a network function in the at least one network function, a second response; mapping the second response to a first response including the slice information about the at least one terminal device; and sending the first response.
  • the exposure function receives the first request, from a server function or a network function; and the exposure function sends the first response, to the server function or the network function.
  • the first request is an event subscription request for at least one event type; an event type in the at least one event type is about the slice information; and the first response is an event notification.
  • the first request includes: at least one external slice type.
  • the at least one external slice type includes at least one of: eMBB slice, URLLC slice, or eMTC slice; and eMBB refers to enhanced mobile broadband, URLLC refers to ultra reliable low latency communications, and eMTC refers to enhanced machine type communication.
  • the first request includes at least one of: slice tenant information; location information; or at least one event condition.
  • the second request is an event subscription request; and the second response is an event notification.
  • the second request includes: at least one internal slice type.
  • the at least one internal slice type is indicated by at least one of: NSSAI, SST, SD, or NSI ID; and NSSAI refers to network slice selection assistance information, SST refers to slice/service type, SD refers to slice differentiator; and NSI ID refers to network slice instance identifier.
  • the second request includes at least one of: slice tenant information; location information; or at least one event condition.
  • the method further comprises: storing the slice information about the at least one terminal device.
  • the method further comprises: determining whether to authorize the first request.
  • the server function comprises: an application function, AF, or a service capability server/application server, SCS/AS.
  • the exposure function comprises: a network exposure function, NEF.
  • the network function comprises at least one of: an access and mobility management function, AMF; a session management function, SMF; a network slice selection function, NSSF; a unified data management, UDM; or a policy control function, PCF.
  • the at least one terminal device comprises: a user equipment, UE.
  • a third aspect of the present disclosure provides a method performed at a network function, comprising: receiving, from an exposure function, a request for obtaining slice information about at least one terminal device; and sending, to the exposure function, a response including the slice information about the at least one terminal device.
  • the method further comprises: obtaining the slice information about the at least one terminal device, based on a registration procedure of the at least one terminal device.
  • the method further comprises: obtaining the slice information about the at least one terminal device, based on a session establishment procedure of the at least one terminal device.
  • the method further comprises: obtaining the slice information about the at least one terminal device, from another network function.
  • the network function sends, via another network function, to the exposure function, the response including the slice information about the at least one terminal device.
  • the request is an event subscription request for at least one event type.
  • An event type in the at least one event type is about the slice information.
  • the response is an event notification.
  • the event subscription request includes at least one internal slice type.
  • the at least one internal slice type is indicated by at least one of: NSSAI, SST, SD, or NSI ID; and NSSAI refers to network slice selection assistance information, SST refers to slice/service type, SD refers to slice differentiator, and NSI ID refers to network slice instance identifier.
  • the event subscription request further includes at least one of: slice tenant information; location information; or at least one event condition.
  • the exposure function comprises: a network exposure function, NEF.
  • the network function comprises at least one of: an access and mobility management function, AMF; a session management function, SMF; a network slice selection function, NSSF; a unified data management, UDM; or a policy control function, PCF.
  • the network function is UDM.
  • the method comprises: obtaining the slice information about the at least one terminal device, based on UECM registration procedure; and UECM refers to user equipment context management service.
  • the terminal device comprises: a user equipment, UE.
  • a fourth aspect of the present disclosure provides a network node, comprising: a processor; and a memory, containing instructions executable by the processor.
  • the network node is operative to implement any of the methods above mentioned in the first aspect.
  • a fifth aspect of the present disclosure provides a network node, comprising: a processor; and a memory, containing instructions executable by the processor.
  • the network node is operative to implement any of the methods above mentioned in the second aspect.
  • a sixth aspect of the present disclosure provides a network node, comprising: a processor; and a memory, containing instructions executable by the processor.
  • the network node is operative to implement any of the methods above mentioned in the third aspect.
  • a seventh aspect of the present disclosure provides a computer readable storage medium having a computer program stored thereon.
  • the computer program is executable by a device to cause the device to carry out any of the methods above mentioned.
  • a eighth aspect of the present disclosure provides a server function, comprising: a sending unit, configured to send a request for obtaining slice information about at least one terminal device; and a receiving unit, configured to receive a response including the slice information about the at least one terminal device.
  • a ninth aspect of the present disclosure provides an exposure function, comprising: a first receiving unit, configured to receive a first request for obtaining slice information about at least one terminal device; a first mapping unit, configured to map the first request to a second request; a second sending unit, configured to send, to at least one network function, the second request; a second receiving unit, configured to receive, from a network function in the at least one network function, a second response; a second mapping unit, configured to map the second response to a first response including the slice information about the at least one terminal device; and a first sending unit, configured to send the first response.
  • a tenth aspect of the present disclosure provides a network function, comprising: a receiving unit, configured to receive, from an exposure function, a request for obtaining slice information about at least one terminal device; and a sending unit, configured to send, to the exposure function, a response including the slice information about the at least one terminal device.
  • FIG. 1 is an exemplary diagram showing a simplified structure of a communication network
  • FIG. 2 is an exemplary flow chart showing a method for obtaining slice information about terminal device, according to embodiments of the present disclosure
  • FIG. 3 is an exemplary flow chart showing another method for obtaining slice information about terminal device, according to embodiments of the present disclosure
  • FIG. 4 is an exemplary flow chart showing still another method for obtaining slice information about terminal device, according to embodiments of the present disclosure
  • FIG. 5 is an exemplary diagram showing more details about functions and procedures in the communication system
  • FIG. 6 is a block diagram showing blocks of the functions in accordance with embodiments of the present disclosure.
  • FIG. 7 is a block diagram showing a computer readable storage medium in accordance with embodiments of the present disclosure.
  • FIG. 8 is a schematic showing units of the server application
  • FIG. 9 is a schematic showing units of the exposure function 200.
  • FIG. 10 is a schematic showing units of the network function 300.
  • 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.
  • node 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, SCE, 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, SCE, network exposure function, NEF
  • 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 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. More generally, however, 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.
  • 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
  • terminal device encompasses a device which is able to communicate with a network node, such as a base station, or with another wireless device by transmitting and/or receiving wireless signals.
  • a network 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 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 diagram showing a simplified structure of a communication network.
  • a network includes a plurality of network functions, NF 300 (NF 1, NF 2...NF n, n is an integer) .
  • the network provides network exposure capability to enable suitable access/exchange of network information to a server function or terminal device.
  • the server function, SF such as application function, AF 100 (AF 1, AF 2, AF 3) , uses application program interfaces, API 500 (API 1, API 2, API 3...API n, n is an integer) of the exposure functions, EF, such as network exposure function, NEF 200 (NEF 1, NEF 2) , so as to access/exchange network information.
  • the Network Exposure Function may support exposure of capabilities of network functions, using information collecting via network internal interfaces, and exposing towards Application Function (AF) via proper APIs.
  • the terminal device such as the user equipment, UE, 400 may receive service form the AF 100 via the communication network.
  • the AF 100 may be lack of enough information about whether the UE 400 has connected to a proper enterprise slice corresponding to the service or not. If an improper slice is used by the UE 400, the quality of service might be affected, or the service might have to be stopped.
  • FIG. 2 is an exemplary flow chart showing a method for obtaining slice information about terminal device, according to embodiments of the present disclosure.
  • the method is performed at a server function, such as the application function 100.
  • the method comprises: step S101, sending a request for obtaining slice information about at least one terminal device; and step S102, receiving a response including the slice information about the at least one terminal device.
  • the server function such as the application function 100, needs the slice information about at least one terminal device.
  • the server function sends a request and receives a response including the slice information about the at least one terminal device. Therefore, the server function may be aware of the certain slice used by the terminal device, and the connection to improper slice may be avoided.
  • the request may be an event subscription request for at least one event type.
  • An event type in the at least one event type is about the slice information.
  • the response is an event notification.
  • an event mechanism in the communication system may be further utilized.
  • the server function may only sends one request to subscribe such event, then whenever the event happens the server function will receive notification including the slice information.
  • the server function may monitor the slice information of the terminal device continuously, without repeatedly sending requests about the slice information. Further, the request may also be used to simultaneously subscribe other event, or get other information, which is not related to the slice.
  • the event subscription request includes: at least one external slice type.
  • the at least one external slice type includes at least one of: eMBB slice, URLLC slice, or eMTC slice; wherein eMBB refers to enhanced mobile broadband, URLLC refers to ultra reliable low latency communications, and eMTC refers to enhanced machine type communication.
  • the server function may be aware of whether the terminal device is connected to proper slice type.
  • the event subscription request may include at least one of: slice tenant information; location information; or at least one event condition.
  • the server function may monitor all the tenant slices for the server function.
  • the server function may monitor the location where the terminal device is connected to the slice. Further, the server function may indicate specifically in which condition the event is regarded as happened.
  • the method further comprises: triggering a pre-determined action, based on the slice information about the at least one terminal device.
  • the server function may trigger different actions. For example, the service from the server function may or may not continue.
  • the terminal device may be routed from the improper slice to proper slice.
  • the server function comprises: an application function, AF, or a service capability server/application server, SCS/AS.
  • the application function is provided as one example for the server function.
  • the server function may include a service capability server/application server, SCS/AS.
  • the server function sends, to an exposure function, the request for obtaining the slice information about the at least one terminal device; and the server function receives, from the exposure function, the response including the slice information about the at least one terminal device.
  • the server function communicates with exposure function for the slice information.
  • the AF 100 may use API 500 of the NEF 200, to obtain the slice information.
  • the exposure function may comprise: a network exposure function, NEF.
  • the at least one terminal device may comprise: a user equipment, UE.
  • FIG. 3 is an exemplary flow chart showing another method for obtaining slice information about terminal device, according to embodiments of the present disclosure.
  • the method is performed at an exposure function 200.
  • the method comprises: step S201, receiving a first request for obtaining slice information about at least one terminal device; step S202, mapping the first request to a second request; step S203, sending, to at least one network function, the second request; step S204, receiving, from a network function in the at least one network function, a second response; step S205, mapping the second response to a first response including the slice information about the at least one terminal device; and step S206, sending the first response.
  • the exposure function 200 may obtain a second response from any network function in the at least one network function.
  • the second response may include different kinds of slice information.
  • the exposure function 200 may further map the second response to the first response, which includes information as the first request indicates.
  • the exposure function receives the first request, from a server function or a network function; and the exposure function sends the first response, to the server function or the network function.
  • the exposure function may provide the slice information to any other authorized function/node/entity, including a server function or a network function.
  • the first request is an event subscription request for at least one event type; an event type in the at least one event type is about the slice information; and the first response is an event notification.
  • the first request includes: at least one external slice type.
  • the at least one external slice type includes at least one of: eMBB slice, URLLC slice, or eMTC slice; and eMBB refers to enhanced mobile broadband, URLLC refers to ultra reliable low latency communications, and eMTC refers to enhanced machine type communication.
  • the first request includes at least one of: slice tenant information; location information; or at least one event condition.
  • the second request is an event subscription request; and the second response is an event notification.
  • the second request includes: at least one internal slice type.
  • the at least one internal slice type is indicated by at least one of: NSSAI, SST, SD, or NSI ID; and NSSAI refers to network slice selection assistance information, SST refers to slice/service type, SD refers to slice differentiator; and NSI ID refers to network slice instance identifier.
  • the second request includes at least one of: slice tenant information; location information; or at least one event condition.
  • the external slice type may be used for the external function/node/entity of the communication network, such as the server function
  • the internal slice type may be used for the internal function/node/entity of the communication network, such as the network function.
  • slice information may be selectively exposed from the internal of the communication network to the external of the communication network.
  • the method further comprises: storing the slice information about the at least one terminal device, such as in a storage function, e.g. user data repository, UDR.
  • a storage function e.g. user data repository, UDR.
  • the event context may be logged for further service or applications.
  • the method further comprises: determining whether to authorize the first request. Namely, the exposure function may reject unauthorized request, so as to improve security.
  • the server function comprises: an application function, AF, or a service capability server/application server, SCS/AS.
  • the exposure function comprises: a network exposure function, NEF.
  • the network function comprises at least one of: an access and mobility management function, AMF; a session management function, SMF; a network slice selection function, NSSF; a unified data management, UDM; or a policy control function, PCF.
  • the at least one terminal device comprises: a user equipment, UE.
  • FIG. 4 is an exemplary flow chart showing still another method for obtaining slice information about terminal device, according to embodiments of the present disclosure.
  • the method is performed at a network function.
  • the method comprises: step S301, receiving, from an exposure function, a request for obtaining slice information about at least one terminal device; and step S302, sending, to the exposure function, a response including the slice information about the at least one terminal device.
  • any network function in the communication network which may obtain/store the slice information about the terminal device during the communication procedures, may provide such information to the exposure function under request.
  • the method further comprises: obtaining the slice information about the at least one terminal device, based on a registration procedure of the at least one terminal device.
  • any network function which may obtain/store the slice information about the terminal device during the registration procedure of the at least one terminal device, may provide such information to the exposure function under request.
  • the method further comprises: obtaining the slice information about the at least one terminal device, based on a session establishment procedure of the at least one terminal device. Further, the session may be established for a data connection.
  • the method further comprises: obtaining the slice information about the at least one terminal device, from another network function.
  • the network function sends, via another network function, to the exposure function, the response including the slice information about the at least one terminal device.
  • the slice information may be further transferred between network functions and exposure function, without any limitation.
  • a flexible usage of the slice information may be improved in the communication network.
  • the request is an event subscription request for at least one event type.
  • An event type in the at least one event type is about the slice information.
  • the response is an event notification.
  • the event subscription request includes at least one internal slice type.
  • the at least one internal slice type is indicated by at least one of: NSSAI, SST, SD, or NSI ID; and NSSAI refers to network slice selection assistance information, SST refers to slice/service type, SD refers to slice differentiator, and NSI ID refers to network slice instance identifier.
  • the event subscription request further includes at least one of: slice tenant information; location information; or at least one event condition.
  • the exposure function comprises: a network exposure function, NEF.
  • the network function comprises at least one of: an access and mobility management function, AMF; a session management function, SMF; a network slice selection function, NSSF; a unified data management, UDM; or a policy control function, PCF.
  • the network function is UDM.
  • the method comprises: obtaining the slice information about the at least one terminal device, based on UECM registration procedure; and UECM refers to user equipment context management service.
  • the UDM is listed. Further, a corresponding UECM registration procedure is listed as example. During this procedure, the UDM obtains the slice information about the terminal device.
  • the terminal device comprises: a user equipment, UE.
  • FIG. 5 is an exemplary diagram showing more details about functions and procedures in the communication system.
  • the AF 100 subscribes to EF/NEF 200 on event for slice information, and provides the target UE (s) e.g. UE ID or UE group ID.
  • AF 100 may further specific the event conditions, such as specific slice information to be monitored, e.g. Slice type, location where the UE attach to network slice.
  • AF 100 with identifier “AFid-1” subscribes a “slice event” for one of its enterprise user UE 400.
  • the request to subscribe the event includes:
  • GPSI Generic Public Subscription Identifier
  • v2x refers to “vehicle to everything” ;
  • Event conditions “Registration” or “Data connection” .
  • This request procedure may be named as Nnef_EventExposure_Subscribe, for example.
  • NEF 200 checks the event subscription and authorize that the AF 100 can subscribe such event with the indicated event conditions, e.g. the AF can monitor UE (s) attaching on a certain network slice.
  • NEF 200 may also map the slice information provided by AF 100 to the internal slice information such as NSSAI, SST, SD etc.
  • S-NSSAI refers to Single Network Slice Selection Assistance Information.
  • NEF 200 may further determine Event conditions “Registration” shall trigger a 5th generation core network, 5GC, internal event subscription to AMF 300a via UDM 300d; and Event conditions “Data connection” shall trigger 5GC internal event subscription to SMF 300b via UDM 300d.
  • NEF 200 subscribes to receive event (s) from 5GC NF (s) on slice information and provides the associated notification endpoint of event, and the target UE (s) e.g. UE ID or UE group ID.
  • the 5GC NF which provides such events can be UDM 300d, AMF 300a, SMF 300b, NSSF 300c, and/or PCF (not shown in FIG. 5) .
  • NEF 200 may subscribe event and receive event notify directly from these 5GC NF (s) , or indirectly via an intermediate 5GC NF (s) .
  • NEF 200 send subscription request to UDM 300d for “slice event” .
  • This procedure may be named as Nudm_EventExposure_Subscribe, for example.
  • the SUPI refers to Subscription Permanent Identifier.
  • This procedure may be named as Namf_EventExposure_Subscribe, for example.
  • UDM 300d also subscribe “slice event” to SMF 300b.
  • This procedure may be named as Nsmf_EventExposure_Subscribe, for example.
  • AMF 300a performs network slice selection procedure.
  • step 6 when a network slice is selected for the UE 400, and the UE 400 is the target of slice information event, AMF 300a trigger event notification.
  • AMF 300a may send UE’s selected slice information to UDM 300d via Nudm_UECM_registration procedure.
  • UDM 300d further notifies the event to NEF 200.
  • AMF 300a may report UE’s selected slice information to UDM 300d via Namf_EventExposure_Notify procedure.
  • UDM further notify the event to NEF 200.
  • AMF 300a may directly report UE’s selected slice information to NEF 200 via Namf_EventExposure_Notify procedure.
  • NEF 200 checks the event notify; then NEF 200 may also map the slice information provided by 5GC NF (s) , such as NSSAI, SST, SD etc., to the external slice information such as tenant info, external readable slice type “eMBB” , “v2x” .
  • 5GC NF s
  • s 5GC NF
  • NEF 200 may also store the event content in a storage e.g. UDR.
  • NEF 200 sends the event notify to AF 100 with mapped slice information in the event content.
  • This procedure may be named as Nnef_EventExposure_Notify, for example.
  • AF 100 checks the event notify and can trigger a specific action, such as provisioning NSSP for UE 400.
  • steps 10-11 when UE 400 requests packet data unit, PDU connection with 5GC into the network, AMF 300a performs session establishment procedure.
  • AMF 300a may trigger PDU session establishment procedure with SMF 300b in network slice “S-NSSAI-1” .
  • AMF 300a may further trigger step5-9 to report event for slice information, while replacing the event condition “Registration” with “Data connection” .
  • SMF 300b may also report event, during or after PDU session establishment procedure.
  • SMF 300b may send UE’s selected slice information to UDM 300d via Nudm_UECM_registration procedure; UDM 300d further notify the event to NEF 200.
  • SMF may report UE’s selected slice information to UDM via Nsmf_EventExposure_Notify procedure; UDM further notify the event to NEF 200.
  • SMF 300b may directly report UE’s selected slice information to NEF 200 via Nsmf_EventExposure_Notify procedure.
  • step 6c-9 is further triggered to report event for slice information.
  • UE 400 and the data network transmit data via a selected slice.
  • the slice may be further changed if AF 100 triggers a specific action, e.g. in step 9. And the corresponding steps in the FIG. 5 may be further repeatedly triggered, without limitation.
  • FIG. 6 is a block diagram showing blocks of the functions in accordance with embodiments of the present disclosure.
  • the server function e.g. the application function 100, comprises: a processor 101; and a memory 102, containing instructions executable by the processor 101.
  • the server function e.g. the application function 100, is operative to implement any of the methods above mentioned, such as the method showing in FIG. 2. Namely, the server function, e.g. the application function 100 may be operative to: send (S101) a request for obtaining slice information about at least one terminal device; and receive (S102) a response including the slice information about the at least one terminal device.
  • the exposure function 200 comprises: a processor 201; and a memory 202, containing instructions executable by the processor 201.
  • the exposure function 200 is operative to implement any of the methods above mentioned, such as the method shown in FIG. 3. Namely, the exposure function 200 may be operate to: receive (S201) a first request for obtaining slice information about at least one terminal device; map (S202) the first request to a second request; send (S203) , to at least one network function, the second request; receive (S204) , from a network function in the at least one network function, a second response; map (S205) the second response to a first response including the slice information about the at least one terminal device; and send (S206) the first response.
  • the network function 300 comprises: a processor 301; and a memory 302, containing instructions executable by the processor 301.
  • the network function 300 is operative to implement any of the methods above mentioned, such as the method shown in FIG. 4. Namely, the network function 300 may be operative to: receive (S301) , from an exposure function, a request for obtaining slice information about at least one terminal device; and send (S302) , to the exposure function, a response including the slice information about the at least one terminal device.
  • the processors 101, 201, 301 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 memories 102, 202, 302 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. 7 is a block diagram showing a computer readable storage medium in accordance with embodiments of the present disclosure.
  • the computer readable storage medium 700 having a computer program 701 stored thereon.
  • the computer program 701 is executable by a device to cause the device to carry out any of the methods above mentioned, such as the methods shown in FIGs. 2-5.
  • the computer readable storage medium 700 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. 8 is a schematic showing units of a network node, which is or comprises the application function 100.
  • the server function e.g. the application function 100, comprises: a sending unit 1001, configured to send (S101) a request for obtaining slice information about at least one terminal device; and a receiving unit 1002, configured to receive (S201) a response including the slice information about the at least one terminal device.
  • FIG. 9 is a schematic showing units of a network node, which is or comprises the exposure function 200.
  • the exposure function 200 comprising: a first receiving unit 2001, configured to receive (S201) a first request for obtaining slice information about at least one terminal device; a first mapping unit 2002, configured to map (S202) the first request to a second request; a second sending unit 2003, configured to send (S203) , to at least one network function, the second request; a second receiving unit 2004, configured to receive (S204) , from a network function in the at least one network function, a second response; a second mapping unit 2005, configured to map (S205) the second response to a first response including the slice information about the at least one terminal device; and a first sending unit 2006, configured to send (S206) the first response.
  • a first receiving unit 2001 configured to receive (S201) a first request for obtaining slice information about at least one terminal device
  • a first mapping unit 2002 configured to map (S202) the first request to a second request
  • a second sending unit 2003 configured to send (S203) , to at least one network function, the second request
  • FIG. 10 is a schematic showing units of a network node, which is or comprises the network function 300.
  • the network function 300 comprises: a receiving unit 3001, configured to receive (S301) , from an exposure function, a request for obtaining slice information about at least one terminal device; and a sending unit 3002, configured to send (S302) , to the exposure function, a response including the slice information about the at least one terminal device.
  • the term 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 server function e.g. application function 100, exposure function 200, or network function 300 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.
  • these network functions may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
  • the server function such as the application function 100, needs the slice information about at least one terminal device.
  • the server function may send a request and receives a response including the slice information about the at least one terminal device. Therefore, the server function may be aware of the certain slice used by the terminal device, and the connection to improper slice may be avoided.
  • an event mechanism in the communication system may be further utilized. This is, a particular event type about slice information is provided.
  • the server function may only send one request to subscribe such event, then whenever the event happens the server function will receive notification including the slice information.
  • the server function may monitor the slice information of the terminal device continuously, without repeatedly sending requests about the slice information. Further, the request may also be used to simultaneously subscribe other event, or get other information, which is not related to the slice.
  • 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 Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Certains modes de réalisation de la présente invention concernent un procédé et un appareil d'obtention d'informations de tranche de réseau. Un procédé mis en œuvre au niveau d'une fonction de serveur comporte les étapes consistant à: émettre (S101) une demande visant à obtenir des informations de tranche concernant au moins un dispositif terminal; et recevoir (S102) une réponse incluant les informations de tranche concernant le ou les dispositifs terminaux. Selon des modes de réalisation de la présente invention, des fonctions de réseau, et/ou des applications/utilisateurs/opérateurs tiers, peuvent être en mesure d'obtenir des informations de tranche concernant un dispositif terminal.
PCT/CN2020/079511 2019-03-17 2020-03-16 Procédé et appareil d'obtention d'informations de tranche de réseau WO2020187184A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2019078409 2019-03-17
CNPCT/CN2019/078409 2019-03-17

Publications (1)

Publication Number Publication Date
WO2020187184A1 true WO2020187184A1 (fr) 2020-09-24

Family

ID=72519597

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/079511 WO2020187184A1 (fr) 2019-03-17 2020-03-16 Procédé et appareil d'obtention d'informations de tranche de réseau

Country Status (1)

Country Link
WO (1) WO2020187184A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
WO2018038489A1 (fr) * 2016-08-22 2018-03-01 삼성전자 주식회사 Procédé de demande d'authentification entre un terminal et un serveur tiers dans un système de communication sans fil, terminal associé et dispositif de gestion d'instance de tranche de réseau
WO2018084593A1 (fr) * 2016-11-03 2018-05-11 주식회사 케이티 Procédé de traitement de données sur la base d'une tranche de réseau, et appareil associé
WO2018233808A1 (fr) * 2017-06-20 2018-12-27 Motorola Mobility Llc Création d'une règle de politique de sélection de tranche de réseau

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018038489A1 (fr) * 2016-08-22 2018-03-01 삼성전자 주식회사 Procédé de demande d'authentification entre un terminal et un serveur tiers dans un système de communication sans fil, terminal associé et dispositif de gestion d'instance de tranche de réseau
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
WO2018084593A1 (fr) * 2016-11-03 2018-05-11 주식회사 케이티 Procédé de traitement de données sur la base d'une tranche de réseau, et appareil associé
WO2018233808A1 (fr) * 2017-06-20 2018-12-27 Motorola Mobility Llc Création d'une règle de politique de sélection de tranche de réseau

Similar Documents

Publication Publication Date Title
US20220240173A1 (en) Method and apparatus for managing network slice for terminal device
WO2020248582A1 (fr) Procédés et appareils pour pont tsn logique
US11968729B2 (en) Method and apparatus for allocating PDU session ID for terminal device
US20220232051A1 (en) Method and apparatus for restoration of proxy call session control function
US20220338156A1 (en) Methods and apparatuses for event exposure of location reporting for a terminal device
WO2020187184A1 (fr) Procédé et appareil d'obtention d'informations de tranche de réseau
US11985045B2 (en) Method and apparatus for subscribing change notification of network function
WO2022199411A1 (fr) Procédé et appareil pour fournir une configuration pour servir un dispositif terminal
WO2021031904A1 (fr) Procédé et entité permettant de transmettre une pluralité d'adresses mac
EP4189933B1 (fr) Procédés et appareils de commande de politique
US20230370834A1 (en) Method and apparatus for improved capability exposure at edge enabler server
US11647379B2 (en) Methods and apparatuses for exposure of monitoring event
WO2023279977A1 (fr) Noeuds de réseau et procédés associés pour la surveillance d'événements
WO2020215486A1 (fr) Procédé et appareil pour une session nidd gérée par fonction de réseau
WO2023274366A1 (fr) Procédé et appareil d'établissement de session avec une qualité de service requise
WO2021077298A1 (fr) Procédé et appareil pour arrêter un service retardé
CN118138457A (zh) 提供用于服务终端设备的配置的方法和装置

Legal Events

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

Ref document number: 20774062

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20774062

Country of ref document: EP

Kind code of ref document: A1