WO2026056808A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication

Info

Publication number
WO2026056808A1
WO2026056808A1 PCT/CN2025/119698 CN2025119698W WO2026056808A1 WO 2026056808 A1 WO2026056808 A1 WO 2026056808A1 CN 2025119698 W CN2025119698 W CN 2025119698W WO 2026056808 A1 WO2026056808 A1 WO 2026056808A1
Authority
WO
WIPO (PCT)
Prior art keywords
subnet
information
service
terminal
request message
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2025/119698
Other languages
English (en)
Chinese (zh)
Inventor
李浩然
徐艺珊
王远
韩之琳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2026056808A1 publication Critical patent/WO2026056808A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and apparatus.
  • a user equipment may access both the main network and the subnet simultaneously.
  • the radio access network (RAN) device receives a non-access stratum (NAS) message, it cannot determine whether the destination address of the NAS message is the main network or the subnet, which may cause the UE to be unable to perform the corresponding service.
  • NAS non-access stratum
  • This application provides a communication method and apparatus for determining the destination address of NAS messages in a distributed subnet scenario.
  • this application provides a communication method that can be executed by an access network device.
  • the access network device can be the access network device itself, a component within the access network device (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the functions of the access network device. This application does not specifically limit the scope of the method.
  • This method can be applied to 5G communication systems or higher, and also to non-terrestrial communication systems; this application does not specifically limit its application.
  • the execution is as follows:
  • Receive a first message from the terminal the first message including: a first indication information and a first request message, the first indication information indicating the service information requested by the terminal; obtain the destination address of the first request message according to the first indication information.
  • the first request message can be a session establishment request message, a location request message, etc., which are not specifically limited in this application.
  • the access network device learns the service information requested by the first request message.
  • the access network device stores the service information that can be executed in the main network and the subnet. Based on this, the access network device can clearly route the first request message to the main network or the subnet for processing. Based on this, the routing address of the first request message can be determined, thereby improving data processing efficiency.
  • the first indication information includes at least one of the following:
  • the service type requested by the terminal and the service parameters requested by the terminal are The service type requested by the terminal and the service parameters requested by the terminal.
  • the service type and service parameters requested by the terminal correspond to different service granularities.
  • the service type corresponds to a coarse-grained service granularity, while the service parameters correspond to a fine-grained service granularity.
  • Different terminals may request different service granularities. Based on this, the access network device can clearly define the specific service requirements of the terminal.
  • the access network device receives authorized subnet service information from a first network element for the terminal.
  • the authorized subnet service information for the terminal includes: the service type and address of the authorized subnet, or the authorized subnet service information for the terminal includes: service parameters and address of the authorized subnet.
  • the device then obtains the destination address of the first request message based on the first instruction information and the authorized subnet service information for the terminal.
  • the access network device obtains the destination address of the first request message based on the first indication information and the subnet service information authorized for the terminal, which can improve the routing efficiency of the first request message.
  • the destination address of the first request message is determined to be the address of the subnet.
  • the service information requested by the terminal indicated by the first instruction information is the same as the subnet service information that provides authorization to the terminal, it can be clearly determined that the address of the first request message is the address of the subnet.
  • the access network device receives first information from a first network element, the first information including: capability information of at least one subnet and the address of at least one subnet; and obtains the destination address of the first request message based on first instruction information and the first information.
  • the access network device obtains the destination address of the first request message based on the first indication information and the first information, which can improve the routing efficiency of the first request message.
  • the destination address of the first request message is determined to be the address of the first subnet, wherein the first subnet is one of at least one subnet.
  • the access network device obtains the destination address of the first request message based on the first indication information and the capability information of at least one subnet, which can improve the routing efficiency of the first request message.
  • the capability information of at least one subnet includes: service information supported by at least one subnet and service area information of at least one subnet.
  • access network devices can clearly identify the services supported by the subnet and route service requests supported by the subnet to the subnet for processing, thereby improving routing efficiency and preventing situations where service requests routed to the subnet are not supported by the subnet.
  • the service area of the first subnet includes the location of the terminal.
  • the first subnet can provide business services to the terminal.
  • the first information further includes: second indication information, which indicates service information to be performed by the subnet; the access network device obtains the destination address of the first request message based on the first indication information and the second indication information.
  • the judgment logic of the access network device can be reduced, and the routing efficiency of the access network device in determining the destination address of the first request message can be improved.
  • the routing destination address of the service request can be clearly identified as the subnet based on the second indication information.
  • the destination address of the first request message is determined to be the address of the first subnet, and the first subnet is one of at least one subnet.
  • Determining the destination address of the first request message based on the second and first indication information can reduce the judgment logic of the access network device and improve routing efficiency.
  • the service information supported by at least one subnet includes at least one of the following:
  • At least one subnet supports the service type and at least one subnet supports the service parameters.
  • service types and service parameters correspond to different service granularities.
  • the service granularity corresponding to service types is coarse-grained, while the service granularity corresponding to service parameters is fine-grained.
  • Different subnets may support different service granularities. Based on this, access network devices can specify the specific service granularity that a subnet can execute in order to improve the routing efficiency of service requests.
  • the subnet address is indicated by one of the following information:
  • the first request message is a NAS message.
  • access network devices can clearly define the routing address of NAS messages.
  • this application provides a communication method that can be executed through a first network element.
  • this first network element is used for access management of the management center network (i.e., the main network) and also for registering information about subnet network elements.
  • This first network element can be the first network element itself, a component within the first network element (e.g., a processor, chip, or chip system), or a logical module or software that implements all or part of the functions of the first network element.
  • This application does not specifically limit the scope here.
  • the execution is as follows:
  • Obtain authorized subnet service information for the terminal which includes: the service type and subnet address provided by the authorized subnet; or, the authorized subnet service information for the terminal includes: service parameters and subnet address provided by the authorized subnet.
  • access network devices can refer to the subnet service information provided to the terminal for authorization to determine the destination address of the terminal request message, thereby improving the routing efficiency of the terminal request message.
  • the first network element receives capability information of at least one subnet, the capability information of the at least one subnet including: service information supported by at least one subnet and service area information of at least one subnet; receives subscription information, the subscription information including: subnet service information subscribed by the terminal and subnet identifier subscribed by the terminal; and determines authorized subnet service information to be provided to the terminal based on the subnet capability information, the subscription information and the terminal's location information.
  • the subnet service information authorized to the terminal determined by the first network element based on subnet capability information, contract information, and terminal location information is more reliable.
  • the service information supported by at least one subnet includes at least one of the following: the service type supported by at least one subnet, and the service parameters supported by at least one subnet.
  • this application provides a communication method that can be executed through a first network element.
  • this first network element is used for access management of the management center network (i.e., the main network) and also registers information about subnet network elements.
  • This first network element can be the first network element itself, a component within the first network element (e.g., a processor, chip, or chip system), or a logical module or software that implements all or part of the functions of the first network element.
  • This application does not specifically limit the scope here.
  • the execution is as follows:
  • the first network element can determine the destination address of the first request message, generate first information to determine the destination address of the first request message, and send the first information to the access network device. This allows the access network device to quickly route the first request message to its destination address when the terminal subsequently carries a request message of the same type as the first request message.
  • the first network element receives capability information of at least one subnet, the capability information of the at least one subnet including: service information supported by at least one subnet and service area information of at least one subnet; and determines the destination address of the first request message based on the first instruction information, the location information of the terminal, and the capability information of at least one subnet.
  • the address of the first request message determined by the first network element based on the first indication information, the location information of the terminal, and the capability information of at least one subnet is more reliable.
  • the first network element receives subscription information, which includes: subnet service information subscribed by the terminal and subnet identifier subscribed by the terminal; and determines the destination address of the first request message based on the first instruction information, the terminal's location information, the subscription information, and the capability information of at least one subnet.
  • the address of the first request message determined by the first network element based on the first instruction information, the terminal's location information, the subscription information, and the capability information of at least one subnet is more reliable.
  • the first network element sends first information to the access network device, the first information including: capability information of at least one subnet and the address of at least one subnet.
  • the first information further includes: second indication information, which indicates service information performed by the subnet.
  • the service information supported by at least one subnet includes at least one of the following:
  • At least one subnet supports the service type and at least one subnet supports the service parameters.
  • the subnet address is indicated by one of the following information:
  • the first request message is a NAS message.
  • the first indication information includes at least one of the following:
  • the service type requested by the terminal and the service parameters requested by the terminal are The service type requested by the terminal and the service parameters requested by the terminal.
  • this application provides a communication method that can be executed by a terminal.
  • the terminal can be the access network device itself, a component within the terminal (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the terminal's functions. This application does not specifically limit the method.
  • the execution is as follows:
  • Determine the first message which includes: a first instruction message and a first request message, wherein the first instruction message indicates the service information requested by the terminal; and send the first message.
  • the first indication information includes at least one of the following:
  • the service type requested by the terminal and the service parameters requested by the terminal are The service type requested by the terminal and the service parameters requested by the terminal.
  • the first request message is a NAS message.
  • this application provides a communication method that can be executed by an access network device.
  • the access network device can be the access network device itself, a component within the access network device (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the functions of the access network device. This application does not specifically limit the scope here.
  • the execution is as follows:
  • the first message includes a first identifier and a first request message.
  • the first identifier is an identity identifier assigned to the terminal by the second network element, and the second network element is the access management network element of the subnet. Determine the destination address of the first request message as the address of the second network element based on the first identifier.
  • This application improves routing efficiency and data processing efficiency by using different temporary identifiers (i.e., the first identifier) so that access network devices can select the correct first request message routing address without changing the logic of selecting network elements.
  • the first request message is a NAS message.
  • this application provides a communication method that can be executed by a terminal.
  • the terminal can be the access network device itself, a component within the terminal (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the terminal's functions. This application does not specifically limit the method.
  • the execution is as follows:
  • Determine the first message which includes: a first identifier and a first request message, wherein the first identifier is an identity identifier assigned to the terminal by the second network element, and the second network element is the access management network element of the subnet; send the first message.
  • the first request message is a NAS message.
  • embodiments of this application provide a communication device, which can be a terminal, a first network element, or an access network device.
  • the communication device has the functions to implement the first to sixth aspects described above.
  • the communication device includes modules, units, or means that perform the steps involved in the first to sixth aspects. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.
  • the communication device includes a processing unit and a transceiver unit.
  • the transceiver unit can be used to send and receive signals to enable communication between the communication device and other devices; for example, the transceiver unit is used to receive a first message.
  • the processing unit can be used to perform some internal operations of the communication device.
  • the transceiver unit can be called an input/output unit, a communication unit, etc., and can be a transceiver; the processing unit can be a processor.
  • the transceiver unit can be an input/output interface, input/output circuit, or input/output pins, etc., and can also be called an interface, communication interface, or interface circuit, etc.;
  • the processing unit can be a processor, processing circuit, or logic circuit, etc.
  • the communication device includes a processor and may further include a transceiver for transmitting and receiving signals.
  • the processor executes program instructions to perform the methods in any of the possible designs or implementations of the first to sixth aspects described above.
  • the communication device may also include one or more memories coupled to the processor, which may store necessary computer programs or instructions for implementing the functions described in the first to sixth aspects.
  • the processor can execute the computer programs or instructions stored in the memory, causing the communication device to implement the methods in any of the possible designs or implementations of the first to sixth aspects described above when the computer programs or instructions are executed.
  • the communication device includes a processor that can be coupled to a memory.
  • the memory can store necessary computer programs or instructions for implementing the functions described in the first to sixth aspects above.
  • the processor can execute the computer programs or instructions stored in the memory, causing the communication device to implement the methods in any possible design or implementation of the first to sixth aspects above when the computer programs or instructions are executed.
  • the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and to perform the methods in any possible design or implementation of the first to sixth aspects described above.
  • the processor can be implemented in hardware or software.
  • the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory.
  • the processor can be one or more processors, and one or more memories.
  • the memory can be integrated with the processor, or the memory and processor can be separate. In specific implementations, the memory can be integrated with the processor on the same chip, or it can be set on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.
  • embodiments of this application provide a communication system including the aforementioned terminal, first network element, and access network device.
  • the access network device can be used to execute the methods of the first or fifth aspect
  • the first network element can be used to execute the methods of the second or third aspect
  • the terminal can be used to execute the methods of the fourth or sixth aspect.
  • processes executed interactively by multiple devices or network elements there may be processes executed interactively by multiple devices or network elements; the corresponding processes cannot be executed by a single device or network element. Instead, they are mainly executed through the interaction of corresponding devices or network elements, which will not be elaborated upon here.
  • this application provides a chip system including a processor and potentially a memory for implementing the methods described in the first to sixth aspects.
  • the chip system may be composed of chips or may include chips and other discrete devices.
  • this application also provides a computer-readable storage medium storing computer-readable instructions that, when executed on a computer, cause the computer to perform the methods described in the first to sixth aspects.
  • this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods of the embodiments of the first to sixth aspects described above.
  • Figure 1 shows a schematic diagram of a distributed subnet system provided in an embodiment of this application
  • FIG. 2 shows a flowchart of a communication method provided in an embodiment of this application
  • FIG. 3 shows a flowchart of a communication method provided in an embodiment of this application
  • Figure 4 shows a flowchart of a communication method provided in an embodiment of this application
  • Figure 5 shows a flowchart of a communication method provided in an embodiment of this application
  • Figure 6 shows a flowchart of a communication method provided in an embodiment of this application.
  • Figure 7 shows a schematic diagram of the communication device provided in an embodiment of this application.
  • Figure 8 shows a schematic diagram of the communication device provided in an embodiment of this application.
  • Figure 9 shows a schematic diagram of the structure of the communication device provided in an embodiment of this application.
  • At least one means one or more, and “more than one” means two or more.
  • “And/or” describes the relationship between related objects, indicating that three relationships can exist.
  • a and/or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural.
  • the character “/” generally indicates an “or” relationship between the preceding and following related objects; in the formulas of this application, the character “/” indicates a “division” relationship between the preceding and following related objects.
  • “Including at least one of A, B, and C” can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.
  • Figure 1 illustrates a distributed subnet system architecture, in which the core network is divided into a main network and subnets.
  • the main network also known as the central network, is the operator's central network, possessing complete core network functions and providing all management services to terminals.
  • the subnets are core network subnets deployed in a distributed manner by the operator, capable of interacting with the main network and calling its functions to manage terminals.
  • the distributed subnet system allows for on-demand updates of functional network elements within the subnets, thereby providing specific services to users.
  • This architecture also includes terminals and access network equipment. Terminals can request services from the main network or subnets through the access network equipment. This application does not specifically limit the number of main networks and subnets in the distributed subnet system architecture.
  • Figure 1 uses one main network and two subnets as an example for illustration.
  • a terminal can be a device capable of receiving scheduling and instruction information from access network equipment, providing voice and/or data connectivity to users, or a handheld device with wireless connectivity, or other processing devices connected to a wireless modem.
  • the terminal can communicate with one or more core networks or the Internet via a radio access network (RAN).
  • RAN radio access network
  • a terminal can be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device.
  • Terminals can also be referred to as subscriber units (SS), subscriber stations (MS), mobile stations (MS), remote stations (AP), access points (AP), remote terminals (AP), access terminals (AP), user agents (MS), customer premises equipment (CPE), terminals (Terminal), user equipment (UE), mobile terminals (MT), etc.
  • Terminals can also be wearable devices.
  • Terminals can also be devices in next-generation communication systems. For example, terminals in 5G networks or future evolved public land mobile networks (PLMNs), and terminals in NR communication systems.
  • terminals can include: mobile phones, tablets, laptops, PDAs, customer-premises equipment (CPE), mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle equipment (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, and industrial control devices.
  • CPE customer-premises equipment
  • MIDs mobile internet devices
  • wearable devices such as smartwatches, smart bracelets, pedometers, etc.
  • in-vehicle equipment e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.
  • VR virtual reality
  • AR augmented reality
  • Wireless terminals in various fields including smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters), smart robots, workshop equipment, wireless terminals in self-driving, remote medical surgery, smart grids, transportation safety, smart cities, smart homes, and flying equipment (e.g., smart robots, hot air balloons, drones, airplanes), can also be used.
  • Terminals can also be other devices with terminal functions; for example, a terminal can be a device that functions as a terminal in D2D communication.
  • Access network equipment is an entity on the network side used to transmit or receive signals. Examples include transmission reception points (TRPs) and gNBs.
  • Network equipment can be an access point (AP) in a wireless local area network (WLAN), a base transceiver station (BTS) in a global system for mobile communication (GSM) or code division multiple access (CDMA), a base station (nodeB, NB) in wideband code division multiple access (WCDMA), or an evolved node B (eNB or eNodeB) in long-term evolution (LTE).
  • WLAN wireless local area network
  • BTS base transceiver station
  • GSM global system for mobile communication
  • CDMA code division multiple access
  • nodeB, NB base station
  • WCDMA wideband code division multiple access
  • eNB or eNodeB evolved node B in long-term evolution
  • Network equipment can also be a relay station or access point, or in-vehicle equipment, wearable devices, and network equipment in 5G networks, or in future evolved PLMNs, or gNodeB/gNB devices in NR systems.
  • a gNB may include a CU and a DU.
  • the CU implements some of the gNB's functions, and the DU implements others.
  • the CU handles non-real-time protocols and services, such as radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP).
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • the DU handles physical layer protocols and real-time services, such as radio link control (RLC), medium access control (MAC), and physical (PHY) layers.
  • RLC radio link control
  • MAC medium access control
  • PHY physical
  • the gNB may also include an active antenna unit (AAU).
  • AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since information from the RRC layer ultimately becomes information from the PHY layer, or is derived from information from the PHY layer... Therefore, under this architecture, higher-layer signaling (e.g., RRC layer signaling) can also be considered to be sent by the DU, or by the DU and AAU.
  • the network device can be one or more of the following: CU node, DU node, and AAU node.
  • the CU can be a network device in the radio access network (RAN), or a network device in the core network (CN); this application does not limit this.
  • RAN radio access network
  • CN core network
  • the network device provides services to a cell, and the terminal communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell.
  • the cell can be the cell corresponding to the network device (e.g., a base station).
  • the cell can belong to a macro base station or to a base station corresponding to a small cell.
  • a small cell can include: a metro cell, a micro cell, a pico cell, a femto cell, etc. Because small cells have small coverage areas and low transmission power, they can provide high-speed data transmission services.
  • the network device can be any other device that provides wireless communication functionality to the terminal.
  • CU can also be called O-CU (open CU)
  • DU can also be called O-DU
  • CU-CP can also be called O-CU-CP
  • CU-UP can also be called O-CU-UP
  • RU can also be called O-RU.
  • this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through a software module, a hardware module, or a combination of software and hardware modules.
  • the large network includes network functions such as network service mesh controller (NSMC), session management, user plane, policy control, network slice selection, network slice-specific authentication and authorization, network repository, network data analysis, unified data management, unified data storage, authentication service, network capability opening, terminal wireless capability management, binding support, application functions, and mobility management (MM). These functions are not listed here but are illustrated by example only.
  • NSC network service mesh controller
  • session management user plane
  • policy control policy control
  • network slice selection network slice-specific authentication and authorization
  • network repository network data analysis
  • unified data management unified data storage
  • authentication service network capability opening
  • terminal wireless capability management binding support
  • application functions application functions
  • MM mobility management
  • the NSMC is responsible for managing subnet capabilities and serves as the unified interface between the main network and subnets, capable of collecting subnet capabilities. It also possesses main network element discovery capabilities, enabling it to discover other functional network elements within the main network.
  • the NSMC along with the MM, is equivalent to the access and mobility management function (AMF), primarily used for terminal attachment, mobility management, and tracking area update procedures in mobile networks. Furthermore, it supports NAS signaling and its security, as well as the management of tracking area (TA) lists.
  • AMF access and mobility management function
  • TA tracking area
  • Session management functions are primarily used for session management in mobile networks, such as session creation, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to terminals and selecting user plane functions that provide packet forwarding capabilities.
  • IP Internet Protocol
  • the session management function can be a session management function (SMF).
  • SMF session management function
  • the session management function may still be called an SMF, or it may have other names; this application is not limited to these.
  • MMF multicast/broadcast session management network element, which can be a multicast/broadcast-session management function (MB-SMF), primarily used for session management in mobile networks, such as session creation, modification, and release.
  • MMF multicast/broadcast-session management function
  • User plane functions are primarily used for processing user packets, such as forwarding and billing.
  • user plane functions can be user plane functions (UPFs).
  • user plane functions may still be called UPFs, or they may have other names; this application does not limit this.
  • Policy control functions include policy control functions, charging policy control functions, QoS control, etc.
  • policy control functions can be policy control functions (PCF).
  • PCF policy control functions
  • policy control functions may still be called PCF, or they may have other names; this application is not limited to these.
  • the network slice selection function is mainly used to select a suitable network slice for the terminal's services.
  • the network slice selection function can be called the network slice selection function (NSSF).
  • the network slice selection function may still be called NSSF, or it may have other names; this application is not limited to these names.
  • the network repository function is primarily used to provide registration and discovery of network functions or the services provided by network functions.
  • the network repository function may be a network repository function (NRF).
  • NRF network repository function
  • future communication systems the network repository function may still be called NRF, or it may have other names; this application is not limited to any particular name.
  • the unified data management function is mainly used to manage the subscription information of terminals.
  • the unified data management function can be a unified data management (UDM) function.
  • the unified data management function may still be a UDM function, or it may have other names. This application is not limited to this.
  • the unified data storage function is primarily used to store structured data information, including subscription information, policy information, and network data or service data with standard format definitions.
  • the unified data storage function can be a unified data repository (UDR) function.
  • the unified data storage function may still be a UDR function, or it may have other names; this application is not limited to these.
  • the authentication service function is mainly used for secure authentication of terminals.
  • the authentication service function can be an authentication server function (AUSF).
  • AUSF authentication server function
  • the authentication service function may still be called AUSF, or it may have other names; this application is not limited to any particular name.
  • NEF Network capability exposure
  • 5G communication systems NEF may be used.
  • NEF may still be used, or it may have other names; this application does not limit this.
  • Subnets may include distributed network service mesh (D-NSM), SMF, session management, network repository, etc.
  • D-NSM distributed network service mesh
  • SMF Session Management Function
  • the network functions included in different subnets may be the same or different; this is not specifically limited here.
  • Subnets can deploy the required network functions based on specific applications.
  • D-NSM is responsible for network element management within the subnet and has network element discovery capabilities, enabling it to discover other network elements within the subnet.
  • subnet 1 includes D-NSM1, SMF1, and UPF1.
  • Subnet 2 includes D-NSM2 and location management function (LMF). This is only an illustrative example and does not specifically limit the categories of network functions in a subnet; other network functions may also be included, which are not specifically limited here.
  • D-NSM is used for subnet element capability management and processing terminal NAS signaling.
  • D-NSM can register and update subnet capability information with the main network NSMC.
  • a subnet dynamically deploys network functions (e.g., adding new network functions or updating services supported by network functions), it registers with D-NSM, enabling D-NSM to obtain the subnet's capability information.
  • D-NSM can interpret the NAS signaling and execute the corresponding services.
  • the functions in the embodiments of this application may also be referred to as network elements, network functions, functional entities, devices, etc.
  • access and mobility management functions may also be referred to as access and mobility management network elements, or access and mobility management network functions, or access and mobility management functional entities, etc.
  • the names of each function are not limited in this application. Those skilled in the art can replace the names of the above functions with other names to perform the same function, and all such replacements are within the scope of protection of this application.
  • the UE's session establishment request message (such as NAS message) is directly routed to the AMF for processing.
  • the RAN cannot determine whether the session establishment request message should be sent to the main network or the subnet. This may lead to incorrect routing of the session establishment request message, causing the UE to be unable to execute the corresponding service.
  • the access management network element corresponding to the subnet in the distributed subnet system is used for access management of the subnet and also for discovering network elements within the subnet; for example, D-NSM.
  • D-NSM network elements within the subnet
  • specific applications may require data interaction with other network elements, such as UDM and UPF, which are not specifically limited here.
  • the first message sent by the terminal to the access network device includes first indication information indicating the service information requested by the terminal and a first request message. After obtaining authorized subnet service information for the terminal from the first network element, the access network device determines the destination address of the first request message based on the first indication information, as shown in Figures 2 and 3 below.
  • the first message sent by the terminal to the access network device includes first indication information indicating the service information requested by the terminal and a first request message.
  • the access network device determines the destination address of the first request message based on stored subnet capability information and the first indication information, as shown in Figure 4 below.
  • the terminal sends the first request message to the access device it carries a first identifier allocated by the subnet.
  • the access network device determines the destination address of the first request message based on the first identifier, as shown in Figures 5 and 6 below.
  • the execution logic of each embodiment has been briefly described above; the following is a detailed description.
  • Step 201 The first network element obtains the subnet service information that provides authorization to the terminal.
  • the authorized subnet service information provided to the terminal includes: the service type and subnet address provided by the authorized subnet, or the authorized subnet service information provided to the terminal includes: the service parameters and subnet address provided by the authorized subnet.
  • the service types provided by the authorized subnet for the terminal can be understood as the subnet service types authorized for the terminal.
  • the service types provided by the authorized subnet for the terminal indicate the services supported by the subnet, such as session management, location management, perception management, and data computing services. These are merely illustrative examples and not specific limitations.
  • service types can be further distinguished according to the real-time nature and accuracy of the service results. For example, in perception management services, the creation of detailed maps requires high accuracy, while the positioning of target locations requires high real-time performance. The processing of detailed maps can be set as one type of perception management service, and the positioning of target locations can be set as another type of perception service. This is merely illustrative and not specific limitations on how to set service types.
  • Service types can be represented by specific identifiers; for example, session management services can use the identifier 0x0001. This is merely illustrative and not specific limitations on how to identify service types.
  • the subnet service information provided to the terminal for authorization includes the Session Management Service and the identifier of Subnet 1.
  • the Session Management Service and the address of D-NSM1 i.e., the address of D-NSM in Subnet 1.
  • the first network element can request authorized subnet service information for the terminal from other distributed subnet systems.
  • distributed subnet system 1 includes NSMC1, subnet A, subnet B, and subnet C.
  • Distributed subnet system 2 includes NSMC2, subnet A, subnet B, and subnet C. If NSMC1 has already obtained information 1 (i.e., authorized subnet service information for the terminal), then NSMC2 can request information 1 from NSMC1 and use this information 1 as the authorized subnet service information for the terminal. It can also obtain the authorized subnet service information for the terminal by adjusting information 1. This is merely an example and not a specific limitation.
  • the first network element determines the authorized subnet service information to provide to the terminal based on the subnet's capability information, the terminal's subscription information, and the terminal's location information.
  • the subnet's capability information includes the services supported by the subnet (specifically, the services that network elements in the subnet can support) and the subnet's service area information (e.g., geographical location, cell identifier, etc.). Service information can be understood as service type and/or service parameters.
  • the terminal's subscription information includes the subnet service information subscribed to by the terminal and the subnet identifier. For example, terminal 1 subscribes to the session management service of subnet 1 and the location service of subnet 2.
  • the terminal's location information indicates the terminal's current location or its location within a preset time period. For example, if the preset time period is 10 minutes, the terminal 1's location information includes its location 10 minutes before and 10 minutes after the current time.
  • the terminal's location information can be indicated by the cell identifier, tracking area (TA), and the terminal's geographic coordinates; this is only illustrative and not specifically limited.
  • a first network element can receive capability information of at least one subnet from an access management network element (e.g., D-NSM) corresponding to at least one subnet.
  • the capability information of the at least one subnet includes: service information supported by the at least one subnet and service area information of the at least one subnet.
  • the first network element can actively request the capability information of the at least one subnet.
  • the access management network element corresponding to the subnet can also actively send (or register) the capability information of the subnet to the first network element; this application is not specifically limited herein.
  • subnet A can send its capability information to NSMC1
  • subnet B can send its capability information to NSMC1.
  • NSMC1 can also obtain capability information of at least one subnet from other distributed subnet systems.
  • distributed subnet system 1 and distributed subnet system 2 include subnet A, subnet B, and subnet C. Since the subnets in distributed subnet 2 have already sent their capability information to NSMC2 in distributed subnet system 2, NSMC1 in distributed subnet system 1 can directly request the capability information of subnets A, B, and C from NSMC2 in distributed subnet system 2. This is merely an illustrative example and does not specifically limit how the first network element obtains the subnet capability information.
  • the subnet's capability information usually includes the subnet's address information.
  • the first network element may receive subscription information from a data management network element (e.g., UDM) or policy information from a policy management network element (e.g., PCF).
  • the subscription information or policy information includes: subnet service information subscribed to by the terminal and the subnet identifier subscribed to by the terminal.
  • the first network element may proactively request subscription information from the data management network element or the policy management network element.
  • the data management network element or the policy management network element may also proactively send subscription information to the first network element. This application does not specifically limit how the subscription information is obtained.
  • the first network element may request the terminal's location information from the location management network element (e.g., the location management function (LMF)).
  • the terminal may also actively report its current location information, for example, by reporting its location through a registration message or other messages, which are not specifically limited here.
  • a distributed subnet system 1 includes a main network 1, subnet A, subnet B, and subnet C.
  • the first network element in main network 1 obtains the capability information of subnets A, B, and C.
  • Subnet A supports session management and location management services, and its service area includes cells 1 and 2.
  • Subnet B supports session management and sensing management services, and its service area includes cells 2 and 3.
  • Subnet C supports sensing management services, and its service area includes cell 4.
  • the terminal's subscription information includes the terminal's subscription to subnet A's session management and location management services, and subnet B's session management service.
  • the terminal is currently within the coverage area of cell 1. Since subnet A's service area includes cell 1, and the terminal's subscription information includes subnet A's service information, the authorized subnet service information for the terminal can be subnet A's session management and location management services. This is only an illustrative example.
  • the subnet service information authorized to the terminal is not fixed and needs to be updated periodically. For example, since the terminal's location information is not fixed, a change in the terminal's location can trigger an update of the subnet service information authorized to the terminal.
  • the first network element can periodically obtain the terminal's location and proactively update the subnet service information authorized to the terminal based on the change in the terminal's location. Or, the first network element updates the subnet service information authorized to the terminal when the subnet's capability information or the terminal's subscription information is updated. No specific limitations are specified here.
  • the aforementioned terminals refer to all terminals in the distributed subnet system, and the authorized subnet service information is obtained for each terminal in the distributed subnet system.
  • the aforementioned terminals may refer to one or more terminals in a terminal group, and providing authorized subnet service information to a terminal is equivalent to providing authorized subnet service information to the terminal group.
  • Step 202 The first network element sends subnet service information authorized for the terminal to the access network device.
  • the first network element can send subnet service information authorized for the terminal to the access network device through a terminal registration acceptance message, or it can send it through other messages, which are not specifically limited here.
  • the access network device can determine the destination address of the subnet service requested by the terminal by referring to the type of subnet service information authorized for the terminal.
  • Step 203 The access network device saves the subnet service information authorized for the terminal.
  • the access network device may store the subnet service information that provides authorization to the terminal in the terminal's context information, or it may store the subnet service information that provides authorization to the terminal separately. This application does not specifically limit this.
  • the authorized subnet service information for the terminal is usually multiple.
  • Step 204 The terminal sends a first message to the access network device.
  • the first message includes: a first indication message and a first request message.
  • the first indication message indicates the service information requested by the terminal.
  • the first message can reuse an existing AN message.
  • an AN message includes two parts: AN parameters and a first request message.
  • the AN parameters usually include terminal identifiers and PLMN IDs, allowing access devices to directly route to the existing AMF in the core network.
  • first indication information can be added to the AN parameters, thus the AN parameters also include the first indication information.
  • the first indication information can be added to the AN message, then the AN message includes the AN parameters, the first indication information, and the first request message.
  • the first request message can be a session establishment request message, a location request message, etc., and is not specifically limited here.
  • the first request message is a NAS message.
  • the first message can also be a new type of message that is associated with the routing of the first request message, which is not specifically limited here.
  • the first indication information may include at least one of the following: the service type requested by the terminal, and the service parameters requested by the terminal.
  • the service type requested by the terminal indicates the service requested by the terminal, such as session management service, location management service, perception management service, data computing service, etc., which are only illustrative examples and not specifically limited here.
  • the service type can be further distinguished according to the real-time nature and accuracy of the service result. For example, in perception management, the creation of a detailed map requires high accuracy, while the positioning of the target location requires high real-time performance.
  • the processing of the detailed map can be set as one type of perception management service, and the positioning of the target location as another type of perception service. This is only illustrative example and does not specifically limit how the service type is set.
  • the service type requested by the terminal can be a specific service, such as building a detailed map of region A, etc., which are only illustrative examples here.
  • the service parameters requested by the terminal can be understood as the subnet service parameters that the terminal is pre-using.
  • the service parameters requested by the terminal indicate the processing parameters for the service the terminal is requesting to execute.
  • the terminal may request the slice parameter S-NSSAI 1 for session management, etc. This is only an example and is not a specific limitation.
  • the service type and service parameters requested by the terminal correspond to different service granularities.
  • the service type corresponds to a coarse-grained service granularity, while the service parameters correspond to a fine-grained service granularity.
  • Different terminals may request different service granularities. Based on this, the access network device can clearly define the specific service requirements of the terminal.
  • Step 205 The access network device obtains the destination address of the first request message according to the first instruction information.
  • the access network device obtains the service information requested by the terminal's first request message based on the first indication information. If the service information corresponds to the main network or subnet, the access network device can directly determine the destination address of the first request message based on this correspondence. For example, the session management service corresponds to the main network, the location management service corresponds to subnet 1, and the data computing service corresponds to subnet 2. If the first indication information indicates the location management service, then the access network device can determine the destination address of the first request message as subnet 1. Alternatively, the access network device stores service information executable by the main network and subnets, and determines the destination address of the first request message based on this stored information. For example, the main network executes the session management service, and subnet 1 executes the location management service.
  • the access network device can determine the destination address of the first request message as the main network. Alternatively, the access network device pre-configures routing rules for different service information between itself and the main network and subnets. For example, the session management service is processed by the main network, and the location management service is processed by subnet 1. After receiving the first indication information indicating the session management service, the access network device routes the first request message to the main network for processing. This is only an example and is not a specific limitation.
  • the access network device can obtain the destination address of the first request message based on the first indication information and the subnet service information that provides authorization to the terminal. This can improve the routing efficiency of the first request message.
  • the destination address of the first request message is determined to be the address of the subnet.
  • terminal 1 carries AN parameters and a session establishment request message in the AN message.
  • the AN parameters include terminal 1's identity identifier (e.g., a subscription concealed identifier (SUCI) or 5G-GUTI (5G globally unique temporary identity)) and first indication information, which indicates that the service type requested by terminal 1 is session management service.
  • the access device queries the subnet service information stored by the access device that authorizes terminal 1 based on terminal 1's identity identifier. If terminal 1 is authorized to use subnet X to perform session management service, the access network device can route the session establishment request message to the D-NSM of subnet X for processing. If the access device does not find any subnet service information that authorizes terminal 1 based on terminal 1's identity identifier, it routes the session request message to the main network for processing.
  • SUCI subscription concealed identifier
  • 5G-GUTI 5G globally unique temporary identity
  • terminal 1 carries AN parameters and a session establishment request message in the AN message.
  • the AN parameters include the identity identifier of terminal 1 (e.g., SUCI or 5G-GUTI) and first indication information.
  • the first indication information indicates that the service type requested by terminal 1 is session management service and the service parameter is slice S-NSSAI 1.
  • the access device queries the subnet service information authorized for terminal 1 stored in the access device according to the identity identifier of terminal 1. If terminal 1 is authorized to use subnet X to perform session management service, but subnet X does not support slice S-NSSAI 1, or terminal 1 is not authorized to use slice S-NSSAI 1 of subnet X, then the session request message is routed to the main network for processing.
  • the access network device can store the correspondence between the subnet identifier and the access management network element of the subnet.
  • subnet identifier 1 corresponds to D-NSM1
  • subnet identifier 2 corresponds to D-NSM2
  • one subnet identifier can correspond to the address of one or more access management network elements of the subnet. This is not specifically limited here.
  • the access device queries the subnet service information stored by the access device that authorizes terminal 1 based on the identity identifier of terminal 1.
  • the identifier of subnet X corresponds to D-NSM-X1 and D-NSM-X2.
  • the access network device can randomly select D-NSM-X1 and D-NSM-X2 as the routing address for the session request message. If the subnet address is indicated by the address of the access management network element corresponding to the subnet, the access network device can directly send a session establishment request message to the address of the access management network element corresponding to the subnet.
  • the access network device learns the service information requested by the first request message.
  • the access network device stores subnet service information that provides authorization for the terminal. Based on this, the access network device can clearly route the first request message to the main network or subnet for processing. Based on this, the routing address of the first request message can be determined, thereby improving data processing efficiency.
  • Step 301 D-NSM sends a capability information registration request from the subnet to NSMC.
  • this capability registration request can be proactively reported by the D-NSM of each subnet to the NSMC after the initial deployment of the distributed subnet. Alternatively, it can be proactively reported by the D-NSM of each subnet to the NSMC after network functions (or network elements) are added or updated within the subnet after the distributed subnet deployment is completed.
  • the subnet capability information includes: service information supported by the subnet (specifically, the service information that network elements in the subnet can support) and service area information of the subnet (e.g., geographical location, cell identifier, etc.).
  • the subnet capability information can be understood in detail with reference to the description in step 201 above, and will not be repeated here.
  • SMF control plane service processing for session management
  • UPF user plane service processing for session management
  • the main network can choose to route session management-related services to the subnet for processing.
  • the subnet reports its session management capabilities, it can also further report supported slices, DNN, and other information for the main network to more accurately manage the subnet capabilities.
  • Step 302 NSMC saves the subnet capability information and sends a registration request acceptance message to the subnet.
  • Step 303 The UE sends a UE registration request to the NSMC through the RAN device.
  • Step 304 NSMC selects an authentication server function (AUSF) that meets the requirements to perform the security authentication process.
  • AUSF authentication server function
  • Step 305 Perform the security authentication process.
  • Step 306 NSMC sends the UE registration request and the UE authentication result to MM.
  • Step 307 MM sends a UE registration acceptance response message to NSMC.
  • Steps 303 to 307 above can be understood by referring to the existing UE registration and security authentication process, and will not be elaborated here.
  • NSMC is equivalent to performing the operations performed by AMF in the existing security authentication process.
  • MM is equivalent to performing the operations performed by AMF in the existing security authentication process. MM can save the UE's context, allocate a registration area for the UE, and send a registration acceptance response message.
  • Step 308 NSMC requests the UE's subscription data from UDM.
  • the UE's subscription information includes the subnet service information subscribed to by the UE and the subnet identifier subscribed to by the UE. Refer to the description in step 201 above for a detailed understanding of the terminal's subscription data; it will not be repeated here.
  • Step 309 The NSMC determines the authorized subnet service information to be provided to the UE based on the subnet capability information, the UE's subscription data, and the UE's location information.
  • step 201 Please refer to the description in step 201 above for further understanding; it will not be repeated here.
  • Step 310 NSMC sends a UE registration acceptance message to the RAN device, which includes authorized subnet service information for the UE.
  • the RAN device stores information about the subnet services authorized by the UE.
  • Step 311 The RAN device sends a UE registration acceptance message to the UE.
  • the UE registration acceptance message in step 311 does not include subnet service information authorized for the UE.
  • Step 312 The UE sends an AN message (equivalent to the first message) to the RAN device.
  • the AN message includes: a first indication information and a session establishment request message (i.e., a first request message).
  • the first indication information indicates that the terminal requests session services.
  • step 204 can be used for understanding, and will not be repeated here.
  • Step 313 The RAN device determines the destination address of the session establishment request message based on the first indication information and the subnet service information authorized for the UE.
  • step 205 For details on how to determine the destination address of the session establishment request message, please refer to the description in step 205 above, which will not be repeated here.
  • the RAN device determines that the destination address is a subnet, then proceed with step 314 below.
  • Step 314 The RAN device sends a session establishment request message to the D-NSM.
  • Step 315 D-NSM selects network elements in the subnet to perform subsequent procedures for session establishment.
  • Step 315 can be understood by referring to the existing session establishment process, and will not be elaborated here.
  • steps 301 and 302 above can be performed before step 309, and this application does not specifically limit the execution order.
  • the data interaction between the terminal, access network equipment, the first network element, and the access management network element corresponding to the first subnet is illustrated as an example.
  • This application does not limit the number of subnets and main networks in a distributed subnet system; only one is used as an example here.
  • the execution is as follows:
  • Step 401 The terminal sends a first message to the access network device.
  • the first message includes: a first indication information and a first request message.
  • the first indication information indicates the service information requested by the terminal.
  • step 204 You can refer to step 204 above for understanding, which will not be repeated here.
  • Step 402 The access network device sends a second message to the first network element.
  • the second message includes a first indication message and a first request message.
  • step 402 is executed when the access device first receives the first request message, or when the access network device cannot determine the destination address of the first request message.
  • Step 403 The first network element determines the destination address of the first request message based on the first instruction information.
  • the first network element determines the destination address of the first request message based on the first indication information, the terminal's location information, and the capability information of at least one subnet. For example, the first network element may receive capability information of at least one subnet from the access management network element corresponding to at least one subnet.
  • the capability information of the at least one subnet includes: service information supported by at least one subnet and service area information of at least one subnet.
  • the first network element may actively request the capability information of at least one subnet from the at least one subnet.
  • the access management network element corresponding to the subnet may also actively send (or register) the subnet's capability information to the first network element; this is not specifically limited herein.
  • the first network element may request the terminal's location information from the location management network element (e.g., LMF).
  • the terminal may also actively report its current location information, for example, by reporting its location through a registration message or other messages; this is not specifically limited herein.
  • the first network element can indirectly determine the terminal's location information based on the location of the access network device.
  • a distributed subnet system 1 includes a main network 1, subnet A, subnet B, and subnet C.
  • the first network element in main network 1 obtains the capability information of subnet A, subnet B, and subnet C.
  • Subnet A supports session management services and location management services, and its service area includes cell 1 and cell 2.
  • Subnet B supports session management services and sensing management services, and its service area includes cell 2 and cell 3.
  • Subnet C supports sensing management services, and its service area includes cell 4.
  • the terminal is currently within the coverage area of cell 1.
  • subnet A Since the service area of subnet A includes cell 1, and the first indication information indicates that the service information requested by terminal 1 is location management service, subnet A can provide services to terminal 1. Based on this, the first network element in main network 1 can use subnet A as the destination address of the first request message. This is only an example.
  • the first network element determines the destination address of the first request message based on the first indication information, the terminal's location information, subscription information, and the capability information of at least one subnet.
  • the first network element may receive subscription information from a data management network element (e.g., UDM) or a policy management network element (e.g., PCF), the subscription information including: subnet service information subscribed to by the terminal and the subnet identifier subscribed to by the terminal.
  • the first network element may proactively request subscription information from the data management network element or the policy management network element.
  • the data management network element or the policy management network element may also proactively send subscription information to the first network element. This application does not specifically limit how the subscription information is obtained.
  • a distributed subnet system 1 includes a main network 1, subnet A, subnet B, and subnet C.
  • the first network element in main network 1 obtains the capability information of subnet A, subnet B, and subnet C.
  • Subnet A supports session management services and location management services, and its service area includes cell 1 and cell 2.
  • Subnet B supports session management services and sensing management services, and its service area includes cell 2 and cell 3.
  • Subnet C supports sensing management services, and its service area includes cell 4.
  • the terminal's subscription information includes the terminal's subscription to the session management service and location management service of subnet A, and the session management service of subnet B.
  • the terminal is currently within the coverage area of cell 1. Since the service area of subnet A includes cell 1, and the terminal's subscription information includes the service information of subnet A, the first message indicates that the service information requested by terminal 1 is the session management service. Based on this, the first network element in main network 1 can use subnet A as the destination address of the first request message. This is merely an example.
  • Step 404 The first network element obtains the first information and sends the first information to the access network device.
  • the first information includes: capability information of at least one subnet and the address of at least one subnet. Based on this, in the subsequent processing of the first request message, the access network device can quickly determine the destination address of the first request message based on the first information and the first indication information.
  • the subnet capability information and subnet address included in the first information are used by the first network element to determine the subnet capability information and subnet address for executing the first request message service processing.
  • the first information also includes: second indication information, which indicates service information executed by a subnet (which can specifically indicate a particular subnet or refer to a subnet in general).
  • the second indication information indicates that subnet X executes session management services, or the second indication information indicates that the subnet executes session management services.
  • the access device can quickly determine the destination address of the first request message by judging whether the service information requested by the terminal in the first indication information is the same as the service executed by the subnet indicated by the second indication information. Refer to step 407 below for a detailed explanation.
  • Step 407 Execute the remaining processing flow for the first request message.
  • the terminal in this flow can be the same as the terminal described above, or it can be a different terminal; this is not specifically limited.
  • the request message sent by the terminal to the access network device is of the same type as the first request message in step 401, for example, both are session establishment request messages or location request messages, etc.
  • the name of the first message in the subsequent processing flow may be different from the name of the first message in step 401.
  • the name of the first message in step 401 is message 1
  • the name of the first message in step 408 below is message 2. This is only an example.
  • the specific content included in the first message in step 401 and the first message in step 408 is the same.
  • Step 408 The terminal sends a first message to the access network device.
  • the first message includes: a first indication information and a first request message.
  • the first indication information indicates the service information requested by the terminal.
  • Step 409 The access network device obtains the destination address of the first request message based on the first instruction information and the first information.
  • the first information includes: capability information of at least one subnet and the address of at least one subnet. If the access network device determines, based on the capability information of at least one subnet, that the first subnet has the capability to execute the service requested by the terminal indicated by the first instruction information, then the destination address of the first request message is determined to be the address of the first subnet, and the first subnet is one of the at least one subnet.
  • the access network device stores the first information that subnet X supports session management.
  • the first indication information carried by the terminal in the first message is used to indicate that the service requested by the terminal is a session management service.
  • the access network device determines that subnet X supports the session management service, and therefore determines that the current terminal's request message needs to be routed to subnet X for processing.
  • the first information includes, in addition to: capability information of at least one subnet and the address of at least one subnet, second indication information; the access network device can obtain the destination address of the first request message based on the first indication information and the second indication information. If the service information requested by the terminal indicated by the first indication information is the same as the service information executed by the first subnet indicated by the second indication information, then the destination address of the first request message is determined to be the address of the first subnet.
  • the first information stored by the access network device includes second indication information, which indicates that the session management service is processed by subnet Y.
  • the first indication information carried by the terminal in the first message is used to indicate that the service requested by the terminal is the session management service.
  • the access network device Based on the second indication information, the access network device directly routes the current terminal's request message to subnet X for processing.
  • the destination address of the first request message needs to be determined by specifically referring to the subnet's capability information and the first instruction information.
  • the first information stored by the access network device includes second indication information, which indicates that the session management service is processed by a subnet.
  • the first indication information carried by the terminal in the first message indicates that the service requested by the terminal is a session management service.
  • the access network device determines that the session management service is executed by a subnet.
  • the access network device searches for a subnet in the first information that has the capability to execute the session management service. If there are multiple subnets, a subnet is randomly selected as the destination address of the first request message.
  • the service area of the first subnet typically includes the terminal's location. It's important to note that when a terminal accesses a cell or performs a cell handover, the access network device can obtain information about the cell the terminal is accessing; this can be understood by referring to existing cell access or handover procedures. Based on this, the access network device can determine which cell the terminal is accessing is covered by that device. If the service area of the first subnet includes the information of the cell the terminal is currently accessing, then the service area of the first subnet is considered to include the terminal's location.
  • Step 410 The access network device routes the first request message to the first subnet for processing.
  • the first request message is sent to the access management network element of the first subnet.
  • Step 411 Perform other processing steps for the first request message.
  • the first request message is a session establishment request message
  • the other processing flow is the subsequent processing flow of the session establishment request message, such as selecting SMF, etc.
  • the access network device after the access network device receives the first indication information that indicates the service information requested by the terminal and is sent together with the first request message, it can determine whether to route the first request message to the main network or the subnet for processing based on the first indication information and the first information. Based on this, the routing address of the first request message can be clearly defined, thereby improving data processing efficiency.
  • the data interaction between the terminal, access network equipment, and the second network element (wherein the second network element is the access management network element of the subnet) is illustrated as an example.
  • This application does not limit the number of subnets and main networks in a distributed subnet system; only one is used as an example here.
  • the execution is as follows:
  • Step 500 The second network element sends the first identifier to the terminal.
  • the first identifier is the identity identifier assigned to the terminal by the second network element. This first identifier includes either the subnet identifier or the identifier of the second network element, so that other devices, upon receiving the first identifier, can route it to the corresponding subnet. It is important to note that if a subnet corresponds to only one access management network element, the first identifier includes the subnet identifier; if a subnet corresponds to multiple access management network elements, the first identifier includes the identifier of the specific access management network element. For example, if subnet Z corresponds to only one access management network element D-NSM1, then the first identifier assigned to the terminal by subnet Z includes the identifier of subnet Z.
  • subnet Z corresponds to two access management network elements, D-NSM3 and D-NSM4. If subnet Z assigns a first identifier to a terminal that includes the identifier of D-NSM3, then other devices, upon obtaining the corresponding first identifier, can be routed to D-NSM3 in subnet Z. Similarly, if subnet Z assigns a first identifier to a terminal that includes the identifier of D-NSM4, then other devices, upon obtaining the corresponding first identifier, can be routed to D-NSM4 in subnet Z. This is merely an illustrative example and does not specifically limit the first identifier.
  • the first identifier assigned to different terminals within the same subnet is different. For example, subnet A assigns the first identifier A1 to terminal 1, while subnet B assigns the first identifier A2 to terminal 2.
  • the first identifier assigned to the same terminal by different subnets is also different. For example, subnet A assigns the first identifier A1 to terminal 1, while subnet B assigns the first identifier B1 to terminal 1.
  • the first identifier assigned to different terminals by different subnets is also different. For example, subnet A assigns the first identifier A1 to terminal 1, while subnet B assigns the first identifier B2 to terminal 2.
  • This application does not specifically limit the scope of the application; it is merely illustrative.
  • This first identifier is different from the identifier used for terminal identity authentication. It is also different from the identity identifier assigned to the terminal by the core network during terminal identity registration, and it is not SUCI or 5G-GUTI.
  • the access network device directly routes the request message to the main network for processing. Since the main network has registered the capability information of at least one subnet, if the main network determines that the request message can be processed through a certain subnet, it will route the request message to that subnet for processing. After the subnet completes processing, a first identifier can be assigned to execute step 501 above.
  • the capability information of the subnet can be understood by referring to the relevant description in step 201 above, and will not be repeated here.
  • Step 501 The terminal determines the first message, which includes a first identifier and a first request message.
  • the first message can reuse an existing AN message.
  • an AN message includes two parts: AN parameters and a first request message.
  • the AN parameters usually include the terminal identifier (SUCI or 5G-GUTI) and PLMN ID, allowing access devices to directly route to the AMF in the existing core network.
  • the first identifier can be added to the AN parameters, thus the AN parameters also include the first identifier.
  • the first identifier can be added to the AN message, then the AN message includes the AN parameters, the first identifier, and the first request message.
  • the first request message can be a session modification request message, a location modification request message, etc., and is not specifically limited here.
  • the first request message is a NAS message.
  • the first message can also be a new type of message that is associated with the routing of the first request message, which is not specifically limited here.
  • Step 502 The terminal sends the first message to the access network device.
  • Step 503 The access network device determines the destination address of the first request message as the address of the second network element based on the first identifier.
  • the access network device determines the address of the first request message as the second network element based on the subnet identifier included in the first identifier.
  • This application improves routing efficiency and data processing efficiency by using different temporary identifiers (i.e., the first identifier) so that access network devices can select the correct first request message routing address without changing the logic of selecting network elements.
  • UE1 i.e., the terminal
  • RAN equipment i.e., the access network equipment
  • NSMC i.e., the first network element
  • UDM i.e., the data management network element
  • D-NSM the access management network element of the subnet.
  • the subnet has been deployed in the distributed subnet architecture. Refer to Figure 6 for execution as follows:
  • Step 601 D-NSM sends a capability information registration request from the subnet to NSMC.
  • this capability registration request can be proactively reported by the D-NSM of each subnet to the NSMC after the initial deployment of the distributed subnet. Alternatively, it can be proactively reported by the D-NSM of each subnet to the NSMC after network functions (or network elements) are added or updated within the subnet after the distributed subnet deployment is completed.
  • the subnet capability information includes: service information supported by the subnet (specifically, the service information that network elements in the subnet can support) and service area information of the subnet (e.g., geographical location, cell identifier, etc.).
  • the subnet capability information can be understood in detail by referring to the description in step 201 above, and will not be repeated here.
  • the subnet D-NSM registers with the main network NSMC, indicating that the subnet has the capability to support session management.
  • the main network can choose to route session management-related services to the subnet for processing.
  • the subnet reports its session management capabilities, it can also further report supported slices, DNN, and other information for the main network to more accurately manage the subnet capabilities.
  • Step 602 NSMC saves the subnet capability information and sends a registration request acceptance message to the subnet.
  • Step 604 Execute the registration process.
  • Step 605 NSMC sends a registration acceptance message to UE through the RAN device.
  • the registration acceptance message includes the terminal's identifier (SUCI or 5G-GUTI).
  • Steps 603 to 605 above can be understood by referring to the existing UE registration process, and will not be elaborated here.
  • the following explanation uses the example of the first request message being a session establishment request message, and the session request message being established for the first time.
  • Step 606 The UE sends an AN message to the NSMC through the RAN device.
  • the AN message includes a session establishment request message (i.e., the first request message).
  • Step 607 The NSMC determines the destination address of the session establishment request message as D-NSM based on the UE's subscription information, UE's location, subnet capability information, and the UE's session establishment request message.
  • the distributed subnet system 1 includes a main network 1, subnet A, subnet B, and subnet C.
  • the first network element (NSMC) in main network 1 obtains capability information from subnets A, B, and C.
  • Subnet A supports session management and location management services, and its service area includes cells 1 and 2.
  • Subnet B supports session management and sensing management services, and its service area includes cells 2 and 3.
  • Subnet C supports sensing management services, and its service area includes cell 4.
  • the terminal's subscription information includes subscriptions to session management and location management services in subnet A, and session management services in subnet B.
  • the terminal is currently within the coverage area of cell 1. Since the service area of subnet A includes cell 1, and the terminal's subscription information includes service information from subnet A, the service information requested by terminal 1 is session management. Based on this, the first network element in main network 1 can use subnet A as the destination address of the first request message. This is only an example.
  • Step 608 NSMC sends a session establishment request message to D-NSM.
  • Step 609 Perform the subsequent procedures for session establishment.
  • Step 610 D-NSM sends the first identifier to UE.
  • step 501 This can be understood by referring to the description of step 501 above, and will not be repeated here.
  • the following example illustrates the situation using the first request message as the session establishment request message, and the subsequent session establishment (i.e., not the first time) as an example.
  • Step 611 The terminal sends a first message to the access network device.
  • the first message includes: first identification information and session modification request message.
  • step 501 for clarification; it will not be repeated here.
  • Step 612 The access network device determines the destination address of the first request message as D-NSM based on the first identifier.
  • Step 613 The RAN device sends a session modification request message to the D-NSM.
  • the session modification request message may include a first identifier.
  • Step 614 D-NSM selects network elements in the subnet to perform subsequent procedures for session modification.
  • steps 601 and 602 above can be performed before step 607, and this application does not specifically limit the execution order.
  • each device may include corresponding hardware structures and/or software modules for executing each function.
  • each device may include corresponding hardware structures and/or software modules for executing each function.
  • the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
  • each function can be divided into a separate functional unit, or two or more functions can be integrated into one unit.
  • the integrated unit can be implemented in hardware or as a software functional unit.
  • FIG7 shows a possible exemplary block diagram of the communication device involved in the embodiments of this application.
  • the communication device 700 may include: a processing unit 701 and a transceiver unit 702.
  • the processing unit 701 is used to control and manage the operation of the communication device 700.
  • the transceiver unit 702 is used to support communication between the communication device 700 and other devices.
  • the transceiver unit 702 may include a receiving unit and/or a transmitting unit, respectively used to perform receiving and transmitting operations.
  • the communication device 700 may also include a storage unit for storing the program code and/or data of the communication device 700.
  • the transceiver unit may be referred to as an input/output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor.
  • the communication device is a module (e.g., a chip) in a communication device
  • the transceiver unit may be an input/output interface, an input/output circuit, or an input/output pin, etc., and may also be referred to as an interface, a communication interface, or an interface circuit, etc.
  • the processing unit may be a processor, a processing circuit, or a logic circuit, etc.
  • the device may be the above-mentioned access network device, a first network element, and a terminal.
  • processing unit 701 and the transceiver unit 702 can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.
  • FIG 8 shows a communication device 800 provided in this application.
  • the communication device 800 can be a chip or a chip system.
  • the communication device can be located in the equipment involved in any of the above method embodiments, such as access network equipment, first network element, and terminal, to perform the actions corresponding to the equipment.
  • a chip system can consist of chips or include chips and other discrete components.
  • the communication device 800 includes a processor 810.
  • the processor 810 is configured to execute a computer program stored in the memory 820 to implement the operation of the various devices in any of the above method embodiments.
  • the communication device 800 may also include a memory 820 for storing computer programs.
  • the memory 820 and the processor 810 are coupled. Coupling is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules.
  • the memory 820 and the processor 810 are integrated together.
  • processors 810 and memory 820 there can be one or more processors 810 and memory 820, without limitation.
  • the communication device 800 may or may not include a transceiver 830, as illustrated by the dashed box in the figure.
  • the communication device 800 can exchange information with other devices through the transceiver 830.
  • the transceiver 830 can be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.
  • the communication device 800 can be an access network device, a first network element, or a terminal, as described in the above-described methods.
  • This application embodiment does not limit the specific connection medium between the transceiver 830, processor 810, and memory 820.
  • the memory 820, processor 810, and transceiver 830 are connected via a bus, indicated by a thick line.
  • the connection methods between other components are merely illustrative and not intended to be limiting.
  • the bus can be an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 8, but this does not indicate that there is only one bus or one type of bus.
  • the processor can be a general-purpose processor, digital signal processor, application-specific integrated circuit, field-programmable gate array, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this application embodiment.
  • the general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in this application embodiment can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.
  • the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM).
  • the memory can also be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto.
  • the memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store computer programs, program instructions, and/or data.
  • this application embodiment also provides another communication device 900, including: an interface circuit 910 and a logic circuit 920; the interface circuit 910 can be understood as an input/output interface, which can be used to execute the transmission and reception steps of each device in any of the above method embodiments, and the logic circuit 920 can be used to run code or instructions to execute the methods executed by each device in any of the above embodiments, which will not be described in detail here.
  • this application also provides a computer-readable storage medium storing instructions that, when executed, cause the methods executed by the devices in any of the above method embodiments to be implemented.
  • the computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.
  • this application provides a communication system, which includes the access network device, the first network element, and the terminal mentioned in any of the above method embodiments, and can be used to execute the methods executed by each device in any of the above method embodiments.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and/or one or more block diagrams.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and/or one or more block diagrams.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de communication, se rapportant au domaine technique de la communication. Un dispositif de réseau d'accès reçoit un premier message en provenance d'un terminal, le premier message comprenant : des premières informations d'indication et un premier message de demande, et les premières informations d'indication indiquant des informations de service demandées par le terminal ; et selon les premières informations d'indication, obtient une adresse de destination du premier message de demande. Après réception des premières informations d'indication qui sont envoyées conjointement avec le premier message de demande et indiquent les informations de service demandées par le terminal, le dispositif de réseau d'accès détermine, sur la base des premières informations d'indication, d'acheminer le premier message de demande vers un réseau principal ou un sous-réseau pour traitement. Sur cette base, une adresse de routage du premier message de demande est déterminée, ce qui permet d'améliorer l'efficacité de traitement de données.
PCT/CN2025/119698 2024-09-14 2025-09-08 Procédé et appareil de communication Pending WO2026056808A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202411296373.8 2024-09-14
CN202411296373.8A CN121692451A (zh) 2024-09-14 2024-09-14 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2026056808A1 true WO2026056808A1 (fr) 2026-03-19

Family

ID=99038784

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/119698 Pending WO2026056808A1 (fr) 2024-09-14 2025-09-08 Procédé et appareil de communication

Country Status (2)

Country Link
CN (1) CN121692451A (fr)
WO (1) WO2026056808A1 (fr)

Also Published As

Publication number Publication date
CN121692451A (zh) 2026-03-17

Similar Documents

Publication Publication Date Title
US12483476B2 (en) Slice control method and apparatus
JP7726396B2 (ja) アプリケーション機能（ａｆ）装置の方法、ネットワーク露出機能（ｎｅｆ）装置の方法、統合データ管理（ｕｄｍ）装置の方法、ａｆ装置、ｎｅｆ装置、及びｕｄｍ装置
US12549935B2 (en) Method and device for providing direct communication in wireless communication system
WO2021203827A1 (fr) Procédé et appareil de communication
WO2023080057A1 (fr) Procédé pour appareil à fonction de gestion d'accès et de mobilité (amf), procédé pour nœud de réseau d'accès radio de prochaine génération (ng-ran), procédé pour équipement utilisateur (ue), procédé pour nœud maître (mn), appareil amf, nœud ng-ran, ue et mn
WO2023106347A1 (fr) Procédé d'équipement utilisateur (ue), procédé d'appareil de communication, ue et appareil de communication
WO2023072054A1 (fr) Procédé d'acquisition de service de tranche et appareil associé
WO2023185295A1 (fr) Procédé de communication, dispositif terminal, et dispositif de réseau central
WO2023145527A1 (fr) Procédé d'appareil de communication, procédé d'équipement utilisateur (ue), appareil de communication et ue
WO2026056808A1 (fr) Procédé et appareil de communication
CN120166580A (zh) 一种通信方法及通信装置
TW202612370A (zh) 一種通信方法及裝置
CN116866844A (zh) 通信方法及装置
CN115734247A (zh) 通信的方法和装置
JP7838667B2 (ja) 通信装置の方法、ユーザ装置の方法、通信装置、及びユーザ装置
EP4507408A1 (fr) Procédé de détermination d'informations, procédé d'envoi d'informations, système de communication, appareil et dispositif
US20260089779A1 (en) Communication method and apparatus
WO2024225050A1 (fr) Procédé d'équipement utilisateur (ue) distant, procédé de premier appareil de communication, ue distant et premier appareil de communication
WO2026026390A1 (fr) Procédé, appareil et système de communication
WO2023184190A1 (fr) Procédé et appareil de configuration de paramètres, dispositif, et support de stockage
WO2025209167A1 (fr) Procédé et appareil de communication
WO2025039755A1 (fr) Procédé et appareil de communication
CN120378992A (zh) 一种通信方法及装置
WO2026016879A1 (fr) Procédé et appareil de communication
WO2026001337A1 (fr) Procédé et appareil de communication