WO2020088594A1 - Procédé et appareil de transmission de données - Google Patents

Procédé et appareil de transmission de données Download PDF

Info

Publication number
WO2020088594A1
WO2020088594A1 PCT/CN2019/114750 CN2019114750W WO2020088594A1 WO 2020088594 A1 WO2020088594 A1 WO 2020088594A1 CN 2019114750 W CN2019114750 W CN 2019114750W WO 2020088594 A1 WO2020088594 A1 WO 2020088594A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
function
network function
access
nssai
Prior art date
Application number
PCT/CN2019/114750
Other languages
English (en)
Inventor
Ganhong ZHOU
Yunjie Lu
Juying GAN
Nianshan SHI
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 WO2020088594A1 publication Critical patent/WO2020088594A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • 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

Definitions

  • the non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for data transmission.
  • FIG. 1 is a diagram illustrating an exemplary 5G system architecture according to an embodiment of the present disclosure, which is a copy of Figure 4.2.3-1 of 3rd Generation Partnership Project (3GPP) TS23.501 and the disclosure of 3GPP TS23.501 is incorporated by reference herein in its entirety.
  • 5G system architecture may comprise a plurality of network functions (NFs) such as Authentication Server Function (AUSF) , Access and Mobility Management Function (AMF) , Data Network (DN) (e.g.
  • NFs network functions
  • AUSF Authentication Server Function
  • AMF Access and Mobility Management Function
  • DN Data Network
  • Network Exposure Function NEF
  • NEF Network Repository Function
  • NSF Network Slice Selection Function
  • PCF Policy Control Function
  • SMF Session Management Function
  • UDM Unified Data Management
  • UPF User Plane Function
  • AF Application Function
  • UE User Equipment
  • FIG. 2 shows a registration with AMF re-allocation procedure used to reroute a non-access stratum (NAS) message of the UE to a target AMF during a registration procedure, which is a copy of Figure 4.2.2.2.3-1 of 3GPP TS23.502 and the disclosure of 3GPP TS23.502 is incorporated by reference herein in its entirety.
  • NAS non-access stratum
  • a method implemented at a first network function may comprise obtaining information related to network slice selection; and sending a reroute message to an access network node, wherein the reroute message including a container comprising at least one information element of the information related to network slicing selection.
  • a method implemented at an access network node may comprise receiving a reroute message from a first network function, wherein the reroute message including a container comprising at least one information element of information related to network slicing selection; and sending the second registration request and the container to a second network function.
  • a method implemented at a second network function may comprise receiving from an access network node a registration request and a container comprising at least one information element of information related to network slicing selection; and processing the registration request.
  • an apparatus implemented at a first network function.
  • the apparatus may comprise a processor; and a memory coupled to the processor, said memory containing instructions executable by said processor, whereby said apparatus is operative to obtain information related to network slice selection; and send a reroute message to an access network node, wherein the reroute message including a container comprising at least one information element of the information related to network slicing selection.
  • an apparatus implemented at an access network node.
  • the apparatus may comprise a processor; and a memory coupled to the processor, said memory containing instructions executable by said processor, whereby said apparatus is operative to receive a reroute message from a first network function, wherein the reroute message including a container comprising at least one information element of information related to network slicing selection; and send the registration request including the container to a second network function.
  • an apparatus implemented at a second network function.
  • the apparatus may comprise a processor; and a memory coupled to the processor, said memory containing instructions executable by said processor, whereby said apparatus is operative to receive from an access network node a registration request including a container comprising at least one information element of information related to network slicing selection; and process the registration request.
  • an apparatus implemented at a first network function.
  • the apparatus may comprise an obtaining unit configured to obtain information related to network slice selection; a sending unit configured to send a reroute message to an access network node, wherein the reroute message including a container comprising at least one information element of the information related to network slicing selection.
  • an apparatus implemented at an access network node.
  • the apparatus may comprise a receiving unit configured to receive a reroute message from a first network function, wherein the reroute message including a container comprising at least one information element of information related to network slicing selection; a sending unit configured to send the second registration request and the container to a second network function.
  • an apparatus implemented at a second network function.
  • the apparatus may comprise a receiving unit configured to receive from an access network node a registration request and a container comprising at least one information element of information related to network slicing selection; a processing unit configured to process the registration request.
  • a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the first aspect of the disclosure.
  • a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the second aspect of the disclosure.
  • a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the third aspect of the disclosure.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out the method according to the first aspect of the disclosure.
  • a fourteenth aspect of the disclosure there is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out the method according to the second aspect of the disclosure.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out the method according to the third aspect of the disclosure.
  • At least one information element of the information related to network slicing selection can be included in a container and transferred from the first network function such as Initial AMF to a second network function such as target AMF.
  • the container may be added in the Reroute NAS message and the Initial UE message. Therefore the second network function such as the target AMF can get the at least one information element included in the container.
  • This container is transparent to the access network node, i.e., the access network node can forward the container to other node without decoding
  • FIG. 1 is a diagram illustrating an exemplary 5G system architecture according to an embodiment of the present disclosure
  • FIG. 2 shows a registration with AMF re-allocation procedure used to reroute a NAS message of the UE to a target AMF during a registration procedure
  • FIG. 3 shows a flowchart of a method according to an embodiment of the present disclosure
  • FIG. 4 shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 5 shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 6 shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 7a illustrates simplified block diagrams of an apparatus according to an embodiment of the present disclosure
  • FIG. 7b illustrates simplified block diagrams of an apparatus according to another embodiment of the present disclosure
  • FIG. 7c illustrates simplified block diagrams of an apparatus according to another embodiment of the present disclosure
  • FIG. 8 illustrates simplified block diagrams of an apparatus according to another embodiment of the present disclosure.
  • FIG. 9 illustrates simplified block diagrams of an apparatus according to another embodiment of the present disclosure.
  • FIG. 10 illustrates simplified block diagrams of an apparatus according to another embodiment of the present disclosure.
  • the term “network” refers to a network following any suitable wireless/wired communication standards such as new radio (NR) , long term evolution (LTE) , LTE-Advanced, and so on.
  • NR new radio
  • LTE long term evolution
  • the terms “network” and “system” can be used interchangeably.
  • the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by some of standards organizations such as 3GPP, the International Organization for Standardization (ISO) , the International Telecommunication Union (ITU) , the Institute of Electrical and Electronics Engineers (IEEE) , and the Internet Engineering Task Force (IETF) , etc.
  • the communication protocols as defined by 3GPP may comprise the fourth generation (4G) , 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • the term “network device” refers to a network device in a communication network via which a terminal device accesses to the network and receives services therefrom.
  • the network device may comprise access network device and core network device.
  • the access network device may comprise base station (BS) , an Integrated Access and Backhaul (IAB) node, an access point (AP) , a multi-cell/multicast coordination entity (MCE) , etc.
  • BS base station
  • IAB Integrated Access and Backhaul
  • AP access point
  • MCE multi-cell/multicast coordination entity
  • 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.
  • the core network device may comprise a plurality of network devices which may offer numerous services to the customers who are interconnected by the access network device. Each access network device is connectable to the core network device over a wired or wireless connection.
  • network function refers to any suitable function which can be implemented in a network device of a wireless/wired communication network.
  • the network function may comprise AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R) AN, 5G-Equipment Identity Register (5G-EIR) , Security Edge Protection Proxy (SEPP) , Network Data Analytics Function (NWDAF) , Unified Data Repository (UDR) , Unstructured Data Storage Function (UDSF) , etc.
  • 5G-EIR 5G-Equipment Identity Register
  • SEPP Security Edge Protection Proxy
  • NWDAF Unified Data Repository
  • USF Unstructured Data Storage Function
  • terminal device refers to any end device that can access a communication network and receive services therefrom.
  • the terminal device may refer to a mobile terminal, a user equipment (UE) , a terminal device, or other suitable devices.
  • the terminal device may be, for example, a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a portable computer, an image capture device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA) , a portable computer, a desktop computer, a wearable device, a vehicle-mounted wireless device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE) , a laptop-mounted equipment (LME) , a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like.
  • a portable computer an image capture device such as a digital camera, a gaming terminal device, a music storage and a playback appliance
  • a mobile phone a cellular phone
  • a smart phone a voice over IP (VoIP) phone
  • VoIP voice
  • a UE may represent a terminal device configured for communication in accordance with one or more communication standards promulgated by the 3GPP, such as 3GPP’ LTE standard or NR standard.
  • 3GPP 3GPP’ LTE standard or NR standard.
  • a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device.
  • a terminal device may be configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the wireless communication network.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
  • a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment.
  • the UE may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • a UE may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • references in the specification to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • FIG. 1 may represent a high level architecture in the next generation network such as 5G.
  • the system architecture of FIG. 1 only depicts some exemplary elements such as AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R) AN.
  • a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device.
  • the communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices’ access to and/or use of the services provided by, or via, the communication system.
  • the UE can establish a signaling connection with the AMF over the reference point N1, as illustrated in FIG. 1.
  • This signaling connection may enable NAS signaling exchange between the UE and the core network, comprising a signaling connection between the UE and the (R) AN and the N2 connection for this UE between the (R) AN and the AMF.
  • the (R) AN can communicate with the UPF over the reference point N3.
  • the UE can establish a packet data unit (PDU) session to the DN (e.g. an operator network or Internet) through the UPF over the reference point N6.
  • PDU packet data unit
  • the exemplary system architecture also contains the service-based interfaces such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf and Nsmf exhibited by NFs such as the NRF, the NEF, the AUSF, the UDM, the PCF, the AMF and the SMF.
  • FIG. 1 also shows some reference points such as N1, N2, N3, N4, N6 and N9, which can support the interactions between NF services in the NFs.
  • these reference points may be realized through corresponding NF service-based interfaces and by specifying some NF service consumers and providers as well as their interactions in order to perform a particular system procedure.
  • Various NFs shown in Fig. 1 may be responsible for functions such as session management, mobility management, authentication, and security. These may be critical for delivering a service in the network.
  • the AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R) AN may include the functionality for example as defined in 3GPP TS 23.501 or its future version.
  • the NEF may act as a gateway which can enable external users to monitor, provision and enforce an application policy for users inside the network.
  • the AUSF may be configured as an authentication server.
  • the UDM can store subscriber data and profiles.
  • the PCF can provide a policy framework incorporating network slicing, roaming and mobility management.
  • the AMF can manage access control and mobility.
  • the SMF can set up and manage sessions according to a network policy.
  • the UPF can be deployed in various configurations and locations according to the service type.
  • the NRF is a new network entity which can provide registration and discovery functionality so that the NFs can discover each other and implement communications via application programming interfaces (APIs) .
  • APIs application programming interfaces
  • the “service registration” functionality of the NRF can facilitate the negotiation of how and where a service can be utilized by its consumer such as a NF instance or a service instance.
  • a NF instance also may be regarded as a special example of a service instance, and thus the terms “NF instance” and “service instance” may be used interchangeably in some cases.
  • the NRF can support NF/service discovery functionality.
  • the NRF may receive a NF/service discovery request from a requester NF instance, and provide the information of the discovered NF instance (s) to the requester NF instance.
  • the requester NF instance can implement NF selection.
  • the NF selection may consist in selecting a NF instance among the NF instance (s) discovered through the NF/service discovery.
  • the SMF selection may be supported by the AMF.
  • the NRF can maintain NF profiles of available NF instances and their supported services. For example, each NF instance can inform the NRF of a NF profile of this NF instance.
  • the NF profile may comprise a list of services supported by the NF instance, and other NF instance information.
  • the typical information of a NF profile may include but not limit to NF instance identifier (ID) , NF type (e.g. SMF) , public land mobile network (PLMN) ID, NF protocol information and identification/address information (e.g.
  • URI Uniform Resource Identifier
  • URL Uniform Resource Identifier
  • FQDN IP address
  • NF capacity information e.g., a configurable resource plan
  • NF specific service authorization information e.g., a configurable resource plan
  • names of supported services e.g., a configurable resource plan, a configurable resource plan, a configurable resource plan, a configurable resource plan, a configurable resource plan, a configurable resource plan, etc.
  • DNNs data network names
  • APIs access point names
  • NF location load information at the NF and NF service level, other service parameter, etc.
  • the NSSF may support the following functionality:
  • the NSSF performs the steps specified in point (B) in clause 5.15.2.1 of TS 23.501 [2] .
  • the NSSF returns to initial AMF the Allowed NSSAI for the first access type, optionally the Mapping Of Allowed NSSAI, the Allowed NSSAI for the second access type (if any) , optionally the Mapping of Allowed NSSAI and the target AMF Set or, based on configuration, the list of candidate AMF (s) .
  • the NSSF may return NSI ID (s) associated to the Network Slice instance (s) corresponding to certain S-NSSAI (s) .
  • the NSSF may return the NRF (s) to be used to select NFs/services within the selected Network Slice instance (s) . It may return also information regarding rejection causes for S-NSSAI (s) not included in the Allowed NSSAI.
  • the NSSF may return Configured NSSAI for the Serving PLMN, and possibly the associated mapping of the Configured NSSAI. ”
  • the clause 4.2.2.2.33GPP TS23.502 further describes “7 (B) . If the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF via (R) AN, the initial AMF sends a Reroute NAS message to the (R) AN (7a) .
  • the Reroute NAS message includes the information about the target AMF and the Registration Request message carried at step 1. If the initial AMF has obtained the information as described at step 4b, that information is included.
  • the (R) AN sends the Initial UE message to the target AMF (7b) indicating reroute due to slicing including the information from step 4b that the NSSF provided. ”
  • This message is sent by the AMF in order to request for a rerouting of the INITIAL UE MESSAGE to another AMF.
  • This message is sent by the NG-RAN node to transfer the initial layer 3 message to the AMF over the NG interface.
  • the allowed NSSAI may be added for the Reroute NAS Message and the Initial UE Message in the 3GPP TS38.413 for RAN Redirect support for Registration with AMF re-allocation.
  • the information obtained by the Initial AMF from NSSF includes more information elements (IEs) such as [Mapping Of Allowed NSSAI] , [Allowed NSSAI for the second access type] , [Mapping of Allowed NSSAI] , [NSI ID (s) ] , [NRF (s) ] , [List of rejected (S-NSSAI (s) , cause value (s) ) ] , [Configured NSSAI for the Serving PLMN] , [Mapping Of Configured NSSAI] , which are not included in the Reroute NAS Message and the Initial UE Message.
  • IEs information elements
  • At least one of these IEs may also be expected to be given to the target AMF through RAN redirect. And the IEs may change during later 3GPP revisions. So a mechanism may be desirable to transfer at least one of these IEs obtained from the NSSF to the target AMF through RAN redirect.
  • FIG. 3 shows a flowchart of a method 300 according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in at a first network function such as the AMF as shown in FIG. 1 or communicatively coupled to the first network function.
  • the first network function may provide means for accomplishing various parts of the method 300 as well as means for accomplishing other processes in conjunction with other components.
  • the first network function may receive a registration request from an access network node.
  • the registration request may be any suitable registration request for example originating from a UE.
  • the access network node may receive the registration request from the UE, select the first network function and send the registration request to the first network function.
  • the registration request may be similar to the registration request sent in step 3 of Figure 4.2.2.2.2-1 of 3GPP TS23.502 or the registration request included in the Initial UE message sent in step 1 of Figure 4.2.2.2.3-1 of 3GPP TS23.502.
  • the first network function may determine to reroute the registration request to a second network function.
  • the first network function may determine to reroute the registration request to a second network function due to various reasons.
  • the first network function may reroute the registration request to another network function such as AMF, e.g. when the first network function is not the appropriate network function to serve the UE, or when the first network function is overload, or when the first network function is to be shut down for maintenance or power saving, etc.
  • the first network function such as AMF may perform any of steps 2 and 3a-3b-3c of Figure 4.2.2.2.3-1 of 3GPP TS23.502 to decide whether to reroute the registration request.
  • the first network function may obtain information related to network slice selection.
  • the information related to network slice selection may comprise at least one of access and mobility management function (AMF) set or list of AMF addresses; allowed Network Slice Selection Assistance Information (NSSAI) for a first access type; mapping of allowed NSSAI; allowed NSSAI for a second access type; mapping of allowed NSSAI; network slice instance identifier (s) (NSI ID (s) ) ; network function repository function (s) (NRF (s) ) ; list of rejected (Single Network Slice Selection Assistance Information (s) (S-NSSAI (s) ) , cause value (s) ) ; configured NSSAI for the Serving Public land mobile network (PLMN) ; and mapping of configured NSSAI.
  • the information related to network slice selection may further comprise any other information elements related to network slice selection for example from NSSF.
  • the first network function may obtain information related to network slice selection by sending a Nnssf_NSSelection_Get to a Network Slice Selection Function (NSSF) ; and receiving a response to Nnssf_NSSelection_Get from the NSSF, wherein the response to Nnssf_NSSelection_Get comprises the information related to network slice selection.
  • the Nnssf_NSSelection_Get and the response to Nnssf_NSSelection_Get may be similar to the corresponding messages as described in 3GPP TS23.502 or its future version.
  • the information related to network slice selection may comprise the information elements included in the response to Nnssf_NSSelection_Get.
  • the first network function may send a reroute message to the access network node.
  • the reroute message may include a container comprising at least one information element of the information related to network slicing selection.
  • the container may be of any suitable format which can store at least one information element of the information related to network slicing selection.
  • the size of the container may depend on the number of elements it contains.
  • the format of the reroute message may be similar to the REROUTE NAS REQUEST as defined in Clause 9.2.5.5 of 3GPP TS 38.413 except that it further includes the container.
  • This container may be transparent to access network node, i.e., the access network node may forward it to other node without decoding.
  • the reroute message may further comprise information about the second network function and the registration request.
  • the information about the second network function may comprise any suitable information that can be used by the access network device to determine the second network function.
  • the information about the second network function may comprise access and mobility management function (AMF) set and allowed Network Slice Selection Assistance Information (NSSAI) .
  • the information about the second network function may comprise an address of the second network function.
  • FIG. 4 is a flow chart depicting a method 400 according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in at a first network function such as the AMF as shown in FIG. 1 or communicatively coupled to the first network function.
  • the first device may provide means for accomplishing various parts of the method 400 as well as means for accomplishing other processes in conjunction with other components.
  • Blocks 402, 404, 406 and 410 are similar to blocks 302, 304, 306 and 308, detailed description thereof is omitted here for brevity.
  • the first network function may determine the second network function based at least partly on the information related to network slice selection. For example, when the information related to network slice selection comprises a list of the second network function address, the first network function may determine/select the second network function from the list of the second network function address. When the information related to network slice selection comprises the second network function set such as AMF set, the first network function may determine/select the second network function from the second network function set. In addition, when the first network function has locally stored the address of the second network function, it can determine the address of the second network function.
  • the first network function such as initial AMF may send a Nnrf_NFDiscovery_Request to a NRF; receive a response to Nnrf_NFDiscovery_Request from the NRF; and determine the second network function based on at least partly on the response to Nnrf_NFDiscovery_Request.
  • the Nnrf_NFDiscovery_Request and the response to Nnrf_NFDiscovery_Request may be similar to the corresponding messages as described in step 6a and 6b of Figure 4.2.2.2.3-1 of 3GPP TS23.502.
  • the first network function such as AMF may invoke the Nnrf_NFDiscovery_Request service operation from the NRF to find a proper target AMF which has required NF capabilities to serve the UE.
  • the NF type may be set to AMF.
  • the AMF Set is included in the Nnrf_NFDiscovery_Request.
  • the NRF replies with the list of potential target AMF (s) .
  • the NRF may also provide the details of the services offered by the candidate AMF (s) along with the notification end-point for each type of notification service that the selected AMF had registered with the NRF, if available.
  • it provides a list of potential target AMFs and their capabilities, and optionally, additional selection rules. Based on the information about registered NFs and required capabilities, a target AMF is selected by the initial AMF.
  • the first network function and the second network function are AMFs
  • the reroute message is a reroute NAS message
  • the registration request is included within an initial UE message.
  • the reroute NAS message and the initial UE message may be similar to the corresponding message as described in clause 4.2.2.2.3 of 3GPP TS23.502.
  • FIG. 5 shows a flowchart of a method 500 according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in at an access network node such as the (R) AN as shown in FIG. 1 or communicatively coupled to the access network node.
  • the access network node may provide means for accomplishing various parts of the method 500 as well as means for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the access network node may send a first registration request to a first network function.
  • the first registration request may be any suitable registration request for example originating from a UE.
  • the access network node may receive the first registration request from the UE, select the first network function and send the first registration request to the first network function.
  • the first registration request may be similar to the registration request sent in step 3 of Figure 4.2.2.2.2-1 of 3GPP TS23.502 or the registration request included in the Initial UE message sent in step 1 of Figure 4.2.2.2.3-1 of 3GPP TS23.502.
  • the access network node may receive a reroute message from the first network function.
  • the reroute message may include a container comprising at least one information element of information related to network slicing selection.
  • the first network function may be configured to perform the exemplary methods 300 and 400 as illustrated in FIGs. 3 and 4.
  • the access network node may receive the reroute message from the first network function.
  • the reroute message may further comprise information about the second network function and the first registration request.
  • the information about the second network function comprises an address of the second network function.
  • the information about the second network function may comprise AMF set and allowed NSSAI
  • the access network node may determine the second network function based on the AMF set and the allowed NSSAI at block 506 (optional) .
  • the information related to network slice selection may comprise at least one of access and mobility management function (AMF) set or list of AMF addresses; allowed Network Slice Selection Assistance Information (NSSAI) for a first access type; mapping of allowed NSSAI; allowed NSSAI for a second access type; mapping of allowed NSSAI; network slice instance identifier (s) (NSI ID (s) ) ; network function repository function (s) (NRF (s) ) ; list of rejected (Single Network Slice Selection Assistance Information (s) (S-NSSAI (s) ) , cause value (s) ) ; configured NSSAI for the Serving Public land mobile network (PLMN) ; and mapping of configured NSSAI.
  • the information related to network slice selection may further comprise any other information elements related to network slice selection.
  • the access network node may send a second registration request and the container to a second network function.
  • the second network function may be of same type of the first network function.
  • the second registration request may be similar to the registration request included in the Initial UE message sent in step 7b of Figure 4.2.2.2.3-1 of 3GPP TS23.502.
  • the access network node may not process the container but directly forward the container to the second network function.
  • the first network function and the second network function may be AMFs
  • the reroute message may be a reroute NAS message
  • the first registration request may be included within a first initial UE message
  • the second registration request and the container may be included within a second first initial UE message.
  • FIG. 6 shows a flowchart of a method 600 according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in at a second network function such as AMF as shown in FIG. 1 or communicatively coupled to the AMF.
  • the second network function may provide means for accomplishing various parts of the method 600 as well as means for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the second network function may receive from an access network node a registration request and a container comprising at least one information element of information related to network slicing selection.
  • the access network node may be configured to perform the exemplary method 500 as illustrated in FIG. 5.
  • the second network function may receive from an access network node a registration request and a container comprising at least one information element of information related to network slicing selection.
  • the second network function may process the registration request.
  • the second network function such as AMF may process the registration request according to the step 8 of Figure 4.2.2.2.3-1 of 3GPP TS23.502.
  • the information related to network slice selection may comprise at least one of access and mobility management function (AMF) set or list of AMF addresses; allowed Network Slice Selection Assistance Information (NSSAI) for a first access type; mapping of allowed NSSAI; allowed NSSAI for a second access type; mapping of allowed NSSAI; network slice instance identifier (s) (NSI ID (s) ) ; network function repository function (s) (NRF (s) ) ; list of rejected (Single Network Slice Selection Assistance Information (s) (S-NSSAI (s) ) , cause value (s) ) ; configured NSSAI for the Serving Public land mobile network (PLMN) ; and mapping of configured NSSAI.
  • the information related to network slice selection may further comprise any other information elements related to network slice selection.
  • the second network function may be access and mobility management function (AMF) and the registration request and the container may be included within an initial user equipment (UE) message.
  • AMF access and mobility management function
  • UE initial user equipment
  • At least one information element of the information related to network slicing selection can be included in a container and transferred from the first network function such as Initial AMF to a second network function such as target AMF.
  • the container may be added in the Reroute NAS message and the Initial UE message. Therefore the second network function such as the target AMF can get the at least one information element included in the container.
  • This container is transparent to the access network node, i.e., the access network node can forward the container to other node without decoding.
  • FIG. 3-6 may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function (s) .
  • the schematic flow chart diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of specific embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated methods. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.
  • FIG. 7a illustrates a simplified block diagram of an apparatus 710 that may be embodied in/as a first network function according to an embodiment of the present disclosure.
  • FIG. 7b illustrates an apparatus 720 that may be embodied in/as an access network node according to an embodiment of the present disclosure.
  • FIG. 7c illustrates an apparatus 730 that may be embodied in/as a second network function according to an embodiment of the present disclosure
  • the apparatus 710 may comprise at least one processor 711, such as a data processor (DP) and at least one memory (MEM) 712 coupled to the processor 711.
  • the apparatus 710 may further comprise a transmitter TX and receiver RX 713 coupled to the processor 711.
  • the MEM 712 stores a program (PROG) 714.
  • the PROG 714 may include instructions that, when executed on the associated processor 711, enable the apparatus 710 to operate in accordance with the embodiments of the present disclosure, for example to perform any of the methods 300 and 400.
  • a combination of the at least one processor 711 and the at least one MEM 712 may form processing means 715 adapted to implement various embodiments of the present disclosure.
  • the apparatus 720 comprises at least one processor 721, such as a DP, and at least one MEM 722 coupled to the processor 721.
  • the apparatus 720 may further comprise a transmitter TX and receiver RX 723 coupled to the processor 721.
  • the MEM 722 stores a PROG 724.
  • the PROG 724 may include instructions that, when executed on the associated processor 721, enable the apparatus 720 to operate in accordance with the embodiments of the present disclosure, for example to perform the method 500.
  • a combination of the at least one processor 721 and the at least one MEM 722 may form processing means 725 adapted to implement various embodiments of the present disclosure.
  • the apparatus 730 may comprise at least one processor 731, such as a data processor (DP) and at least one memory (MEM) 732 coupled to the processor 731.
  • the apparatus 730 may further comprise a transmitter TX and receiver RX 733 coupled to the processor 731.
  • the MEM 732 stores a program (PROG) 734.
  • the PROG 734 may include instructions that, when executed on the associated processor 731, enable the apparatus 730 to operate in accordance with the embodiments of the present disclosure, for example to the method 600.
  • a combination of the at least one processor 731 and the at least one MEM 732 may form processing means 735 adapted to implement various embodiments of the present disclosure.
  • Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processors 711, 721 and 731, software, firmware, hardware or in a combination thereof.
  • the MEMs 712, 722 and 732 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories, as non-limiting examples.
  • the processors 711, 721 and 731 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors DSPs and processors based on multicore processor architecture, as non-limiting examples.
  • FIG. 8 illustrates a schematic block diagram of an apparatus 800 implemented at a first network function.
  • the apparatus 800 is operable to carry out any of the exemplary methods 300 and 400 and possibly any other processes or methods.
  • the apparatus 800 may comprise: an obtaining unit 802 configured to obtain information related to network slice selection; a sending unit 804 configured to send a reroute message to an access network node, wherein the reroute message including a container comprising at least one information element of the information related to network slicing selection.
  • the apparatus 800 may further comprise a receiving unit (optional) 806 configured to receive a registration request from an access network node; and a first determining unit (optional) 808 configured to determine to reroute the registration request to a second network function.
  • a receiving unit (optional) 806 configured to receive a registration request from an access network node
  • a first determining unit (optional) 808 configured to determine to reroute the registration request to a second network function.
  • the reroute message further comprises information about the second network function and the registration request.
  • the information about the second network function comprises an address of the second network function.
  • the apparatus 800 may further comprise a second determining unit (optional) 810 configured to determine the second network function based at least partly on the information related to network slice selection.
  • the second determining unit (optional) 810 is configured to send a Nnrf_NFDiscovery_Request to a network function repository function (NRF) ; receive a response to Nnrf_NFDiscovery_Request from the NRF; and determine the second network function based on at least partly on the response to Nnrf_NFDiscovery_Request.
  • NRF network function repository function
  • the information about the second network function comprises access and mobility management function (AMF) set and allowed Network Slice Selection Assistance Information (NSSAI) .
  • AMF access and mobility management function
  • NSSAI Network Slice Selection Assistance Information
  • the information related to network slicing selection comprises at least one of access and mobility management function (AMF) set or list of AMF addresses; allowed Network Slice Selection Assistance Information (NSSAI) for a first access type; mapping of allowed NSSAI; allowed NSSAI for a second access type; mapping of allowed NSSAI; network slice instance identifier (s) (NSI ID (s) ) ; network function repository function (s) (NRF (s) ) ; list of rejected (Single Network Slice Selection Assistance Information (s) (S-NSSAI (s) ) , cause value (s) ) ; configured NSSAI for the Serving Public land mobile network (PLMN) ; and mapping of configured NSSAI.
  • AMF access and mobility management function
  • the obtaining unit 802 is configured to send a Nnssf_NSSelection_Get to a Network Slice Selection Function (NSSF) ; and receive a response to Nnssf_NSSelection_Get from the NSSF, wherein the response to Nnssf_NSSelection_Get comprises the information related to network slice selection.
  • NSF Network Slice Selection Function
  • the first network function and the second network function are access and mobility management functions (AMFs)
  • the reroute message is a reroute non-access stratum (NAS) message
  • the registration request is included within an initial user equipment (UE) message.
  • AMFs access and mobility management functions
  • FIG. 9 illustrates a schematic block diagram of an apparatus 900 implemented at an access network node.
  • the apparatus 900 is operable to carry out the exemplary method 500 and possibly any other processes or methods.
  • the apparatus 900 may comprise: a receiving unit 902 configured to receive a reroute message from a first network function, wherein the reroute message including a container comprising at least one information element of information related to network slicing selection; a first sending unit 904 configured to send the second registration request and the container to a second network function.
  • the apparatus 800 may further comprise a second sending unit (optional) 906 configured to send a first registration request to a first network function.
  • a second sending unit (optional) 906 configured to send a first registration request to a first network function.
  • the reroute message further comprises information about the second network function and the first registration request.
  • the information about the second network function comprises an address of the second network function.
  • the information about the second network function comprises access and mobility management function (AMF) set and allowed Network Slice Selection Assistance Information (NSSAI)
  • the apparatus may further comprise a determining unit (optional) 908 configured to determine the second network function based on the AMF set and the allowed NSSAI.
  • AMF access and mobility management function
  • NSSAI Network Slice Selection Assistance Information
  • the information related to network slicing selection comprises at least one of access and mobility management function (AMF) set or list of AMF addresses; allowed Network Slice Selection Assistance Information (NSSAI) for a first access type; mapping of allowed NSSAI; allowed NSSAI for a second access type; mapping of allowed NSSAI; network slice instance identifier (s) (NSI ID (s) ) ; network function repository function (s) (NRF (s) ) ; list of rejected (Single Network Slice Selection Assistance Information (s) (S-NSSAI (s) ) , cause value (s) ) ; configured NSSAI for the Serving Public land mobile network (PLMN) ; and mapping of configured NSSAI.
  • AMF access and mobility management function
  • the first network function and the second network function may be access and mobility management functions (AMFs)
  • the reroute message may be a reroute Non-access stratum (NAS) message
  • the first registration request may be included within a first initial user equipment (UE) message
  • the second registration request and the container may be included within a second first initial user equipment (UE) message.
  • AMFs access and mobility management functions
  • NAS Non-access stratum
  • FIG. 10 illustrates a schematic block diagram of an apparatus 1000 implemented at a second network function.
  • the apparatus 1000 is operable to carry out the exemplary method 600 and possibly any other processes or methods.
  • the apparatus 1000 may comprise: a receiving unit 1002 configured to receive from an access network node a registration request and a container comprising at least one information element of information related to network slicing selection; a processing unit 1004 configured to process the registration request.
  • the second network function may be access and mobility management function (AMF) and the registration request and the container may be included within an initial user equipment (UE) message.
  • AMF access and mobility management function
  • UE initial user equipment
  • some units or modules in the apparatus 800, 900 and 1000 can be combined in some implementations.
  • a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods related to the first network function as described above, such as the methods 300 and 400.
  • a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods related to an access network node as described above, such as the method 500.
  • a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods related to the second network function as described above, such as the method 600.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods related to the first network function as described above, such as the methods 300 and 400.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods related to an access network node as described above, such as the method 500.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods related to the second network function as described above, such as the method 600.
  • the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • the computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory) , a ROM (read only memory) , Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.
  • an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function or means that may be configured to perform two or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses) , firmware (one or more apparatuses) , software (one or more modules) , or combinations thereof.
  • firmware or software implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon certains modes de réalisation, la présente invention concerne des procédés et des appareils de transmission de données. Un procédé mis en oeuvre au niveau d'une première fonction de réseau peut comprendre l'obtention d'informations relatives à la sélection de tranche de réseau ; et l'envoi d'un message de réacheminement à un noeud de réseau d'accès, le message de réacheminement comprenant un contenant comprenant au moins un élément d'informations des informations relatives à la sélection de découpage de réseau.
