WO2024114385A1 - Procédé et appareil de transmission d'informations, dispositif associé et support d'enregistrement - Google Patents

Procédé et appareil de transmission d'informations, dispositif associé et support d'enregistrement Download PDF

Info

Publication number
WO2024114385A1
WO2024114385A1 PCT/CN2023/131806 CN2023131806W WO2024114385A1 WO 2024114385 A1 WO2024114385 A1 WO 2024114385A1 CN 2023131806 W CN2023131806 W CN 2023131806W WO 2024114385 A1 WO2024114385 A1 WO 2024114385A1
Authority
WO
WIPO (PCT)
Prior art keywords
nssai
information
terminal
pdu session
resident gateway
Prior art date
Application number
PCT/CN2023/131806
Other languages
English (en)
Chinese (zh)
Inventor
朱磊
张鸿佳
李文智
何倩
李功
Original Assignee
中移(成都)信息通信科技有限公司
中国移动通信集团有限公司
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 中移(成都)信息通信科技有限公司, 中国移动通信集团有限公司 filed Critical 中移(成都)信息通信科技有限公司
Publication of WO2024114385A1 publication Critical patent/WO2024114385A1/fr

Links

Definitions

  • the present application relates to the field of communications, and in particular to an information transmission method, apparatus, related equipment and storage medium.
  • the fifth generation mobile communication technology uses the characteristics of large bandwidth, low latency, high reliability and wide connection of 5G network to provide necessary network infrastructure support for vertical industry applications, promote the intelligent upgrade of various industries, and move towards the intelligent interconnection of all things.
  • various vertical industries have generally deployed local area networks and the Internet of Things based on network types such as Wi-Fi, Bluetooth, wired, Zigbee, long-range radio (Lora), wireless local area network (WLAN), and high-definition multimedia interface (HDMI). Due to cost, usage habits and other considerations, it is impossible to completely replace other types of networks (i.e.
  • 5G networks and other types of networks will coexist for a long time. If the terminals of the 5G network are in an isolated state from the terminals of other types of networks, the goal of 5G intelligent interconnection of all things will not be achieved, so the integration of 5G networks with other types of networks is imperative.
  • terminals can directly or indirectly access the 5G network based on the connection with the Residential Gateway (RG) (i.e., the connection based on other types of networks).
  • RG Residential Gateway
  • the network side may not be able to meet the business needs of the terminal.
  • the embodiments of the present application provide an information transmission method, apparatus, related equipment and storage medium.
  • the embodiment of the present application provides an information transmission method, which is applied to a first function, including:
  • NSSAI Network Slice Selection Assistance Information
  • the method further comprises:
  • the second NSSAI that the resident gateway is allowed to use is obtained.
  • the first information includes a third NSSAI of the terminal, and the third NSSAI includes the NSSAI requested by the terminal to be used; and the determining the first NSSAI that the terminal is allowed to use includes:
  • the first NSSAI is determined by comparing the fourth NSSAI with the second NSSAI.
  • determining the first NSSAI by comparing the fourth NSSAI with the second NSSAI includes:
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the first condition includes at least one of the following:
  • the S-NSSAI is included in the second NSSAI;
  • the guarantee level of the service level agreement (SLA) corresponding to the S-NSSAI is lower than or equal to the guarantee level of the SLA corresponding to at least one S-NSSAI included in the second NSSAI, and the service corresponding to the S-NSSAI is supported by the at least one S-NSSAI;
  • the obtaining of the second information includes:
  • the second information is obtained from a second function, where the second function is at least used to store an association relationship between the terminal and the resident gateway.
  • the step of obtaining the second NSSAI that the resident gateway is allowed to use includes:
  • the second NSSAI is obtained from the resident gateway.
  • the method further comprises:
  • Receive fourth information sent by the terminal is used to request to create a first protocol data unit (PDU, Protocol Data Unit) session of the terminal, the fourth information includes a first S-NSSAI in the first NSSAI;
  • PDU Protocol Data Unit
  • the fourth information is sent to the third function.
  • the embodiment of the present application further provides an information transmission method, which is applied to the third function, including:
  • the fourth information is used to request to create a first PDU session of the terminal, where the fourth information includes a first S-NSSAI in a first NSSAI that the terminal is allowed to use, where the first NSSAI is associated with a second NSSAI, where the second NSSAI includes an NSSAI that a resident gateway associated with the terminal is allowed to use, where the terminal communicates with a network side through the resident gateway, and where the network side includes the first function;
  • the first PDU session is created, and the second PDU session can carry the service corresponding to the first S-NSSAI.
  • the method further comprises:
  • Second information is obtained, where the second information represents the resident gateway.
  • the method further comprises:
  • Fifth information is sent to the resident gateway, where the fifth information indicates to create the second PDU session.
  • the method further comprises:
  • sixth information sent by the resident gateway where the sixth information is used to request to create the second PDU session, where the sixth information includes a second S-NSSAI, and the second S-NSSAI is associated with the first S-NSSAI;
  • the fifth information includes:
  • the identifier of the terminal is the identifier of the terminal.
  • the fifth information also includes seventh information, and the seventh information indicates that the type of the fifth information is information indicating the creation of a second PDU session that can carry the service corresponding to the first S-NSSAI.
  • the sending of the fifth information to the resident gateway includes:
  • the fifth information is sent to the resident gateway.
  • the method further comprises:
  • the first S-NSSAI set includes S-NSSAIs corresponding to all PDU sessions created by the resident gateway;
  • determining whether the resident gateway has created the second PDU session by comparing the S-NSSAI in the first S-NSSAI set with the first S-NSSAI includes:
  • the resident gateway has created the second PDU session
  • the resident gateway does not create the second PDU session.
  • the second condition includes at least one of the following:
  • the S-NSSAI is the same as the first S-NSSAI;
  • the guarantee level of the SLA corresponding to the S-NSSAI is higher than or equal to the guarantee level of the SLA corresponding to the first S-NSSAI, and the S-NSSAI supports the service corresponding to the first S-NSSAI;
  • the method further comprises:
  • a first rule is sent to the resident gateway, where the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the method further comprises:
  • a second PDU session satisfying a third condition is determined from the at least two second PDU sessions, and the first rule is used to forward the uplink traffic of the terminal to the second PDU session satisfying the third condition.
  • the method further comprises:
  • eighth information is sent to the terminal, where the eighth information indicates that the capability of the resident gateway does not match the first S-NSSAI and instructs to terminate the creation process of the first PDU session.
  • the method further comprises:
  • the obtaining of the second information includes:
  • the second information is obtained from a second function, where the second function is at least used to store an association relationship between the terminal and the resident gateway.
  • the embodiment of the present application also provides an information transmission method, which is applied to a resident gateway, comprising:
  • a second NSSAI is sent to the first function to determine a first NSSAI that a terminal associated with the resident gateway is allowed to use, the terminal communicates with a network side through the resident gateway, the network side includes the first function, the second NSSAI includes the NSSAI that the resident gateway is allowed to use, and the second NSSAI is associated with the first NSSAI.
  • the method further comprises:
  • the fifth information indicates the creation of a second PDU session, where the second PDU session can carry the service corresponding to the first S-NSSAI, and where the first S-NSSAI is associated with the first PDU session of the terminal.
  • the fifth information includes:
  • the identifier of the terminal is the identifier of the terminal.
  • the fifth information also includes seventh information, and the seventh information indicates that the type of the fifth information is information indicating the creation of a second PDU session that can carry the service corresponding to the first S-NSSAI.
  • the method further comprises:
  • sixth information is sent to the third function, where the sixth information is used to request the creation of the second PDU session, and the sixth information includes a second S-NSSAI, where the second S-NSSAI is associated with the first S-NSSAI.
  • the method further comprises:
  • An S-NSSAI in the second NSSAI that satisfies a second condition is determined as the second S-NSSAI.
  • the method further comprises:
  • the first S-NSSAI set includes S-NSSAIs corresponding to all PDU sessions created by the resident gateway;
  • determining whether the resident gateway has created the second PDU session by comparing the S-NSSAI in the first S-NSSAI set with the first S-NSSAI includes:
  • the resident gateway has created the second PDU session
  • the resident gateway does not create the second PDU session.
  • the second condition includes at least one of the following:
  • the S-NSSAI is the same as the first S-NSSAI;
  • the guarantee level of the SLA corresponding to the S-NSSAI is higher than or equal to the guarantee level of the SLA corresponding to the first S-NSSAI, and the S-NSSAI supports the service corresponding to the first S-NSSAI;
  • the method further comprises:
  • a first rule is configured locally, where the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the method further comprises:
  • the first rule is used to forward the uplink traffic of the terminal to a second PDU session among the at least two second PDU sessions that meets the third condition.
  • the method further comprises:
  • ninth information is sent to the third function, where the ninth information indicates that the creation of the second PDU session fails.
  • the embodiment of the present application further provides an information transmission device, which is arranged on a first function and includes:
  • a first receiving unit is configured to receive first information sent by a terminal, where the first information is used to request registration related to a network slice;
  • a first processing unit is configured to determine a first NSSAI that the terminal is allowed to use, wherein the first NSSAI is associated with a second NSSAI; the second NSSAI includes an NSSAI that a resident gateway associated with the terminal is allowed to use, the terminal communicates with a network side through the resident gateway, and the network side includes a first function;
  • the first sending unit is configured to send third information to the terminal, where the third information includes the first NSSAI.
  • the embodiment of the present application further provides an information transmission device, which is set on the third function, including:
  • a second receiving unit configured to receive fourth information sent by the first function, the fourth information being used to request to create a first PDU session of the terminal, the fourth information comprising a first S-NSSAI in a first NSSAI that the terminal is allowed to use, the first NSSAI being associated with a second NSSAI, the second NSSAI comprising an NSSAI that a resident gateway associated with the terminal is allowed to use, the terminal communicating with a network side through the resident gateway, and the network side comprising the first function;
  • the second processing unit is configured to create the first PDU session when the second PDU session of the resident gateway is successfully created, and the second PDU session can carry the service corresponding to the first S-NSSAI.
  • the embodiment of the present application further provides an information transmission device, which is arranged on a resident gateway and includes:
  • the third sending unit is configured to send a second NSSAI to the first function to determine the first NSSAI that the terminal associated with the resident gateway is allowed to use, the terminal communicates with the network side through the resident gateway, the network side includes the first function, the second NSSAI includes the NSSAI that the resident gateway is allowed to use, and the second NSSAI is associated with the first NSSAI.
  • the embodiment of the present application also provides a first function, including:
  • a first communication interface is configured to receive first information sent by a terminal, where the first information is used to request registration related to a network slice;
  • a first processor configured to determine a first NSSAI that the terminal is allowed to use, and to send third information to the terminal through the first communication interface, wherein the third information includes the first NSSAI, the first NSSAI is associated with a second NSSAI, the second NSSAI includes an NSSAI that a resident gateway associated with the terminal is allowed to use, and the terminal communicates with the resident gateway through the resident gateway Network side communication, the network side includes the first function.
  • the embodiment of the present application also provides a third function, including:
  • a second communication interface configured to receive fourth information sent by the first function, the fourth information being used to request creation of a first PDU session of the terminal, the fourth information comprising a first S-NSSAI in a first NSSAI that the terminal is allowed to use, the first NSSAI being associated with a second NSSAI, the second NSSAI comprising an NSSAI that a resident gateway associated with the terminal is allowed to use, the terminal communicating with the network side through the resident gateway, and the network side comprising the first function;
  • the second processor is configured to create the first PDU session when the second PDU session of the resident gateway is successfully created, and the second PDU session can carry the service corresponding to the first S-NSSAI.
  • the embodiment of the present application further provides a resident gateway, comprising: a third communication interface and a third processor; wherein:
  • the third communication interface is configured to send a second NSSAI to the first function to determine a first NSSAI that the terminal associated with the resident gateway is allowed to use, the terminal communicates with a network side through the resident gateway, the network side includes the first function, the second NSSAI includes the NSSAI that the resident gateway is allowed to use, and the second NSSAI is associated with the first NSSAI.
  • the embodiment of the present application further provides a first function, including: a first processor and a first memory configured to store a computer program that can be run on the processor,
  • the first processor is configured to execute the steps of any one of the above-mentioned methods on the first functional side when running the computer program.
  • the embodiment of the present application further provides a third function, including: a second processor and a second memory configured to store a computer program that can be run on the processor,
  • the second processor is configured to execute the steps of any method of the third functional side when running the computer program.
  • the embodiment of the present application further provides a resident gateway, comprising: a third processor and a third memory configured to store a computer program that can be run on the processor,
  • the third processor is configured to execute the steps of any one of the above-mentioned methods for resident on the gateway side when running the computer program.
  • An embodiment of the present application also provides a storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements the steps of any method on the first function side, or implements the steps of any method on the third function side, or implements the steps of any method on the resident gateway side.
  • the information transmission method, apparatus, related equipment and storage medium provided in the embodiments of the present application have a first function of receiving first information sent by a terminal, where the first information is used to request registration related to a network slice; determining a first NSSAI that the terminal is allowed to use, and sending third information to the terminal, where the third information includes the first NSSAI, the first NSSAI is associated with a second NSSAI, and the second NSSAI includes an NSSAI that a resident gateway associated with the terminal is allowed to use,
  • the terminal communicates with the network side through the resident gateway, and the network side includes the first function.
  • the network function determines the resident gateway associated with the terminal, i.e., determines the resident gateway to which the terminal is connected, and determines the NSSAI that the terminal is allowed to use based on the NSSAI that the resident gateway to which the terminal is connected is allowed to use, thereby enabling the collaboration between the terminal and the resident gateway on the network slice that is allowed to be used, and then subsequently enabling the collaboration between the terminal and the resident gateway when accessing the network slice; in other words, the network slice accessed by the resident gateway can meet the service requirements corresponding to the network slice that the terminal needs to access, i.e., the performance of the channel between the resident gateway and the network side can meet the service requirements of the terminal, thereby ensuring the normal operation of the terminal's services.
  • FIG1 is a schematic diagram of a fusion architecture of a 5G network and other types of networks in the related art
  • FIG2 is a schematic diagram of another fusion architecture of a 5G network and other types of networks in the related art
  • FIG3 is a schematic diagram of a third 5G network and other types of network integration architecture in the related art
  • FIG4 is a schematic diagram of a registration process related to network slicing in the related art
  • FIG5 is a schematic diagram of a session establishment process related to network slicing in the related art
  • FIG6 is a schematic diagram of a registration process for independent network slices between a 5G terminal and a 5G resident gateway in the related art
  • FIG7 is a schematic diagram of a process for establishing independent network slice-related sessions between a 5G terminal and a 5G resident gateway in the related art
  • FIG8 is a schematic diagram of a flow chart of an information transmission method according to an embodiment of the present application.
  • FIG9 is a flow chart of another information transmission method according to an embodiment of the present application.
  • FIG10 is a schematic diagram of a flow chart of a third information transmission method according to an embodiment of the present application.
  • FIG11 is a schematic diagram of a network slicing registration process for a 5G resident gateway connected to a 5G terminal in an application example of this application;
  • FIG12 is a schematic diagram of a process for establishing a network slice-related session for a 5G resident gateway connected to a 5G terminal in an application example of the present application;
  • FIG13 is a schematic diagram of the structure of an information transmission device according to an embodiment of the present application.
  • FIG14 is a schematic diagram of the structure of another information transmission device according to an embodiment of the present application.
  • FIG15 is a schematic diagram of the structure of a third information transmission device according to an embodiment of the present application.
  • FIG16 is a schematic diagram of a first functional structure of an embodiment of the present application.
  • FIG17 is a schematic diagram of a third functional structure of an embodiment of the present application.
  • FIG18 is a schematic diagram of the structure of a resident gateway according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of the structure of the information transmission system according to an embodiment of the present application.
  • 5G capability means at least being able to support the 5G non-access layer (NAS) process specified in the relevant technology.
  • NAS non-access layer
  • a user equipment (UE, User Equipment) that can at least support the 5G NAS process specified in the relevant technology is a UE with 5G capability, which can be called a 5G UE;
  • a resident gateway that can at least support the 5G NAS process specified in the relevant technology is a resident gateway with 5G capability, which can be called a 5G resident gateway (5G Residential Gateway in English, 5G-RG for short).
  • Architecture 1 architecture integrating 3GPP network and non-3GPP network
  • 5G fixed-mobile converged architecture between fixed and mobile networks can be understood as a wireless and wired converged architecture
  • the 5G resident gateway connects to the 5G UE through the trusted non-3GPP gateway function (TNGF, Trusted Non-3GPP Gateway Function) or non-3GPP network interaction function (N3IWF, Non-3GPP InterWorking Function) to access the 5G core network (5G Core Network in English, abbreviated as 5GC).
  • TNGF Trusted Non-3GPP Gateway Function
  • N3IWF Non-3GPP InterWorking Function
  • non-3GPP networks such as Wi-Fi, Bluetooth, wired, Zigbee, Lora, WLAN, HDMI, etc. can access the 5G core network based on multiple network elements such as N3IWF and TNGF.
  • untrusted non-3GPP networks such as public Wi-Fi, etc.
  • 5G UE can directly access the 5G core network through non-3GPP networks, that is, it can use 5G N1 interface and 5G NAS signaling to realize 5G network communication.
  • 5G fixed-mobile convergence is specifically implemented based on two types of gateways. One is a resident gateway deployed on the user side to solve the convergence problem on the user side; the other is a wireline access gateway function (W-AGF, Wireline Access Gateway Function) deployed on the network side to solve the convergence problem on the network side.
  • W-AGF Wireline Access Gateway Function
  • the resident gateway is specifically deployed between the UE and the access network, and can include a 5G resident gateway and a fixed network resident gateway (which can be expressed in English as Fixed Network Residential Gateway, abbreviated as FN-RG).
  • the 5G resident gateway can be connected to the 5G radio access network (RAN, Radio Access Network) or the wired access network; while the fixed network resident gateway can only be connected to the wired access network.
  • W-AGF is deployed between the wired access network and the 5G core network, and can form a wired 5G access network (W-5GAN) together with the wired access network.
  • the W-5GAN and the 5G core network can be connected through the 5G N2 and N3 interfaces.
  • W-AGF is the basis for realizing 5G fixed-mobile convergence.
  • the 5G fixed-mobile convergence network architecture based on 5G resident gateway and W-AGF is shown in Figure 2. Based on this architecture, the UE can first access the 5G resident gateway through the non-3GPP network, and then indirectly access the 5G core network through the 5G resident gateway.
  • the UE under the resident gateway may also have 5G capabilities, but based on the above architecture 2, the UE can only indirectly access the 5G core network through the resident gateway, and cannot use the 5G N1 interface and 5G NAS signaling to achieve 5G network communication.
  • the above architecture 1 and architecture 2 can be integrated to obtain architecture 3, that is, combining the fusion architecture of 3GPP network and non-3GPP network, the 5G fixed-mobile convergence architecture as a whole is regarded as a "non-trusted non-3GPP access” or “trusted non-3GPP access”, and accesses the 5G core network through N3IWF or TNGF; among them, the network architecture of the 5G UE connected to the 5G resident gateway accessing the 5G core network through TNGF is shown in Figure 3.
  • the 5G UE connected to the resident gateway can directly access the 5G core network based on the connection with the resident gateway, that is, it can use the 5G N1 interface and 5G NAS signaling to achieve 5G network communication, and can transparently transmit the N1 interface NAS signaling and PDU session traffic between the 5G UE and the 5G core network in the Trusted Non-3GPP Access Network (TNAN).
  • TNAN Trusted Non-3GPP Access Network
  • the terminal when the terminal initiates the registration process related to network slicing to the network side, it can provide the network side with the network slice information it wants to access, and the network side can decide the network slice that the user is finally allowed to access based on the contract, configuration and other information.
  • the registration process related to network slicing may include the following steps:
  • Step 401 The UE sends a registration request message to the RAN, and then executes step 402;
  • Step 402 RAN sends a registration request message of the UE to the core network, and then executes step 403;
  • Step 403 The core network performs authorization authentication of slice-related parameters on the UE and generates an allowed NSSAI (i.e., Allowed NSSAI), and then executes step 404;
  • an allowed NSSAI i.e., Allowed NSSAI
  • Step 404 The core network returns a registration acceptance message to the UE via the RAN.
  • the registration request message sent by the UE may include slice-related parameters, and the slice-related parameters may include the NSSAI requested by the UE (i.e., Requested NSSAI).
  • the RAN may select an appropriate access and mobility management function (AMF) for the UE based on the radio access technology (RAT) and the requested NSSAI, and forward the registration request message to the selected AMF. If the RAN cannot select an appropriate AMF, the registration request message may be forwarded to the locally configured AMF.
  • AMF access and mobility management function
  • the AMF may verify the Requested NSSAI in the registration request message based on the contract information such as the NSSAI contracted by the UE obtained from the Unified Data Management (UDM), and some slice-related information interacted with the Network Slice Selection Function (NSSF) or stored locally, to generate the Allowed NSSAI.
  • the verification of the Requested NSSAI in the registration request message can be understood as the authorization and authentication of the S-NSSAI in the Requested NSSAI, and the S-NSSAI that has passed the authentication is selected into the Allowed NSSAI of the UE.
  • the AMF may return the Allowed NSSAI, Parameters such as configured NSSAI, rejected NSSAI, and pending NSSAI.
  • NSSAI can be understood as a combination or collection of S-NSSAI, and one NSSAI can be associated with eight S-NSSAI.
  • S-NSSAI can identify a specific network slice and is not repeated in the public land mobile network (PLMN);
  • S-NSSAI can contain Slice/Service Type (SST) and Slice Differentiator (SD).
  • SST can characterize the expected network slice behavior in terms of features and services.
  • SD can be understood as a supplement to the slice type and can be used to further distinguish multiple network slices of the same SST.
  • NSSAI can include Configured NSSAI, Requested NSSAI, Allowed NSSAI, Rejected NSSAI, and Pending NSSAI.
  • Configured NSSAI can be configured by the currently serving PLMN.
  • Each PLMN can be configured with a Configured NSSAI, which indicates the network slicing capability planned and deployed by this PLMN network; Requested NSSAI indicates the slice logical network that the terminal requests to access; Allowed NSSAI indicates the NSSAI that the terminal is allowed to use; Rejected NSSAI indicates a set of S-NSSAIs that are denied access when the UE registration is successful but some slices deny access; Pending NSSAI can be provided by the currently serving PLMN and can indicate a set of S-NSSAIs that are pending in the network slice-specific authentication and authorization process.
  • Configured NSSAI indicates the network slicing capability planned and deployed by this PLMN network
  • Requested NSSAI indicates the slice logical network that the terminal requests to access
  • Allowed NSSAI indicates the NSSAI that the terminal is allowed to use
  • Rejected NSSAI indicates a set of S-NSSAIs that are denied access when the UE registration is successful but some slices deny access
  • the network side when establishing a PDU session related to a network slice, the network side can select a network element in the slice to serve the terminal according to the network slice information requested by the terminal.
  • the process of establishing a PDU session related to a network slice may include the following steps:
  • Step 501 The UE sends a PDU session establishment request message carrying S-NSSAI to the core network through the RAN, and then executes step 502;
  • Step 502 The core network selects a session management function (SMF) and establishes a related session, and then executes step 503;
  • SMF session management function
  • Step 503 The core network sends a session establishment request and a PDU session establishment acceptance message to the RAN, and then executes step 504;
  • Step 504 RAN performs radio resource preparation and sends a PDU session establishment accept message to the UE.
  • the UE may send a PDU session establishment request message to the AMF, which may carry the S-NSSAI selected by the UE from the Allowed NSSAI.
  • the AMF may determine the SMF to be selected based on the S-NSSAI carried in the PDU session establishment request message.
  • the SMF can send an N2PDU session establishment message (i.e., a session establishment request) to the RAN through the AMF, and send a PDU session establishment acceptance message to the terminal through the RAN.
  • N2PDU session establishment message i.e., a session establishment request
  • 5G UE can access the 5G network based on the above architecture 2, but under this architecture, the UE indirectly accesses the 5G network through the 5G resident gateway, and does not support the 5G N1 interface and 5G NAS signaling between the UE and the 5G core network, so that the UE cannot conveniently use 5G advanced technologies, such as network slicing, UE route selection policy (URSP, UE Route Selection Policy), etc.
  • 5G advanced technologies such as network slicing, UE route selection policy (URSP, UE Route Selection Policy), etc.
  • the above architecture 3 can solve this problem, that is, the UE can first access the non-3GPP network, and then access the 5G core network through N3IWF or TNGF to achieve direct communication with the 5G network. For areas with good 5G coverage, while the UE accesses the 5G core network through the 5G RAN, it can also access the 5G core network through the non-3GPP network based on the above architecture 3, thereby realizing dual-path transmission, and then meeting some high-reliability application scenarios, such as hospital remote surgery scenarios.
  • the direct access of 5G UE to the 5G core network based on the above-mentioned architecture 3 has very broad application prospects for consumers (2C) and enterprises (2B).
  • the above-mentioned architecture 3 still has the following problems:
  • the 5G UE and the 5G core network directly interact with the 5G NAS signaling through the 5G N1 interface, and the 5G resident gateway transparently transmits the NAS signaling between the 5G UE and the 5G core network.
  • the 5G UE and the 5G resident gateway are two independent UEs, and the 5G network also independently processes the access management, session management, user plane management and other related policies and processes for the two.
  • network slices refer to the network slice-related registration process of the 5G UE shown in Figure 6a, the network slice-related registration process of the 5G resident gateway shown in Figure 6b, the network slice-related PDU session creation process of the 5G UE shown in Figure 7a, and the network slice-related PDU session creation process of the 5G resident gateway shown in Figure 7b.
  • the 5G UE and the 5G resident gateway each initiate independent network slice-related registration processes and PDU session creation processes.
  • 5G UE physically (i.e., actually) accesses the 5G core network through the 5G resident gateway, that is, all data packets of the 5G UE need to pass through the 5G resident gateway.
  • the premise for 5G UE to achieve normal 5G communication is that the 5G resident gateway supports and establishes the data channel required by the 5G UE, such as the PDU session established by the 5G resident gateway in Figure 3.
  • the 5G resident gateway needs to support and access the network slice, or the network slice that the 5G resident gateway has accessed can map or support the slice required by the UE (for example, the SLA quality level of the slice currently accessed by the 5G resident gateway is higher than the slice required by the UE).
  • 5G UE Since the relevant technology cannot achieve the collaboration between 5G UE and 5G resident gateway when accessing network slices, 5G UE regards the path between "5G resident gateway ⁇ -> TNGF/N3IWF" as a transparent control plane and user plane channel, and does not perform corresponding processing on this channel in the registration process and PDU session creation process related to network slicing. Therefore, the performance of this channel (such as bandwidth, rate, latency, reliability, etc.) may not meet the SLA quality of the network slice expected by the 5G UE, which may cause the 5G UE's services to fail to operate normally.
  • 5G UE Since the relevant technology cannot achieve the collaboration between 5G UE and 5G resident gateway when accessing network slices, 5G UE regards the path between "5G resident gateway ⁇ -> TNGF/N3IWF" as a transparent control plane and user plane channel, and does not perform corresponding processing on this channel in the registration process and PDU session creation process related to network slicing. Therefore, the performance of this channel (
  • the network side since the network side cannot achieve coordination between 5G UE and 5G resident gateway when accessing network slices, the network side may not be able to meet the business needs of the terminal.
  • the network function Determine the resident gateway associated with the terminal, that is, determine the resident gateway connected to the terminal, and determine the NSSAI that the terminal is allowed to use based on the NSSAI that the resident gateway connected to the terminal is allowed to use, so that the terminal and the resident gateway can collaborate on the network slices that are allowed to be used, and then subsequently the terminal and the resident gateway can collaborate when accessing the network slice; in other words, the network slice accessed by the resident gateway can meet the service requirements corresponding to the network slice that the terminal needs to access, that is, the performance of the channel between the resident gateway and the network side can meet the service requirements of the terminal, so as to ensure the normal operation of the terminal's business.
  • the terminal and the resident gateway can collaborate when accessing the network slice, it is possible to flexibly use 5G network slicing technology through non-3GPP access in the fixed-mobile convergence scenario (i.e., the above-mentioned architecture 2), thereby promoting a deeper integration of 5G and wired networks.
  • the embodiment of the present application provides an information transmission method, which is applied to the first function. As shown in FIG8 , the method includes:
  • Step 801 Receive first information sent by a terminal, where the first information is used to request registration related to a network slice;
  • Step 802 Determine a first NSSAI that the terminal is allowed to use, and send third information to the terminal, where the third information includes the first NSSAI, the first NSSAI is associated with a second NSSAI, the second NSSAI includes the NSSAI that a resident gateway associated with the terminal is allowed to use, the terminal communicates with a network side through the resident gateway, and the network side includes the first function.
  • the network side includes the first function, which can be understood as the first function can communicate with the terminal through the resident gateway, that is, the first function can receive the first information sent by the terminal through the resident gateway, and can send the third information to the terminal through the resident gateway.
  • the first function can be understood as the first function can communicate with the terminal through the resident gateway, that is, the first function can receive the first information sent by the terminal through the resident gateway, and can send the third information to the terminal through the resident gateway.
  • the terminal may also be referred to as a UE or a user.
  • the terminal may include a 5G terminal, that is, a terminal with 5G capabilities
  • the resident gateway may include a 5G resident gateway, that is, a resident gateway with 5G capabilities.
  • the resident gateway associated with the terminal can be understood as the resident gateway to which the terminal is connected; in other words, when the terminal communicates with the network side through the resident gateway, there is an association relationship between the terminal and the resident gateway, or it can be understood that there is a mapping relationship between the terminal and the resident gateway.
  • the terminal communicates with the network side through the resident gateway, which means that the terminal can directly or indirectly access the 5G core network based on the connection with the resident gateway.
  • connections to other types of networks besides the 5G network can be established between the terminal and the resident gateway, such as Wi-Fi, Bluetooth, wired, Zigbee, Lora, WLAN, HDMI and other non-3GPP network connections.
  • the terminal can indirectly access the 5G core network using the above-mentioned architecture 2, or directly access the 5G core network using the above-mentioned architecture 3; at the same time, the terminal can also directly access the 5G core network through RAN to achieve dual-path transmission, such as directly through Access to the 5G core network through a 5G base station.
  • the resident gateway can be connected to the 5G network through a wired network, or can be connected to the 5G network wirelessly.
  • the specific connection method between the terminal and the resident gateway and the specific method of the terminal and/or the resident gateway accessing the 5G network can be determined according to demand, and the embodiment of the present application does not limit this.
  • the first function needs to determine the resident gateway associated with the terminal, and determine the second NSSAI that the resident gateway is allowed to use.
  • the method may further include:
  • the second NSSAI that the resident gateway is allowed to use is obtained.
  • the terminal or resident gateway can report the association relationship between the terminal and the resident gateway to the network side after establishing the connection, and the association relationship can be saved by the second function.
  • other network functions such as the first function
  • the specific method in which the terminal or resident gateway reports the association relationship between the terminal and the resident gateway to the network side can be determined according to needs, such as based on the network capability exposure function (NEF, Network Exposure Function) or the reporting method of the wired network or RAN, etc., and the embodiments of the present application do not limit this.
  • NEF Network Exposure Function
  • obtaining the second information may include:
  • the second information is obtained from a second function, where the second function is at least used to store an association relationship between the terminal and the resident gateway.
  • the second information may at least include the identification of the resident gateway and other contents.
  • the embodiment of the present application does not limit the specific content of the second information, as long as its function is realized.
  • the specific implementation method of the identification of the resident gateway can also be determined according to the needs, such as mobile station international integrated services digital network number (MSISDN, Mobile Station international ISDN number), international mobile subscriber identity code (IMSI, International Mobile Subscriber Identity), user permanent identifier (SUPI, SUbscription Permanent Identifier), user hidden identifier (SUCI, SUbscription Concealed Identifier), Internet Protocol (IP, Internet Protocol) address, media access control (MAC, Media Access Control) address, permanent equipment identifier (PEI, Permanent Equipment Identifier), etc.
  • MSISDN Mobile Station international ISDN number
  • IMSI international mobile subscriber identity code
  • SUPI user permanent identifier
  • SUbscription Permanent Identifier user hidden identifier
  • IP Internet Protocol
  • MAC media access control
  • PEI Permanent Equipment Identifier
  • the specific method for the first function to obtain the second information from the second function can be determined according to the needs, and the embodiment of the present application does not limit this.
  • the first function can send a query message to the second function for querying the resident gateway associated with the terminal and at least including the identifier of the terminal.
  • the second function can determine the second information according to the identifier of the terminal and send the second information to the first function.
  • the identifier of the terminal can also be implemented by MSISDN, IMSI, SUPI, SUCI, IP address, MAC address, PEI, etc., and the specific implementation method of the identifier is not limited in the embodiment of the present application.
  • the second NSSAI can be understood as the Allowed NSSAI of the resident gateway, and the resident gateway can obtain the second NSSAI through the network slice-related registration process of the resident gateway shown in Figure 6b.
  • the AMF can verify the Requested NSSAI in the registration request message of the resident gateway based on the contract information such as the NSSAI signed by the resident gateway obtained from the UDM, as well as some slice-related information interacted with the NSSF or stored locally, to generate the Allowed NSSAI of the resident gateway (that is, determine the second NSSAI), and send the second NSSAI to the resident gateway through a registration acceptance message.
  • the verification of the Requested NSSAI in the registration request message of the resident gateway can be understood as the authorization and authentication of the S-NSSAI in the Requested NSSAI of the resident gateway, and the S-NSSAI that has passed the authentication is selected into the Allowed NSSAI of the resident gateway.
  • obtaining the second NSSAI that the resident gateway is allowed to use may include:
  • the second NSSAI is obtained from the resident gateway.
  • the first information may also be called a registration request, a registration request message, etc.
  • the embodiment of the present application does not limit the name of the first information as long as its function is realized.
  • the first function may include AMF
  • the first information may include the third NSSAI requested by the terminal (which can be understood as the Requested NSSAI of the terminal).
  • the AMF may first perform the above step 403 to generate the fourth NSSAI allowed to be used by the terminal (which can be understood as the NSSAI originally allowed by the terminal, that is, the original Allowed NSSAI), and then generate a new Allowed NSSAI (that is, the first NSSAI) for the terminal based on the fourth NSSAI and the second NSSAI.
  • the association of the first NSSAI with the second NSSAI means that the first NSSAI is generated at least based on the second NSSAI.
  • the first NSSAI can be determined based on the second NSSAI and the fourth NSSAI; or it can be understood that the first NSSAI can include the S-NSSAI in the second NSSAI, the S-NSSAI in the first NSSAI can be mapped to the S-NSSAI in the second NSSAI, etc.
  • determining the first NSSAI that the terminal is allowed to use may include:
  • the first NSSAI is determined by comparing the fourth NSSAI with the second NSSAI.
  • the fourth NSSAI is associated with the third NSSAI, which means that the fourth NSSAI is generated at least according to the third NSSAI, that is, the fourth NSSAI may include the S-NSSAI in the third NSSAI, or the fourth NSSAI may be understood as a subset of the third NSSAI.
  • the process of determining the fourth NSSAI may be specifically referred to in step 403 and related descriptions. I have understood it, so I will not elaborate on it here.
  • the comparison of the fourth NSSAI with the second NSSAI can be understood as comparing the S-NSSAI in the fourth NSSAI with the S-NSSAI in the second NSSAI, so as to screen out one or more S-NSSAIs that can match the capabilities of the resident gateway from the fourth NSSAI; wherein, the S-NSSAI that can match the capabilities of the resident gateway means that after the terminal accesses the network slice corresponding to the S-NSSAI, the network slice accessed by the resident gateway can meet the business requirements corresponding to the network slice, that is, the S-NSSAI that can make the performance of the channel between the resident gateway and the network side meet the business requirements of the terminal.
  • the S-NSSAI filtered out from the fourth NSSAI may meet at least one of the following three conditions to ensure that the network slice accessed by the resident gateway can meet the service requirements corresponding to the network slice that the terminal needs to access: Condition 1, the second NSSAI contains the S-NSSAI; Condition 2, the SLA guarantee level of one or more S-NSSAI in the second NSSAI is not lower than that of the S-NSSAI, that is, the one or more S-NSSAI can support the service of the S-NSSAI; Condition 3, one or more S-NSSAI in the second NSSAI can be mapped to the S-NSSAI.
  • determining the first NSSAI by comparing the fourth NSSAI with the second NSSAI may include:
  • the first function may determine the entire set or a subset of the set of S-NSSAIs in the fourth NSSAI that meet the first condition as the first NSSAI; in other words, the first NSSAI may include the entire set of S-NSSAIs in the fourth NSSAI that meet the first condition, or the first NSSAI may include a subset of the set of S-NSSAIs in the fourth NSSAI that meet the first condition.
  • the first function may determine a subset of the set as the first NSSAI according to the service requirements of the terminal (such as service type, etc.).
  • the first condition is associated with the second NSSAI, which can be understood as the first condition being determined at least according to the second NSSAI, or the first condition including the second NSSAI.
  • the first condition needs to enable the S-NSSAI that meets the first condition to match the capabilities of the resident gateway, so that the network slice accessed by the resident gateway can meet the service requirements corresponding to the network slice that the terminal needs to access.
  • the first condition may include at least one of the above-mentioned conditions 1, 2, and 3.
  • the first condition may include at least one of the following:
  • the S-NSSAI is included in the second NSSAI;
  • the guarantee level of the SLA corresponding to the S-NSSAI is lower than or equal to the guarantee level of the SLA corresponding to at least one S-NSSAI included in the second NSSAI, and the service corresponding to the S-NSSAI is supported by the at least one S-NSSAI;
  • the first function can determine that the capabilities of the resident gateway do not match the business needs of the terminal, or it can be understood that the capabilities of the resident gateway cannot meet the business needs of the terminal.
  • the first function can return registration failure information to the terminal, which can carry the reason for the registration failure (that is, the capabilities of the resident gateway currently accessed by the terminal cannot meet the business needs of the terminal).
  • the terminal can re-access other resident gateways except the currently accessed resident gateway, and re-initiate the registration process related to the network slice.
  • the third information may also include one or more of the contents of Configured NSSAI, Rejected NSSAI, Pending NSSAI, etc.
  • the specific content of the third information may be determined according to the needs, and the embodiment of the present application does not limit this.
  • Rejected NSSAI may include all S-NSSAI in the third NSSAI that are not selected into the first NSSAI.
  • the method may further include:
  • the fourth information is used to request to establish a first PDU session of the terminal, and the fourth information includes a first S-NSSAI in the first NSSAI;
  • the fourth information is sent to the third function.
  • the third function may include SMF
  • the first function may receive the fourth information through the resident gateway and forward the fourth information to the SMF, and then the SMF realizes the collaboration between the terminal and the resident gateway when accessing the network slice.
  • the embodiment of the present application further provides an information transmission method, which is applied to the third function.
  • the method includes:
  • Step 901 receiving fourth information sent by a first function, the fourth information being used to request creation of a first PDU session of a terminal, the fourth information comprising a first S-NSSAI in a first NSSAI that the terminal is allowed to use, the first NSSAI being associated with a second NSSAI, the second NSSAI comprising an NSSAI that a resident gateway associated with the terminal is allowed to use, the terminal communicating with a network side through the resident gateway, and the network side comprising the first function;
  • Step 902 When the second PDU session of the resident gateway is successfully created, the first PDU session is created, and the second PDU session can carry the service corresponding to the first S-NSSAI.
  • the second PDU session can carry the service corresponding to the first S-NSSAI, that is, the second PDU session can carry the service corresponding to the first PDU session, therefore, the first PDU session is created again when the second PDU session is successfully created, so that the performance of the channel between the resident gateway and the network side can meet the service of the terminal. requirements, thereby ensuring the normal operation of terminal services.
  • the creation of the first PDU session/the second PDU session may also be referred to as establishing the first PDU session/the second PDU session.
  • the third function needs to determine the resident gateway associated with the terminal.
  • the method may further include:
  • Second information is obtained, where the second information represents the resident gateway.
  • obtaining the second information may include:
  • the second information is obtained from a second function, where the second function is at least used to store an association relationship between the terminal and the resident gateway.
  • the third function can send a query message to the second function for querying the resident gateway associated with the terminal and containing at least the identifier of the terminal. After receiving the query message, the second function can determine the second information according to the identifier of the terminal and send the second information to the third function.
  • the network side needs to first determine whether the resident gateway has created the second PDU session. When it is determined that the resident gateway has created the second PDU session, the network side can directly create the first PDU session. When it is determined that the resident gateway has not created the second PDU session, the network side needs to first create the second PDU session and needs to determine whether the second PDU session is successfully created. When it is determined that the second PDU session is successfully created, the first PDU session is created.
  • the network side can use the following two methods to determine whether the resident gateway has created the second PDU session:
  • Mode 1 the third function determines whether the resident gateway has established the second PDU session
  • Mode 2 The resident gateway determines whether it has created the second PDU session.
  • the third function can first determine the S-NSSAI set corresponding to all PDU sessions currently created by the resident gateway, and compare the S-NSSAI in the set with the first S-NSSAI. If there are one or more S-NSSAI in the set that can match the first S-NSSAI, it can be determined that the resident gateway has created the second PDU session. Among them, the one or more S-NSSAI can match the first S-NSSAI, which can be understood as the current capability of the resident gateway matches the first S-NSSAI, or it can be understood as the network slice currently accessed by the resident gateway can meet the service requirements corresponding to the network slice that the terminal needs to access.
  • the resident gateway has created the second PDU session if the set meets at least one of the following three conditions: Condition A, the set contains the first S-NSSAI; Condition B, the SLA guarantee level of one or more S-NSSAI in the set is not lower than that of the first S-NSSAI, that is, the one or more S-NSSAI
  • the S-NSSAI can support the service of the first S-NSSAI; Condition C, there are one or more S-NSSAIs in the set that can be mapped to the first S-NSSAI.
  • the method may further include:
  • the resident gateway has not created the second PDU session, create the second PDU session; and determine whether the second PDU session of the resident gateway is successfully created. If it is determined that the second PDU session of the resident gateway is successfully created, create the first PDU session.
  • the determining whether the resident gateway has created the second PDU session may include:
  • the first S-NSSAI set includes S-NSSAIs corresponding to all PDU sessions created by the resident gateway;
  • determining (i.e., judging) whether the resident gateway has created the second PDU session by comparing the S-NSSAI in the first S-NSSAI set with the first S-NSSAI may include:
  • the third function can determine that the resident gateway has created the second PDU session; when the first S-NSSAI set does not include an S-NSSAI that satisfies the second condition, the third function can determine that the resident gateway has not created the second PDU session.
  • the second condition is associated with the first S-NSSAI, which can be understood as the second condition being determined at least according to the first S-NSSAI, or the second condition containing the first S-NSSAI.
  • the second condition requires that the S-NSSAI that meets the second condition can match the first S-NSSAI, that is, the capability of the resident gateway needs to match the first S-NSSAI, or it can be understood that the network slice accessed by the resident gateway can meet the service requirements corresponding to the network slice that the terminal needs to access.
  • the first condition may include at least one of the above-mentioned conditions A, B, and C.
  • the second condition may include at least one of the following:
  • the S-NSSAI is the same as the first S-NSSAI;
  • the guarantee level of the SLA corresponding to the S-NSSAI is higher than or equal to the guarantee level of the SLA corresponding to the first S-NSSAI, and the S-NSSAI supports the service corresponding to the first S-NSSAI;
  • the third function determines that the resident gateway has created the second PDU. After that, the first PDU session can be created directly.
  • creating the first PDU session may include:
  • the first PDU session is directly created.
  • the third function can trigger the creation process of the second PDU session, and then create the first PDU session if the second PDU session is successfully created.
  • the method may further include:
  • fifth information is sent to the resident gateway, where the fifth information indicates the creation of the second PDU session.
  • the fifth information may include:
  • the identifier of the terminal is the identifier of the terminal.
  • the fifth information may also include seventh information, and the seventh information indicates that the type of the fifth information is information indicating the creation of a second PDU session capable of carrying the service corresponding to the first S-NSSAI.
  • the seventh information may also be referred to as a cell type indication, etc.
  • the name of the seventh information is not limited in the embodiment of the present application, as long as its function is implemented.
  • the specific implementation method of the seventh information may also be determined according to requirements, such as bit, bitmap, number, character string, etc., which is not limited in the embodiment of the present application.
  • a bit1 type value of "1" may indicate that the type of the fifth information is information indicating the creation of a second PDU session capable of carrying the service corresponding to the first S-NSSAI.
  • the resident gateway can select an S-NSSAI (referred to as the second S-NSSAI in the subsequent description) that matches the first S-NSSAI required by the terminal from the second NSSAI, and initiate a PDU session establishment request corresponding to the second S-NSSAI to the third function, that is, send a request to create the second PDU session.
  • the resident gateway can determine the S-NSSAI in the second NSSAI that meets the second condition as the second S-NSSAI, and send a PDU session establishment request containing the second S-NSSAI to the third function.
  • the method may further include:
  • sixth information sent by the resident gateway where the sixth information is used to request to create the second PDU session, where the sixth information includes a second S-NSSAI, and the second S-NSSAI is associated with the first S-NSSAI;
  • the second S-NSSAI is associated with the first S-NSSAI, which can be understood as
  • the second S-NSSAI is an S-NSSAI that matches the first S-NSSAI, that is, an S-NSSAI that satisfies the second condition.
  • the third function needs to determine whether the second PDU session is successfully created. If it is determined that the second PDU session is successfully created, the first PDU session is created; if it is determined that the second PDU session fails to be created, the third function can notify the terminal of the failure to create the second PDU session to terminate the creation process of the first PDU session, and can indicate the reason for the failure to create the second PDU session to the terminal.
  • the embodiment of the present application does not limit the specific reason for the failure to create the second PDU session.
  • the reason for the failure to create the second PDU session may include: the capability of the resident gateway does not match the first S-NSSAI, that is, the capability of the resident gateway cannot support the business requirements corresponding to the first S-NSSAI, or it can be understood that none of the S-NSSAI in the second NSSAI meets the second condition.
  • the method may further include:
  • eighth information is sent to the terminal, where the eighth information indicates that the capability of the resident gateway does not match the first S-NSSAI and instructs to terminate the creation process of the first PDU session.
  • the third function can determine whether the second PDU session is successfully created or failed based on the information fed back by the resident gateway.
  • the method may further include:
  • the ninth information may include the reason why the second PDU session creation failed, such as the capability of the resident gateway does not match the first S-NSSAI (that is, none of the S-NSSAIs in the second NSSAI meets the second condition), etc.
  • the third function can send the traffic diversion rule of the terminal to the resident gateway (referred to as the first rule in the subsequent description) to instruct the resident gateway to forward the uplink traffic of the terminal to the specified PDU session (i.e., the second PDU session).
  • the method may further include:
  • a first rule is sent to the resident gateway, where the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the third function may send the first rule to the resident gateway through the first function.
  • the first rule may include at least one of the following:
  • An identifier of the second PDU session (such as an ID, etc.).
  • the description information of the uplink traffic of the terminal is used to indicate that the resident gateway needs to identify
  • the characteristics of the uplink traffic data packet of the terminal may include the IP address, MAC address and other contents of the terminal.
  • the embodiment of the present application does not limit the specific content of the description information as long as its function is implemented.
  • the identifier of the second PDU session is used to indicate the diverted PDU session of the uplink traffic of the terminal identified by the resident gateway, and the PDU session can carry the slicing requirements of the terminal; in other words, the second PDU session can carry the service corresponding to the first S-NSSAI.
  • the third function can specify a second PDU session among the two second PDU sessions to carry the service, that is, to carry the uplink traffic of the terminal.
  • the method may further include:
  • a second PDU session satisfying a third condition is determined from the at least two second PDU sessions, and the first rule is used to forward the uplink traffic of the terminal to the second PDU session satisfying the third condition.
  • the third condition can be determined according to demand, and the embodiment of the present application does not limit this.
  • the third condition can include the second PDU session with the smallest corresponding slice load among the two second PDU sessions; in other words, the third function can determine the slice load corresponding to each second PDU session based on the slice performance related data provided by the network data analysis function (NWDAF, Network Data Analytics Function), and specify the second PDU session with the smallest corresponding slice load to carry the uplink traffic of the terminal.
  • NWDAF Network Data Analytics Function
  • the third function may not need to determine whether the resident gateway has created the second PDU session, but directly send the fifth information to the resident gateway.
  • the resident gateway may determine whether it has created the second PDU session based on the first S-NSSAI in the fifth information, and if it is determined that it has not created the second PDU session, send the sixth information to the third function to request to create the second PDU session; if it is determined that it has created the second PDU session, the resident gateway may directly configure the first rule locally.
  • an embodiment of the present application further provides an information transmission method, which is applied to a resident gateway. As shown in FIG10 , the method includes:
  • Step 1001 Send a second NSSAI to a first function to determine a first NSSAI that a terminal associated with the resident gateway is allowed to use, the terminal communicates with a network side through the resident gateway, the network side includes the first function, the second NSSAI includes the NSSAI that the resident gateway is allowed to use, and the first NSSAI is associated with the second NSSAI.
  • the terminal associated with the resident gateway can be understood as a terminal accessing the resident gateway, or can be understood as a terminal communicating with the network side through the resident gateway.
  • the method may further include:
  • Step 1002 Receive the fifth information sent by the third function, the fifth information indicating the creation of the The second PDU session can carry the service corresponding to the first S-NSSAI, and the first S-NSSAI is associated with the first PDU session of the terminal.
  • the first S-NSSAI is associated with the first PDU session of the terminal, which can be understood as the first PDU session being at least used to carry the service corresponding to the first S-NSSAI, or it can be understood as the information used to request the creation of the first PDU session (i.e., the above-mentioned fourth information) will include the first S-NSSAI.
  • the fifth information may be sent after the third function determines whether the resident gateway has created the second PDU session, and determines that the resident gateway has not created the second PDU session. Accordingly, after receiving the fifth information, the resident gateway no longer needs to determine whether it has created the second PDU session, but can directly determine that it has not created the second PDU session, that is, the resident gateway can directly send the sixth information for requesting the creation of the second PDU session to the third function, triggering the creation process of the second PDU session.
  • the fifth information may be directly sent by the third function after receiving the fourth information, that is, after the resident gateway receives the fifth information, it needs to determine whether it has created the second PDU session based on the first S-NSSAI in the fifth information. If it is determined that it has not created the second PDU session, the sixth information is sent to the third function to request the creation of the second PDU session; if it is determined that it has created the second PDU session, the resident gateway can directly configure the first rule locally.
  • the method may further include:
  • sixth information is sent to the third function, where the sixth information is used to request the creation of the second PDU session, and the sixth information includes a second S-NSSAI, where the second S-NSSAI is associated with the first S-NSSAI.
  • the second S-NSSAI is associated with the first S-NSSAI, which can be understood as the second S-NSSAI is the S-NSSAI that matches the first S-NSSAI, that is, the S-NSSAI that satisfies the second condition.
  • the determining whether the resident gateway has created the second PDU session may include:
  • the first S-NSSAI set includes S-NSSAIs corresponding to all PDU sessions created by the resident gateway;
  • determining (i.e., judging) whether the resident gateway has created the second PDU session by comparing the S-NSSAI in the first S-NSSAI set with the first S-NSSAI may include:
  • the resident gateway can determine that it has created the second PDU session; when the first S-NSSAI set does not include an S-NSSAI that satisfies the second condition, the resident gateway can determine that it has not created the second PDU session.
  • the resident gateway needs to first determine the second S-NSSAI that matches the first S-NSSAI, that is, determine the second S-NSSAI that meets the second condition.
  • the method before sending the sixth information to the third function, the method may further include:
  • An S-NSSAI in the second NSSAI that satisfies a second condition is determined as the second S-NSSAI.
  • the resident gateway may directly configure the first rule locally.
  • the method may further include:
  • a first rule is configured locally, where the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the third function needs to determine whether the second PDU session is successfully created. If the second PDU session is successfully created, the third function can send the first rule to the resident gateway.
  • the method may further include:
  • a first rule sent by the third function is received, where the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the first rule is used to forward the uplink traffic of the terminal to a second PDU session among the at least two second PDU sessions that meets the third condition.
  • the method may further include:
  • ninth information is sent to the third function, where the ninth information indicates that the creation of the second PDU session fails.
  • the information transmission method provided in the embodiment of the present application comprises: a first function receiving first information sent by a terminal, wherein the first information is used to request registration related to a network slice; determining a first NSSAI that the terminal is allowed to use, and sending third information to the terminal, wherein the third information includes the first NSSAI, wherein the first NSSAI is associated with a second NSSAI, and the second NSSAI includes The resident gateway associated with the terminal is allowed to use the NSSAI, the terminal communicates with the network side through the resident gateway, and the network side includes the first function.
  • the network function determines the resident gateway associated with the terminal, that is, determines the resident gateway connected to the terminal, and determines the NSSAI allowed to be used by the terminal based on the NSSAI allowed to be used by the resident gateway connected to the terminal, thereby enabling the terminal and the resident gateway to collaborate on the network slices allowed to be used, and then subsequently enabling the terminal and the resident gateway to collaborate when accessing the network slice; in other words, the network slice accessed by the resident gateway can meet the service requirements corresponding to the network slice that the terminal needs to access, that is, the performance of the channel between the resident gateway and the network side can meet the service requirements of the terminal, thereby ensuring the normal operation of the terminal's services.
  • the terminal and the resident gateway can collaborate when accessing the network slice, it is possible to flexibly use 5G network slicing technology through non-3GPP access in the fixed-mobile convergence scenario (i.e., the above-mentioned architecture 2), thereby promoting a deeper integration of 5G and wired networks.
  • the terminal includes a 5G terminal, represented by 5G UE; the resident gateway includes a 5G resident gateway, represented by 5G-RG; the first function includes AMF; the second function includes UDM; and the third function includes SMF.
  • the 5G-RG when the 5G-RG connects to the 5G UE to initiate a network slice-related registration process, if the 5G UE's registration request (i.e., the first information mentioned above) carries the Requested NSSAI (i.e., the third NSSAI mentioned above), the 5G network needs to determine the 5G UE's Allowed NSSAI (i.e., the first NSSAI mentioned above) in combination with the network slices currently supported by the 5G-RG. Specifically, as shown in FIG11 , the network slice-related registration process of the 5G-RG connecting to the 5G UE may include the following steps:
  • Step 1101 The 5G UE sends a registration request (i.e., the first information) carrying the Requested NSSAI (i.e., the third NSSAI) to the AMF, and then executes step 1102;
  • a registration request i.e., the first information
  • the Requested NSSAI i.e., the third NSSAI
  • Step 1102 AMF generates the original Allowed NSSAI (i.e., the fourth NSSAI) of the UE according to the process specified in the relevant technology, and then executes step 1103;
  • the original Allowed NSSAI i.e., the fourth NSSAI
  • Step 1103 AMF queries the 5G-RG associated with the 5G UE from the UDM, and then executes step 1104;
  • Step 1104 AMF obtains (can also be understood as querying) the Allowed NSSAI (i.e., the second NSSAI) of 5G-RG from 5G-RG, and then executes step 1105;
  • the Allowed NSSAI i.e., the second NSSAI
  • Step 1105 AMF compares the Allowed NSSAI of 5G-RG with the original Allowed NSSAI of UE Compare and take the intersection to obtain the final Allowed NSSAI of the 5G UE (which can be understood as the new Allowed NSSAI, i.e., the first NSSAI mentioned above), and then execute step 1106;
  • Step 1106 AMF sends a registration acceptance message carrying the final Allowed NSSAI to the 5G UE.
  • the registration request sent by the 5G UE to the AMF can actually be sent from the 5G UE to the TNGF/N3IWF first, and the TNGF/N3IWF selects the AMF according to the slice information (i.e., Requested NSSAI) in the registration request and related information of the local configuration, and then forwards the registration request to the selected AMF.
  • slice information i.e., Requested NSSAI
  • AMF can verify the Requested NSSAI in the registration request based on the contract information such as the NSSAI of the 5G UE obtained from UDM, as well as some slice-related information interacted with NSSF or stored locally, and generate the original Allowed NSSAI of the UE.
  • AMF may verify the Requested NSSAI in the network slice-related registration request of 5G-RG based on the contract information such as the NSSAI signed by 5G-RG obtained from UDM, as well as some slice-related information interacted with NSSF or stored locally, and generate the Allowed NSSAI of 5G-RG.
  • step 1101, step 1102 and step 1104 can be understood by referring to the provisions of the relevant technology, and this application example will not go into details.
  • step 1105 when the AMF compares the Allowed NSSAI of the 5G-RG with the original Allowed NSSAI of the UE, for each S-NSSAI in the original Allowed NSSAI of the UE, the S-NSSAI needs to meet at least one of the following three conditions (i.e., the first condition above) to be selected as the final Allowed NSSAI of the UE:
  • Condition 1 The S-NSSAI is included in the Allowed NSSAI of 5G-RG;
  • Condition 2 There is at least one S-NSSAI in the Allowed NSSAI of the 5G-RG, and the SLA guarantee level of the at least one S-NSSAI is not lower than that of the S-NSSAI, and the service of the S-NSSAI can be supported;
  • Condition 3 there is at least one S-NSSAI in the Allowed NSSAI of 5G-RG, and the at least one S-NSSAI can be mapped to the S-NSSAI.
  • the registration acceptance message may also carry one or more of the contents of Configured NSSAI, Rejected NSSAI, Pending NSSAI, etc., which are not limited in this application example. It can be understood that the Rejected NSSAI includes all S-NSSAI in the Requested NSSAI of the 5G UE that are not selected into the final Allowed NSSAI.
  • the 5G-RG when the 5G-RG is connected to the 5G UE to initiate the network slicing-related PDU session creation process, if the 5G UE's PDU session creation request (i.e., the fourth information mentioned above) carries S-NSSAI (i.e., the first S-NSSAI mentioned above), the 5G network needs to verify the network slice currently accessed by the 5G-RG to determine whether the channel currently established by the 5G-RG can carry the slicing requirements of the 5G UE.
  • the network slicing-related PDU session establishment process of the 5G-RG connecting to the 5G UE can include the following steps:
  • Step 1210 5G UE sends a packet carrying S-NSSAI (i.e., the first S-NSSAI mentioned above) to AMF
  • S-NSSAI i.e., the first S-NSSAI mentioned above
  • PDU session creation request i.e., the fourth information above
  • Step 1220 AMF selects SMF and forwards the PDU session creation request of 5G UE to the SMF, and then executes step 1230;
  • Step 1230 SMF queries the 5G-RG associated with the 5G UE from the UDM, and ensures that a PDU session (i.e., the second PDU session mentioned above) that can carry the S-NSSAI required by the 5G UE is created on the 5G-RG by executing step 1204 or step 1205, and then executes step 1240 or step 1250;
  • a PDU session i.e., the second PDU session mentioned above
  • Step 1240 The SMF determines whether the 5G-RG has created a PDU session that can carry the S-NSSAI required by the 5G UE, and then executes step 1260;
  • Step 1250 The 5G-RG determines whether it has created a PDU session that can carry the S-NSSAI required by the 5G UE, and then executes step 1260;
  • Step 1260 Subsequent process for creating a 5G UE PDU session (i.e., the first PDU session mentioned above).
  • step 1240 may specifically include the following steps:
  • Step 1241 SMF determines whether 5G-RG has created a PDU session (i.e., the second PDU session) that can carry the S-NSSAI required by 5G UE. If not, execute step 1242; if yes, execute step 1243;
  • Step 1242 SMF sends a PDU session creation indication (i.e., the fifth information) to 5G-RG. If the PDU session is successfully created, execute step 1243.
  • a PDU session creation indication i.e., the fifth information
  • Step 1243 SMF sends the 5G UE traffic diversion rules (i.e. the first rule mentioned above) to 5G-RG.
  • SMF can determine the S-NSSAI set (i.e. determine the above-mentioned first S-NSSAI set) to which all PDU sessions currently created by 5G-RG belong, and compare the set with the S-NSSAI required by 5G UE (i.e. the above-mentioned first S-NSSAI).
  • SMF can determine (i.e.
  • SMF can determine (i.e. judge) that 5G-RG has not created a PDU session that can carry the S-NSSAI required by 5G UE, and needs to execute step 1242.
  • the S-NSSAI set to which all PDU sessions currently created by 5G-RG belong contains the S-NSSAI required by 5G UE;
  • Condition B There is at least one S-NSSAI in the S-NSSAI set to which all PDU sessions currently created by 5G-RG belong, and the SLA guarantee level of the at least one S-NSSAI is not lower than the S-NSSAI required by 5G UE, and the service of the S-NSSAI can be supported;
  • Condition C There is at least one S-NSSAI in the S-NSSAI set to which all PDU sessions currently created by 5G-RG belong, and the at least one S-NSSAI can be mapped to the S-NSSAI required by 5G UE.
  • SMF may send a PDU session creation indication (i.e., the fifth information) to 5G-RG through AMF, and the indication may include at least one of the following:
  • the cell type indication (i.e. the seventh information) is used to indicate that the type of this cell sent to the 5G-RG is "an indication of creating a PDU session that can carry the network slice required by the 5G UE;
  • the S-NSSAI required by the 5G UE (i.e., the first S-NSSAI mentioned above) is used to indicate the identifier of the network slice that the 5G-RG should carry, i.e., the network slice that the 5G UE needs to access;
  • the 5G UE identifier is used to indicate the 5G UE served by the network slice in this cell, which can be achieved through MSISDN, IMSI, SUPI, SUCI, IP address, MAC address, PEI, etc.
  • 5G-RG After receiving the PDU session creation indication, 5G-RG can select the S-NSSAI (i.e., the second S-NSSAI mentioned above) that matches the S-NSSAI required by 5G UE from its own Allowed NSSAI, and initiate a PDU session establishment request (i.e., send the sixth information mentioned above). If the 5G-RG PDU session is successfully created, step 1243 can be continued. If the 5G-RG PDU session creation fails, 5G-RG can send a failure feedback to SMF (i.e., send the ninth information mentioned above), and SMF can return a PDU session creation failure message (i.e., the eighth information mentioned above) carrying a reason code to 5G UE. The reason code can indicate that the current capability of 5G-RG cannot match the S-NSSAI required by 5G UE, and terminate the PDU session creation process of 5G UE.
  • SMF i.e., send the ninth information mentioned above
  • PDU session creation failure message i.e., the
  • SMF may send the 5G UE traffic diversion rule (i.e., the first rule mentioned above) to 5G-RG through AMF, instructing 5G-RG to forward the uplink traffic of 5G UE to the specified PDU session (i.e., the PDU session that carries the S-NSSAI required by 5G UE, i.e., the second PDU session mentioned above).
  • the 5G UE traffic diversion rule may include at least one of the following contents:
  • 5G UE traffic description i.e., the description information of the uplink traffic of the above-mentioned terminal
  • the 5G-RG needs to identify including but not limited to the IP address and MAC address of the UE
  • the PDU session ID (i.e., the identifier of the second PDU session mentioned above) is used to indicate the diverted PDU session of the identified 5G UE's traffic, and this PDU session can carry the slicing requirements of the 5G UE; when there are multiple PDU sessions that meet the UE requirements on the 5G-RG, the SMF can designate one of the PDU sessions (i.e., the second PDU session that meets the third condition mentioned above) to carry the service.
  • the designation method can be determined by the SMF itself or the PDU session ID corresponding to the slice with a smaller current load can be specified based on the slice performance data provided by the NWDAF.
  • step 1250 may specifically include the following steps:
  • Step 1251 SMF sends a PDU session creation indication (i.e., the fifth information) to 5G-RG, and then executes step 1252;
  • a PDU session creation indication i.e., the fifth information
  • Step 1252 The 5G-RG determines whether it has created a PDU session (i.e., the second PDU session) that can carry the S-NSSAI required by the 5G UE. If not, execute step 1253; if yes, execute step 1254;
  • Step 1253 5G-RG sends a PDU session establishment request (i.e., the sixth information) to SMF. If the PDU session is successfully established, execute step 1254;
  • Step 1254 5G-RG locally configures 5G UE traffic diversion rules.
  • the content included in the PDU session creation indication in step 1251 can be the same as the content included in the PDU session creation indication in the above-mentioned step 1242, which will not be repeated here.
  • 5G-RG can compare the S-NSSAI set (i.e., determine the above-mentioned first S-NSSAI set) to which all PDU sessions currently created by itself belong with the S-NSSAI required by 5G UE (i.e., the above-mentioned first S-NSSAI set).
  • 5G-RG can select an S-NSSAI (i.e., the second S-NSSAI mentioned above) that matches the S-NSSAI required by 5G UE from its own Allowed NSSAI, and initiate a PDU session establishment request (i.e., send the sixth information mentioned above). If the 5G-RG PDU session is successfully created, step 1254 can be continued. If the 5G-RG PDU session creation fails, 5G-RG can send a failure feedback to SMF (i.e., send the ninth information mentioned above), and SMF can return a PDU session creation failure message (i.e., the eighth information mentioned above) carrying a reason code to 5G UE. The reason code can indicate that the current capability of 5G-RG cannot match the S-NSSAI required by 5G UE, and terminate the PDU session creation process of 5G UE.
  • SMF i.e., send the ninth information mentioned above
  • PDU session creation failure message i.e., the eighth information mentioned above
  • the 5G-RG can locally configure the 5G UE traffic diversion rules to forward the uplink traffic of the 5G UE to the PDU session that can carry the S-NSSAI required by the 5G UE.
  • the content of the 5G UE traffic diversion rules in this step can be the same as the content of the 5G UE traffic diversion rules in the above step 1243, which will not be repeated here.
  • SMF can continue to execute subsequent processes created by the 5G UE PDU session (i.e., the first PDU session mentioned above) according to the provisions of relevant technologies, such as the selection of user plane function (UPF, User Plane Function) and the configuration of forwarding rules, etc.
  • UPF User Plane Function
  • This application example will not go into details about these related processes.
  • the solution provided by this application example realizes the collaboration between 5G UE and 5G-RG on network slicing, and realizes the collaboration between 5G UE and 5G-RG when accessing network slices, thereby ensuring the normal operation of 5G UE services.
  • 5G UE can flexibly use 5G network slicing technology through non-3GPP access in fixed-mobile convergence scenarios, thereby promoting a deeper integration of 5G and wired networks.
  • the embodiment of the present application further provides an information transmission device, which is arranged on the first function, as shown in FIG13, and the device includes:
  • the first receiving unit 1301 is configured to receive first information sent by a terminal, where the first information is used to request registration related to a network slice;
  • the first processing unit 1304 is configured to determine a first NSSAI that the terminal is allowed to use, the first NSSAI being associated with a second NSSAI; the second NSSAI includes an NSSAI that a resident gateway associated with the terminal is allowed to use, the terminal communicates with a network side through the resident gateway, and the network side includes a first function;
  • the first sending unit 1305 is configured to send third information to the terminal.
  • the third information Contains the first NSSAI.
  • the device may further include:
  • a first acquiring unit 1302 is configured to acquire second information, where the second information represents the resident gateway;
  • the second obtaining unit 1303 is configured to obtain the second NSSAI that the resident gateway is allowed to use.
  • the first processing unit 1304 is further configured to:
  • the first NSSAI is determined by comparing the fourth NSSAI with the second NSSAI.
  • the first processing unit 1304 is further configured to determine an S-NSSAI in the fourth NSSAI that satisfies a first condition, the first condition is associated with the second NSSAI, and the first NSSAI includes the S-NSSAI that satisfies the first condition.
  • the first obtaining unit 1302 is further configured to obtain the second information from a second function, where the second function is at least used to store an association relationship between the terminal and the resident gateway.
  • the second obtaining unit 1303 is further configured to obtain the second NSSAI from the resident gateway.
  • the first receiving unit 1301 is further configured to receive fourth information sent by the terminal, where the fourth information is used to request to create a first PDU session of the terminal, and the fourth information includes a first S-NSSAI in the first NSSAI;
  • the first sending unit 1305 is further configured to send the fourth information to the third function.
  • the first receiving unit 1301 and the first sending unit 1305 can be implemented by the communication interface in the first function; the first acquisition unit 1302 and the second acquisition unit 1303 can be implemented by the processor in the first function combined with the communication interface; the first processing unit 1304 can be implemented by the processor in the first function.
  • the embodiment of the present application further provides an information transmission device, which is set on the third function, as shown in FIG14, and the device includes:
  • the second receiving unit 1401 is configured to receive fourth information sent by the first function, where the fourth information is used to request to create a first PDU session of the terminal, where the fourth information includes a first S-NSSAI in a first NSSAI that the terminal is allowed to use, where the first NSSAI is associated with a second NSSAI, where the second NSSAI includes an NSSAI that a resident gateway associated with the terminal is allowed to use, where the terminal communicates with a network side through the resident gateway, and where the network side includes the first function;
  • the second processing unit 1403 is configured to create the first PDU session when the second PDU session of the resident gateway is successfully created, and the second PDU session can carry the first 1. Services corresponding to S-NSSAI.
  • the device may further include:
  • the third acquiring unit 1402 is configured to acquire second information, where the second information represents the resident gateway.
  • the device may further include:
  • the second sending unit 1404 is configured to send fifth information to the resident gateway, where the fifth information indicates the creation of the second PDU session.
  • the second receiving unit 1401 is further configured to receive sixth information sent by the resident gateway, where the sixth information is used to request to create the second PDU session, and the sixth information includes a second S-NSSAI, where the second S-NSSAI is associated with the first S-NSSAI;
  • the second processing unit 1403 is also configured to create the second PDU session.
  • the second sending unit 1404 is further configured to send the fifth information to the resident gateway when the resident gateway does not create the second PDU session.
  • the second processing unit 1403 is further configured to:
  • the first S-NSSAI set includes S-NSSAIs corresponding to all PDU sessions created by the resident gateway;
  • the second processing unit 1403 is further configured to:
  • the resident gateway has created the second PDU session
  • the resident gateway does not create the second PDU session.
  • the second sending unit 1404 is further configured to send a first rule to the resident gateway when the second PDU session of the resident gateway is successfully created, wherein the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the second processing unit 1403 is further configured to determine, when the resident gateway has created at least two second PDU sessions, a second PDU session that satisfies a third condition from the at least two second PDU sessions, and the first rule is used to forward the uplink traffic of the terminal to the second PDU session that satisfies the third condition.
  • the second sending unit 1404 is further configured to send eighth information to the terminal when the creation of the second PDU session fails, wherein the eighth information indicates that the capability of the resident gateway does not match the first S-NSSAI and indicates to terminate the creation process of the first PDU session.
  • the second receiving unit 1401 is further configured to receive ninth information sent by the resident gateway, where the ninth information indicates that the second PDU session creation fails.
  • the third obtaining unit 1402 is further configured to obtain the second information from a second function, where the second function is at least used to store an association relationship between the terminal and the resident gateway.
  • the second receiving unit 1401 and the second sending unit 1404 can be implemented by the communication interface in the third function;
  • the third acquisition unit 1402 can be implemented by the processor in the third function combined with the communication interface;
  • the second processing unit 1403 can be implemented by the processor in the third function.
  • the embodiment of the present application further provides an information transmission device, which is arranged on the resident gateway, as shown in FIG. 15 , and the device includes:
  • the third sending unit 1501 is configured to send a second NSSAI to the first function to determine the first NSSAI that the terminal associated with the resident gateway is allowed to use, the terminal communicates with the network side through the resident gateway, the network side includes the first function, the second NSSAI includes the NSSAI that the resident gateway is allowed to use, and the second NSSAI is associated with the first NSSAI.
  • the device may further include:
  • the third receiving unit 1502 is configured to receive fifth information sent by the third function, where the fifth information indicates the creation of a second PDU session, where the second PDU session can carry the service corresponding to the first S-NSSAI, and the first S-NSSAI is associated with the first PDU session of the terminal.
  • the third sending unit 1501 is further configured to send sixth information to the third function when the resident gateway has not created the second PDU session, the sixth information being used to request the creation of the second PDU session, the sixth information including a second S-NSSAI, and the second S-NSSAI being associated with the first S-NSSAI.
  • the device may further include:
  • the third processing unit 1503 is configured to determine the S-NSSAI that satisfies the second condition in the second NSSAI as the second S-NSSAI.
  • the third processing unit 1503 is further configured as:
  • the first S-NSSAI set includes S-NSSAIs corresponding to all PDU sessions created by the resident gateway;
  • the third processing unit 1503 is further configured as:
  • the resident gateway has created the second PDU session
  • the resident gateway does not create the second PDU session.
  • the third processing unit 1503 is further configured to locally configure a first rule when the resident gateway has created the second PDU session, wherein the first rule is used to Forwarding the uplink traffic of the terminal to the second PDU session.
  • the third receiving unit 1502 is further configured to receive a first rule sent by the third function when the second PDU session is successfully created, wherein the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the third sending unit 1501 is further configured to send ninth information to the third function when the creation of the second PDU session fails, and the ninth information indicates that the creation of the second PDU session fails.
  • the third sending unit 1501 and the third receiving unit 1502 can be implemented by the communication interface in the resident gateway; the third processing unit 1503 can be implemented by the processor in the resident gateway.
  • the information transmission device provided in the above embodiment only uses the division of the above program modules as an example when performing information transmission.
  • the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the information transmission device provided in the above embodiment and the information transmission method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • the embodiment of the present application further provides a first function, as shown in FIG. 16 , the first function 1600 includes:
  • the first communication interface 1601 is capable of exchanging information with at least one of a terminal, a resident gateway and other network functions;
  • a first processor 1602 is connected to the first communication interface 1601 to implement information interaction with at least one of a terminal, a resident gateway, and other network functions, and is configured to execute the method provided by one or more technical solutions of the first function side when running a computer program;
  • a first memory 1603 on which the computer program is stored.
  • the first communication interface 1601 is configured to receive first information sent by a terminal, where the first information is used to request registration related to a network slice;
  • the first processor 1602 is configured to determine a first NSSAI that the terminal is allowed to use, and send third information to the terminal through the first communication interface 1601, the third information including the first NSSAI, the first NSSAI is associated with a second NSSAI, the second NSSAI includes the NSSAI that a resident gateway associated with the terminal is allowed to use, the terminal communicates with a network side through the resident gateway, and the network side includes the first function 1600.
  • the first processor 1602 is further configured to:
  • the first information includes the third NSSAI of the terminal, In the case where the NSSAI includes the NSSAI requested by the terminal, the first processor 1602 is further configured to:
  • the first NSSAI is determined by comparing the fourth NSSAI with the second NSSAI.
  • the first processor 1602 is further configured to determine an S-NSSAI in the fourth NSSAI that satisfies a first condition, the first condition is associated with the second NSSAI, and the first NSSAI includes the S-NSSAI that satisfies the first condition.
  • the first processor 1602 is further configured to obtain the second information from a second function through the first communication interface 1601, where the second function is at least used to store an association relationship between the terminal and the resident gateway.
  • the first processor 1602 is further configured to obtain the second NSSAI from the resident gateway through the first communication interface 1601.
  • the first communication interface 1601 is further configured as:
  • the fourth information is used to request to establish a first PDU session of the terminal, and the fourth information includes a first S-NSSAI in the first NSSAI;
  • the fourth information is sent to the third function.
  • bus system 1604 is used to realize the connection and communication between these components.
  • bus system 1604 also includes a power bus, a control bus and a status signal bus.
  • various buses are marked as bus system 1604 in Figure 16.
  • the first memory 1603 in the embodiment of the present application is configured to store various types of data to support the operation of the first function 1600. Examples of such data include: any computer program for operating on the first function 1600.
  • the method disclosed in the above-mentioned embodiment of the present application can be applied to the first processor 1602, or implemented by the first processor 1602.
  • the first processor 1602 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above-mentioned method can be completed by the hardware integrated logic circuit in the first processor 1602 or the instruction in the form of software.
  • the above-mentioned first processor 1602 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP Digital Signal Processor
  • the first processor 1602 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • a general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as a hardware decoding processor to be executed, or the hardware and software in the decoding processor can be used.
  • the module combination is executed.
  • the software module may be located in a storage medium, and the storage medium is located in the first memory 1603.
  • the first processor 1602 reads the information in the first memory 1603 and completes the steps of the above method in combination with its hardware.
  • the embodiment of the present application further provides a third function, as shown in FIG. 17 , the third function 1700 includes:
  • the second communication interface 1701 is capable of exchanging information with at least one of a terminal, a resident gateway and other network functions;
  • the second processor 1702 is connected to the second communication interface 1701 to implement information interaction with at least one of the terminal, the resident gateway and other network functions, and is configured to execute the method provided by one or more technical solutions of the third function side when running the computer program;
  • a second memory 1703 on which the computer program is stored.
  • the second communication interface 1701 is further configured to send fifth information to the resident gateway, where the fifth information indicates the creation of the second PDU session.
  • the second communication interface 1701 is further configured to receive sixth information sent by the resident gateway, where the sixth information is used to request to create the second PDU session, and the sixth information includes a second S-NSSAI, where the second S-NSSAI is associated with the first S-NSSAI;
  • the second communication interface 1701 is further configured to send the fifth information to the resident gateway when the resident gateway does not create the second PDU session.
  • the second processor 1702 is further configured to:
  • the resident gateway has created the second PDU session
  • the resident gateway does not create the second PDU session.
  • the second communication interface 1701 is further configured to send a first rule to the resident gateway when the second PDU session of the resident gateway is successfully created, wherein the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the second communication interface 1701 is further configured to receive ninth information sent by the resident gateway, where the ninth information indicates that the second PDU session creation fails.
  • the second processor 1702 is further configured to obtain the second information from a second function through the second communication interface 1701, where the second function is at least used to store an association relationship between the terminal and the resident gateway.
  • the second memory 1703 in the embodiment of the present application is configured to store various types of data to support the operation of the third function 1700. Examples of such data include: any computer program for operating on the third function 1700.
  • the method disclosed in the above embodiment of the present application can be applied to the second processor 1702, or The second processor 1702 implements the method.
  • the second processor 1702 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the second processor 1702.
  • the second processor 1702 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the second processor 1702 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • a general-purpose processor may be a microprocessor or any conventional processor, etc.
  • the third function 1700 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned method.
  • the embodiment of the present application further provides a resident gateway, as shown in FIG. 18 , the resident gateway 1800 includes:
  • the third communication interface 1801 is capable of information interaction with the terminal and/or network function
  • the third processor 1802 is connected to the third communication interface 1801 to implement information interaction with the terminal and/or the network function, and is configured to execute the method provided by one or more technical solutions of the above-mentioned resident gateway side when running the computer program;
  • a third memory 1803 on which the computer program is stored.
  • the third communication interface 1801 is configured to send a second NSSAI to the first function to determine the first NSSAI that the terminal associated with the resident gateway 1800 is allowed to use, the terminal communicates with the network side through the resident gateway 1800, the network side includes the first function, the second NSSAI includes the NSSAI that the resident gateway 1800 is allowed to use, and the second NSSAI is associated with the first NSSAI.
  • the third communication interface 1801 is also configured to receive fifth information sent by the third function, and the fifth information indicates the creation of a second PDU session, and the second PDU session can carry the service corresponding to the first S-NSSAI, and the first S-NSSAI is associated with the first PDU session of the terminal.
  • the third communication interface 1801 is also configured to send sixth information to the third function when the resident gateway 1800 has not created the second PDU session, and the sixth information is used to request the creation of the second PDU session.
  • the sixth information includes a second S-NSSAI, and the second S-NSSAI is associated with the first S-NSSAI.
  • the third processor 1802 is configured to determine an S-NSSAI in the second NSSAI that satisfies a second condition as the second S-NSSAI.
  • the third processor 1802 is further configured to:
  • the first S-NSSAI set includes S-NSSAIs corresponding to all PDU sessions created by the resident gateway 1800;
  • the third processor 1802 is further configured to:
  • the resident gateway 1800 has created the second PDU session
  • the resident gateway 1800 does not create the second PDU session.
  • the third processor 1802 is further configured to locally configure a first rule when the resident gateway 1800 has created the second PDU session, wherein the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the third communication interface 1801 is further configured to receive a first rule sent by the third function when the second PDU session is successfully created, wherein the first rule is used to forward the uplink traffic of the terminal to the second PDU session.
  • the third communication interface 1801 is further configured to send ninth information to the third function when the creation of the second PDU session fails, and the ninth information indicates that the creation of the second PDU session fails.
  • bus system 1804 is used to realize the connection and communication between these components.
  • bus system 1804 also includes a power bus, a control bus, and a status signal bus.
  • various buses are marked as bus system 1804 in Figure 18.
  • the third memory 1803 in the embodiment of the present application is configured to store various types of data to support the operation of the resident gateway 1800. Examples of such data include: any computer program for operating on the resident gateway 1800.
  • the method disclosed in the above-mentioned embodiment of the present application can be applied to the third processor 1802, or implemented by the third processor 1802.
  • the third processor 1802 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above-mentioned method can be completed by the hardware integrated logic circuit in the third processor 1802 or the instruction in the form of software.
  • the above-mentioned third processor 1802 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the third processor 1802 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • a general-purpose processor may be a microprocessor or any conventional processor, etc.
  • the steps of the disclosed method can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a storage medium, which is located in the third memory 1803.
  • the third processor 1802 reads the information in the third memory 1803 and completes the steps of the aforementioned method in combination with its hardware.
  • the resident gateway 1800 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned methods.
  • the memory (first memory 1603, second memory 1703, third memory 1803) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a ferromagnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM);
  • the magnetic surface memory can be a disk memory or a tape memory.
  • Volatile memory can be random access memory (RAM), which is used as external cache.
  • RAM random access memory
  • RAM random access memory
  • SRAM static random access memory
  • SSRAM synchronous static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • DRRAM direct memory bus random access memory
  • the memory described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the embodiment of the present application also provides an information transmission system, as shown in Figure 19, the system includes: a first function 1901, a third function 1902 and a resident gateway 1903.
  • the embodiment of the present application further provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 1603 storing a computer program, and the computer program can be executed by a first processor 1602 of the first function 1600, To complete the steps of the aforementioned first function side method.
  • a second memory 1703 storing a computer program is included, and the computer program can be executed by the second processor 1702 of the third function 1700 to complete the steps of the aforementioned third function side method.
  • a third memory 1803 storing a computer program is included, and the computer program can be executed by the third processor 1802 of the resident gateway 1800 to complete the steps of the aforementioned resident gateway side method.
  • the computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)

Abstract

La présente demande divulgue un procédé et un appareil de transmission d'informations, une première fonction, une troisième fonction, une passerelle résidentielle et un support d'enregistrement. Le procédé comprend les étapes suivantes : une première fonction reçoit de premières informations envoyées par un terminal, les premières informations étant utilisées pour demander un enregistrement associé à une tranche de réseau ; et détermine de premières informations d'aide à la sélection de tranches de réseau (NSSAI) que le terminal est autorisé à utiliser, et envoie de troisièmes informations au terminal, les troisièmes informations comprenant les premières NSSAI, les premières NSSAI étant associées à de secondes NSSAI, les secondes NSSAI comprenant des NSSAI qu'une passerelle résidentielle associée au terminal est autorisée à utiliser, le terminal communiquant avec un côté réseau au moyen de la passerelle résidentielle, et le côté réseau comprenant la première fonction.
PCT/CN2023/131806 2022-11-29 2023-11-15 Procédé et appareil de transmission d'informations, dispositif associé et support d'enregistrement WO2024114385A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211513901.1A CN118119002A (zh) 2022-11-29 2022-11-29 信息传输方法、装置、相关设备及存储介质
CN202211513901.1 2022-11-29

Publications (1)

Publication Number Publication Date
WO2024114385A1 true WO2024114385A1 (fr) 2024-06-06

Family

ID=91211144

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/131806 WO2024114385A1 (fr) 2022-11-29 2023-11-15 Procédé et appareil de transmission d'informations, dispositif associé et support d'enregistrement

Country Status (2)

Country Link
CN (1) CN118119002A (fr)
WO (1) WO2024114385A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110381548A (zh) * 2018-04-13 2019-10-25 华为技术有限公司 一种通信方法及相关设备
JP2020088473A (ja) * 2018-11-19 2020-06-04 シャープ株式会社 ユーザ装置
CN113498121A (zh) * 2020-04-07 2021-10-12 华为技术有限公司 一种通信的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110381548A (zh) * 2018-04-13 2019-10-25 华为技术有限公司 一种通信方法及相关设备
JP2020088473A (ja) * 2018-11-19 2020-06-04 シャープ株式会社 ユーザ装置
CN113498121A (zh) * 2020-04-07 2021-10-12 华为技术有限公司 一种通信的方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
BROADBAND FORUM: "SD-420 R2 5G Fixed Mobile Convergence Study", 3GPP DRAFT; SD-420R2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 9 September 2018 (2018-09-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051561326 *
ERICSSON, NOKIA, NOKIA SHANGHAI BELL: "Corrections of RG procedures", 3GPP DRAFT; S2-2003437, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Online Meeting ;20200420 - 20200423, 25 April 2020 (2020-04-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051878820 *

Also Published As

Publication number Publication date
CN118119002A (zh) 2024-05-31

Similar Documents

Publication Publication Date Title
CN109314917B (zh) 网络切片选择策略更新方法、及装置
US20060126584A1 (en) Method for user equipment selection of a packet data gateway in a wireless local network
US8665849B2 (en) Methods and systems for implementing inter-network roam, querying and attaching network
US20220272607A1 (en) Network Access Method and Communication Apparatus
EP4075866A1 (fr) Procédé et appareil de communication
US20200053126A1 (en) User plane security management in a communication system
CN114079995A (zh) 一种中继管理方法及通信装置
US20240048986A1 (en) Communication method and apparatus
WO2021138822A1 (fr) Procédé et dispositif d'acquisition d'informations d'abonnement
WO2021204277A1 (fr) Procédé, appareil et système de communication
US20220330004A1 (en) Enforcement of steering of roaming for user equipment via a proxy
WO2020042026A1 (fr) Procédé et dispositif de communication sans fil
WO2024114385A1 (fr) Procédé et appareil de transmission d'informations, dispositif associé et support d'enregistrement
WO2022268166A1 (fr) Système, procédé et appareil de communication, et premier dispositif et support d'enregistrement
WO2022022450A1 (fr) Procédé de sélection de réseau, procédé d'accès au réseau et dispositif de noeud associé
EP4021049B1 (fr) Procédé de communication sans fil et dispositif
WO2021169644A1 (fr) Procédé permettant à une passerelle domestique d'accéder à un réseau et appareil de communication
WO2024114413A1 (fr) Procédé de communication, appareil, dispositif associé et support de stockage
CN115835184A (zh) 终端设备的管理方法及装置
WO2024114431A1 (fr) Système, procédé et appareil de communication, dispositif et support de stockage
US20240171425A1 (en) Information transmission method and apparatus, information processing method and apparatus, terminal, network element and storage medium
WO2024114356A1 (fr) Procédé et appareil de transmission d'informations, et dispositif et support de stockage associés
WO2023116363A1 (fr) Procédé et appareil de traitement de session, et dispositif de communication et support de stockage
WO2023169206A1 (fr) Procédé et dispositif de vérification d'autorisation
EP4376494A1 (fr) Procédé et appareil de configuration d'informations, dispositifs associés et support de stockage associé