PCT/CN2019/114750 2018-11-02 2019-10-31 Procédé et appareil de transmission de données WO2020088594A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2018113796 2018-11-02
CNPCT/CN2018/113796 2018-11-02

Publications (1)

Publication Number Publication Date
WO2020088594A1 true WO2020088594A1 (fr) 2020-05-07

Family

ID=70462330

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/114750 WO2020088594A1 (fr) 2018-11-02 2019-10-31 Procédé et appareil de transmission de données

Country Status (1)

Country Link
WO (1) WO2020088594A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113746649A (zh) * 2020-05-14 2021-12-03 华为技术有限公司 一种网络切片控制方法及通信装置
WO2023105420A1 (fr) * 2021-12-07 2023-06-15 Lenovo (Singapore) Pte. Ltd. Communication de messages d'identité entre des dispositifs réseau
WO2023142632A1 (fr) * 2022-01-26 2023-08-03 华为技术有限公司 Procédé de communication et appareil de communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017175715A1 (fr) * 2016-04-05 2017-10-12 シャープ株式会社 Dispositif terminal, dispositif station de base, mme (entité de gestion de mobilité), et procédé de contrôle de communication
WO2017218849A1 (fr) * 2016-06-15 2017-12-21 Convida Wireless, Llc Recherche et sélection de tranches de réseau
US20180316615A1 (en) * 2017-04-27 2018-11-01 At&T Intellectual Property I, L.P. Method and apparatus for selecting processing paths in a converged network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017175715A1 (fr) * 2016-04-05 2017-10-12 シャープ株式会社 Dispositif terminal, dispositif station de base, mme (entité de gestion de mobilité), et procédé de contrôle de communication
WO2017218849A1 (fr) * 2016-06-15 2017-12-21 Convida Wireless, Llc Recherche et sélection de tranches de réseau
US20180316615A1 (en) * 2017-04-27 2018-11-01 At&T Intellectual Property I, L.P. Method and apparatus for selecting processing paths in a converged network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "23.502 – Alignment of slice selection procedures during registration and SMF selection", 3GPP DRAFT; S2-179380, 1 December 2017 (2017-12-01), pages 1 - 4, XP051365889 *
ERICSSON: "NSSF and Slice selection during the Registration procedures", 3GPP DRAFT; S2-174202, 30 June 2017 (2017-06-30), pages 1 - 11, XP051309288 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113746649A (zh) * 2020-05-14 2021-12-03 华为技术有限公司 一种网络切片控制方法及通信装置
CN113746649B (zh) * 2020-05-14 2022-12-06 华为技术有限公司 一种网络切片控制方法及通信装置
WO2023105420A1 (fr) * 2021-12-07 2023-06-15 Lenovo (Singapore) Pte. Ltd. Communication de messages d'identité entre des dispositifs réseau
WO2023142632A1 (fr) * 2022-01-26 2023-08-03 华为技术有限公司 Procédé de communication et appareil de communication

Similar Documents

Publication Publication Date Title
EP3949354B1 (fr) Procédé et appareil pour la découverte de services
WO2021027177A1 (fr) Procédé et appareil pour découverte de services de fonctions réseau
WO2023280121A1 (fr) Procédé et appareil d'obtention de service de périphérie
US11882234B2 (en) Method and apparatus for granting or not granting a chargeable party at a session management with required quality of service utilizing a MAC address
WO2020238411A1 (fr) Procédé et appareil de découverte et de sélection de fonction d'exposition de réseau
WO2020215668A1 (fr) Procédé et appareil pour la découverte de services
US11729599B2 (en) Communication system
WO2020088594A1 (fr) Procédé et appareil de transmission de données
EP3681182A1 (fr) Procédé, appareil et dispositif de détermination d'état de dispositif terminal
US20230007557A1 (en) Method and apparatus for handover
US20230104162A1 (en) Using dnai to identify a smf supporting connection to a local dn
WO2020224411A1 (fr) Procédé et appareil de gestion de session
WO2021180170A1 (fr) Procédé et appareil de transfert intercellulaire
WO2023125805A1 (fr) Procédé et appareil de gestion de session
WO2021218805A1 (fr) Procédé et appareil destinés à un transfert indirect de données
EP3977791A1 (fr) Dispositif et appareil d'enregistrement

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: 19880737

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: 19880737

Country of ref document: EP

Kind code of ref document: A1